• You've discovered RedGuides, an EverQuest multi-boxing and scripting community 🧙‍♀️⚙️. We want you to play several EQ characters at once, come join us and say hello! 👋

  • A TLP without truebox has thawed (Very Vanilla ready)
    Frostreaver

Very Vanilla's default MacroQuest.ini

As in removed them from loading default, there is no need for most people to have them loaded, as they are very specific in what they do, so if you need em you can still /load <pluginname>.
 
New default plugins incoming...

[CODE lang="ini" title="default plugins"][Plugins]
; MacroQuest Defaults
mq2autologin=1
mq2bzsrch=1
mq2chatwnd=1
mq2custombinds=1
mq2eqbugfix=1
mq2hud=1
mq2itemdisplay=1
mq2labels=1
mq2lua=1
mq2map=1
mq2targetinfo=1
; RedGuides Defaults
mq2autoaccept=1
mq2camera=1
MQ2dannet=1
mq2easyfind=1
mq2groupinfo=1
mq2moveutils=1
mq2nav=1
mq2pluginmanager=1
mq2portalsetter=1
mq2posse=1
mq2rez=1
mq2xtarinfo=1[/CODE]
 
Last edited:
New default plugins incoming...

[CODE lang="ini" title="default plugins"][Plugins]
; MacroQuest Defaults
mq2autologin=1
mq2bzsrch=1
mq2chatwnd=1
mq2custombinds=1
mq2eqbugfix=1
mq2hud=1
mq2itemdisplay=1
mq2labels=1
mq2lua=1
mq2map=1
mq2targetinfo=1
; RedGuides Defaults
mq2autoaccept=1
mq2camera=1
MQ2dannet=1
mq2easyfind=1
mq2groupinfo=1
mq2moveutils=1
mq2nav=1
mq2pluginmanager=1
mq2portalsetter=1
mq2posse=1
mq2rez=1
mq2xtarinfo=1[/CODE]
Why is bugfix still a default?
 
Why is bugfix still a default?
any reason why you think it shouldn't be? eqbugfix is often used to fix eqbugs that cause crashes or issues before eq fixes them --- like the item casting crash that was happening last year
 
any reason why you think it shouldn't be? eqbugfix is often used to fix eqbugs that cause crashes or issues before eq fixes them --- like the item casting crash that was happening last year
I was under the impression it currently isn't needed.
 
I was under the impression it currently isn't needed.
Well. In the event an eq bug exists that the mq devs find can be handled in bugfix until eq fixes it, the best place for it is eqbugfix. If folks don't have it loaded, then they wouldn't get the benefit of mq devs bugfixing eq stuff, like the aforementioned item clicky casting crash
 
Well. In the event an eq bug exists that the mq devs find can be handled in bugfix until eq fixes it, the best place for it is eqbugfix. If folks don't have it loaded, then they wouldn't get the benefit of mq devs bugfixing eq stuff, like the aforementioned item clicky casting crash
No problem I'll just leave of off until it's needed. Thanks.
 
you're not mixed up with the now-not-a-part-of-macroquest "MQ2IC" are you? that isn't in next, will never be in next

but yeah, eqbugfix is optional plugin, not required to be loaded or anything
 
why is mq2label? no one needs that unless the specific run uis with xml edits for adding it, or on mq2 legacy and have to use anon mode, but in mq next anon is handled by its own system.

mq2bzsrch=1 and there is literally no reason to have this on, it has no features outside of a macro.
 
Yah hud and labels prolly not needed as a default imo. Especially hud.

Agree on bzsrch too
 
Eqbugfix should definitely be on by default or I’m wasting my time fixing EQ’s bugs because nobody is going to get the fixes.

There are at least two fixes in there for things that crash regularly.
 
@Sic recommends we remove MQ2HUD from defaults, and move MQ2TargetInfo to the RG section. Any other changes before I edit?
 
I think we should add MQItemColor. It's simple enough that it's not likely to break anything, and I otherwise forget to turn it on.

edit: on second thought, we should let things settle down with the new UI
 
Last edited:
Very Vanilla's default MacroQuest.ini

Users who are viewing this thread

Back
Top
Cart