• 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 MQ (Live Servers)

Vanilla - Very Vanilla MQ (Live Servers) (4 Viewers) 3.1.52471.11

No permission to download
Any trick to getting the /mapshow npc to highlight on the map? Shows as previously hidden in the mq2 window but nothing on any layers of the map.
 
Don't know how relevant this is, but, one used to be able to do ${Task[0]} and it would return a value. Now it returns NULL. I believe it would be the same value as ${Task[1]}
 
/mapfilter is doing what I need, still can't figure out for the life of me where the /mapshow command/alias was coming from in the old mq2 setup.
 
seems /exchange will only exchange an item if it is in the base inventory (not in a bag).

Example:
- Rebreather in bag
- Helm of XXX on character
- type /exchange "rebreather" head = does nothing
- Move Rebreather out of bag into base inventory
- type /exchange "rebreather" head = works
Best place for these bug reports is on their respective plugin, that's what I usually look at when I'm looking to do bug fix work. Most of the plugins can be found here: https://gitlab.com/redguides/plugins MQ2Exchange is here: https://gitlab.com/redguides/plugins/MQ2Exchange . But I went ahead and created this issue here: https://gitlab.com/redguides/plugins/MQ2Exchange/-/issues/1

any chance of getting mq2raidutils transferred over?
It'll be in the next build. But I didn't check to see if it works so you'll have to tell me.
 
Bug. Needs a good /swat

When you /varset SomeVariable ${Me.Y}, ${Me.X}, or ${Me.Z} the value of ${SomeVariable} may differ by 0.01

More in the code:

[CODE lang="ini" title="Test snippet"]| With MQNext the float variables that are set using ${Me.X}, ${Me.Y}, ${Me.Z}
| may differ by 0.01. This does not happen with VeryVanilla.
|
| Blunt explanation: When you set a variable to 0.01, you expect to retrieve the
| variable as 0.01, not 0.00 or 0.02
|
| Use the following to see for yourself how it behaves. Move somewhere, remain
| stationary. Move somewhere else.
|
| My belief is the issue lies with a type conversion / rounding rule. It probably
| is widespread.
|
Sub Main

/declare SomeXPosition float outer 0.00
/declare SomeYPosition float outer 0.00
/declare SomeZPosition float outer 0.00

/while (1) {

/varset SomeXPosition ${Me.X}
/varset SomeYPosition ${Me.Y}
/varset SomeZPosition ${Me.Z}

/echo X: SomeXPosition ${SomeXPosition} Me.X ${Me.X}
/echo Y: SomeYPosition ${SomeYPosition} Me.Y ${Me.Y}
/echo Z: SomeZPosition ${SomeZPosition} Me.Z ${Me.Z}
/echo
/delay 5s

}

/return[/CODE]

Edit: Posted as an issue at GitHub
 
Last edited:
Nero,

I think you have a valid point here, but I was concerned that you were in essence comparing two variable conditions. The location of Me at one point in time against the location of Me at another point in time.

I also think it's important to see if the rounding error is consistent and where the rounding occurs.

Here is my test and results.

C++:
Sub Main
/declare floatzero  float outer
/declare floatone   float outer
/declare floattwo   float outer
/declare floatthree float outer
/declare floatfour  float outer
/declare floatfive  float outer
/declare floatsix   float outer
/declare floatseven float outer
/declare floateight float outer
/declare floatnine  float outer

    /while (1) {

        /varset floatzero    0.00
        /varset floatone     0.01
        /varset floattwo     0.02
        /varset floatthree   0.03
        /varset floatfour    0.04
        /varset floatfive    0.05
        /varset floatsix     0.06
        /varset floatseven   0.07
        /varset floateight   0.08
        /varset floatnine    0.09
        
        /echo floatzero  | ${floatzero} | 0.00
        /echo floatone   | ${floatone} | 0.01
        /echo floattwo   | ${floattwo} | 0.02
        /echo floatthree | ${floatthree} | 0.03
        /echo floatfour  | ${floatfour} | 0.04
        /echo floatfive  | ${floatfive} | 0.05
        /echo floatsix   | ${floatsix} | 0.06
        /echo floatseven | ${floatseven} | 0.07
        /echo floateight | ${floateight} | 0.08
        /echo floatnine  | ${floatnine} | 0.09
        
        /echo
        /delay 5s
    
    }

[CODE lang="ini" title="Results"]> /mac rounding_test
floatzero | 0.00 | 0.00
floatone | 0.00 | 0.01
floattwo | 0.01 | 0.02
floatthree | 0.02 | 0.03
floatfour | 0.03 | 0.04
floatfive | 0.05 | 0.05
floatsix | 0.05 | 0.06
floatseven | 0.07 | 0.07
floateight | 0.07 | 0.08
floatnine | 0.09 | 0.09

floatzero | 0.00 | 0.00
floatone | 0.00 | 0.01
floattwo | 0.01 | 0.02
floatthree | 0.02 | 0.03
floatfour | 0.03 | 0.04
floatfive | 0.05 | 0.05
floatsix | 0.05 | 0.06
floatseven | 0.07 | 0.07
floateight | 0.07 | 0.08
floatnine | 0.09 | 0.09

floatzero | 0.00 | 0.00
floatone | 0.00 | 0.01
floattwo | 0.01 | 0.02
floatthree | 0.02 | 0.03
floatfour | 0.03 | 0.04
floatfive | 0.05 | 0.05
floatsix | 0.05 | 0.06
floatseven | 0.07 | 0.07
floateight | 0.07 | 0.08
floatnine | 0.09 | 0.09

floatzero | 0.00 | 0.00
floatone | 0.00 | 0.01
floattwo | 0.01 | 0.02
floatthree | 0.02 | 0.03
floatfour | 0.03 | 0.04
floatfive | 0.05 | 0.05
floatsix | 0.05 | 0.06
floatseven | 0.07 | 0.07
floateight | 0.07 | 0.08
floatnine | 0.09 | 0.09
[/CODE]
 
Nah that's not it. VeryVanilla behaves. The issue is within mqnext.

The problem also presents itself when you convert the values to Int.

What seems to work is ${Math.Abs[${Math.Calc[${Me.X}-${LastMoveX}]}]}>1

That at least mitigates rounding jitter.

Note. Also found the problem occurs with ${Me.Pet.Height}
 
Last edited:
Nah that's not it. VeryVanilla behaves. The issue is within mqnext.

The problem also presents itself when you convert the values to Int.

What seems to work is ${Math.Abs[${Math.Calc[${Me.X}-${LastMoveX}]}]}>1

That at least mitigates rounding jitter.

Note. Also found the problem occurs with ${Me.Pet.Height}

Reproduced the issue with both mq and mq2. This actually isn't a problem with either. Floating point is funky. When you ask for 0.01, the value is actually 0.00999999
You can easily see the issue by just doing /echo ${Float[0.01]}

If floating point rounding mode is set to FE_TOWARDZERO then it will return 0.00
If floating point rounding mode is set to FE_TONEAREST then it will return 0.01.

The default rounding mode is FE_TONEAREST. However, EQ changes its floating point mode to FE_TOWARDZERO. That changes the expected behavior.

What you're actually seeing is some other part of mq2 not playing nicely with EQ and changing the rounding mode.

I've fixed MQ in the latest commit so that when you execute commands from the console it will no longer do it during the imgui draw phase (which has a temporarily modified floating point mode) so that you can easily see what i'm talking about with the /echo, but otherwise i'm not inclined to change this behavior because this is how its always been.
 
Last edited:
I'm completely switched over. Phew.

I miss being able to click the map to nav to spots tho, or nav directly to places with CTRL-F...unless I'm clicking the wrong buttons.
 
I'm completely switched over. Phew.

I miss being able to click the map to nav to spots tho, or nav directly to places with CTRL-F...unless I'm clicking the wrong buttons.

This is what I use in my MQ2Map.ini It adds some versatility but requires MQ2DanNet. Could swap around the commands to use EQBC if that is what you prefer. Just have it pasted at the bottom of the MQ2Map.ini and works perfect.

INI:
[Left Click]
#Shift + LClick = Melee
KeyCombo1=/dgexe melee /nav locyx %y %x |log=off
#Ctrl + LClick = All in zone
KeyCombo2=/dgzaexe /nav locyx %y %x |log=off
#Ctrl+Shift + LClick = Casters
KeyCombo3=/dgexe caster /nav locyx %y %x |log=off
#LAlt + LClick = Self
KeyCombo4=/nav locyx %y %x |log=off
#RAlt + LClick = Priest
KeyCombo8=/dgexe priest /nav locyx %y %x |log=off
 
mq2autoloot
auto sell not work ~~>it can't tap "sell" button by auto
 
Last edited:
Hopefully this is the correct thread for this question. Apologies in advance if it isn't...

I'm installing MQNext so I can migrate over (using the migration tool). When I click "Install" for MQNext from the launcher, I get this question:

1626976773237.png

I do have MQ2 installed at C:\users\redacted\AppData\Local\VeryVanilla\MQ2\Release. I think my answer here should by yes, correct? I'd then have two folders. One for MQ2 (that I'll migrate from) and the new folder for MQNext.
 
Hopefully this is the correct thread for this question. Apologies in advance if it isn't...

I'm installing MQNext so I can migrate over (using the migration tool). When I click "Install" for MQNext from the launcher, I get this question:

View attachment 31712

I do have MQ2 installed at C:\users\redacted\AppData\Local\VeryVanilla\MQ2\Release. I think my answer here should by yes, correct? I'd then have two folders. One for MQ2 (that I'll migrate from) and the new folder for MQNext.
yup, sounds right
 
Thanks Sic. I think that pop up note needs to change to something like make sure you have a unique folder for MQ2 and MQNext before clicking Yes.
 
Hopefully this is the correct thread for this question. Apologies in advance if it isn't...

I'm installing MQNext so I can migrate over (using the migration tool). When I click "Install" for MQNext from the launcher, I get this question:

View attachment 31712

I do have MQ2 installed at C:\users\redacted\AppData\Local\VeryVanilla\MQ2\Release. I think my answer here should by yes, correct? I'd then have two folders. One for MQ2 (that I'll migrate from) and the new folder for MQNext.
There is a field for telling the launcher where you want to install MQNext. This error is happening because you haven't put anything in that field so it doesn't know where you want to install.
 
There is a field for telling the launcher where you want to install MQNext. This error is happening because you haven't put anything in that field so it doesn't know where you want to install.
Agree I saw the field in the settings tab. Not a big deal and I got it to work and used the migrator without any issues. Just think the wording on the pop-up window is a bit confusing.
 
On live servers do people use mq2 to do Ldon's? i would think as they level past it becomes mostly obsolete but perhaps some of the skill augs are useful?
 
On live servers do people use mq2 to do Ldon's? i would think as they level past it becomes mostly obsolete but perhaps some of the skill augs are useful?
ldon was just released on rizlona.

I don't think you mean that question for this thread, however - as this is the MQNext release thread.
 
Yeah, there are scripts to run it on auto. I haven't used them though not sure. I play on Rizlona so just starting with ldon.
 
I have some basic questions. I tried Next once last month and got so frustrated with the changes I quickly just deleted it from my HDD.

What is the preferred step-by-step method to install (and maintain) a standalone version of MQNext that doesn't overwrite an existing MQ2 installation?

Do you use the MQNext distribution files attached to this thread? Or do you just use the MQNext option in the launcher? Or do you grab the files from GitLab? Or? And in what order?

Where do you find the migration script? When do you run it? How do you run it? What will I have to copy/maintain manually?

How do I adjust MQNext to play nice with ISBoxer? (I use ISBoxer to start my team at this time.)

How do I adjust MQNext to work with a non-standard (Drakah's Default_Old) interface?

What other changes should I expect will be required?

What existing VVMQ2 options/capabilities will be different/changed/missing in MQNext? (I see mq2easyfind for example.)

Can I maintain both the existing VVMQ2 and MQNext? Is there a preferred method to switch back and forth?

Perhaps it's time for a sticky FAQ? Or a Redguides Wiki category?
 
I have some basic questions. I tried Next once last month and got so frustrated with the changes I quickly just deleted it from my HDD.

What is the preferred step-by-step method to install (and maintain) a standalone version of MQNext that doesn't overwrite an existing MQ2 installation?

Do you use the MQNext distribution files attached to this thread? Or do you just use the MQNext option in the launcher? Or do you grab the files from GitLab? Or? And in what order?

Where do you find the migration script? When do you run it? How do you run it? What will I have to copy/maintain manually?

How do I adjust MQNext to play nice with ISBoxer? (I use ISBoxer to start my team at this time.)

How do I adjust MQNext to work with a non-standard (Drakah's Default_Old) interface?

What other changes should I expect will be required?

What existing VVMQ2 options/capabilities will be different/changed/missing in MQNext? (I see mq2easyfind for example.)

Can I maintain both the existing VVMQ2 and MQNext? Is there a preferred method to switch back and forth?

Perhaps it's time for a sticky FAQ? Or a Redguides Wiki category?
I would just use the VV launcher and make sure i'm not telling it to install next into my existing mq2 location. ez

> Knightly's Next Migration Utility <

to use isboxer you will need to launch MacroQuest as administrator since isboxer requires elevated privs

I use mqnext with non-standard ui just like regular eq / regular mq2 - i use zliz
 
I use a folder for each install /Test /Live and /MQNEXT
in the launchpad select MQNEXT and go to settings put your /MQNEXT folder there.

If you migrate, migrate from the /Live folder to the /MQNEXT folder copying and leaving files in place in the /Live folder
 
What is the preferred step-by-step method to install (and maintain) a standalone version of MQNext that doesn't overwrite an existing MQ2 installation?
1.) Click the dropdown box in the RG Updater
2.) Choose MQNext
3.) Set your MQNext path to something other than your MQ2 Path (this is already defaulted)
Do you use the MQNext distribution files attached to this thread? Or do you just use the MQNext option in the launcher? Or do you grab the files from GitLab? Or? And in what order?
I build it myself -- which is what GitLab is for. But if you're not building yourself, you can ignore GitLab for everything except submitting issues. The download attached to this thread and the one from the updater are the same, the updater uses the attachment here. So, if I were you, I'd just use the updater and not worry about anything else. The updater will also keep all your private plugins in sync, which this thread will not.
Where do you find the migration script? When do you run it? How do you run it? What will I have to copy/maintain manually?
Sic linked it above. You can run it any time, but the best time to run it is right after you install MQNext. But you can run it as many times as you'd like, it'll just warn you that your configuration will get overwritten (since that's what it's doing). Sic has a good video on how to run it, but it's basically just run it with powershell. As far as what you have to copy manually...nothing that I'm aware of.
How do I adjust MQNext to play nice with ISBoxer? (I use ISBoxer to start my team at this time.)
IsBoxer/InnerSpace forces EverQuest to run as administrator. This isn't required, it just does. So in order for MQ to be used with InnerSpace, you have to run MQ as administrator. You can right click on the MacroQuest.exe and go to properties and set it to always run as administrator and that will solve that problem. We also have a bug where sometimes it doesn't inject on startup, so I recommend launching all of your characters using IsBoxer and then launching MQ as admin. That works every time.
How do I adjust MQNext to work with a non-standard (Drakah's Default_Old) interface?
No adjustment required, if it works with legacy MQ2 it's going to work with MQNext.
What other changes should I expect will be required?
er...get used to crashing less? You can look at this list for a list of issues we've closed: https://gitlab.com/groups/macroquest/next/-/issues?scope=all&state=closed . You can look at the changelog for recent changes. There's a page up on the wiki that has a brief outline (that we didn't really maintain) of what changed. But for the most part, you're not going to need to adapt much. Think of MQNext like "MQ2 but more."
What existing VVMQ2 options/capabilities will be different/changed/missing in MQNext? (I see mq2easyfind for example.)
Any closed source plugin that the author doesn't want converted isn't going to be converted. The ones I know off the top of my head are easyfind and slotcolors. There's probably more. If it's open source and you're missing it, tell me and I'll convert it. I usually do that on the weekends. so if you ask on say...a Monday...gonna feel like a long time before I get to it. (Sorry @Douler -- I'll get to it :D ).
Can I maintain both the existing VVMQ2 and MQNext? Is there a preferred method to switch back and forth?
The issue you're going to have running both side by side is just trying to keep your configuration changes in sync. As long as you are okay with that, it's not a big deal. If you make changes in one, you have to go edit the config in the other, or you have to copy the config over (or always make your changes in MQ2 and just keep running the migrator over and over). You can actually point your macros at the same directory if you want, but it's not a great long-term solution.

As for switching back and forth, that depends on what you mean. Sometimes MQ2 fails to unload and I've got a bug with MQ2Discord right now that causes it not to unload with Next so trying to unload one and load the other while in game is probably gonna give you bad results. But other than that you just load the one you want.
Perhaps it's time for a sticky FAQ? Or a Redguides Wiki category?
Now that it's in the launcher and we have a migrator...try it out and see if you have questions. The F in FAQ stands for "Frequently" asked and the most frequently asked question is "Where my easyfind, yo?"
 
1.) Click the dropdown box in the RG Updater
2.) Choose MQNext
3.) Set your MQNext path to something other than your MQ2 Path (this is already defaulted)

I build it myself -- which is what GitLab is for. But if you're not building yourself, you can ignore GitLab for everything except submitting issues. The download attached to this thread and the one from the updater are the same, the updater uses the attachment here. So, if I were you, I'd just use the updater and not worry about anything else. The updater will also keep all your private plugins in sync, which this thread will not.

Sic linked it above. You can run it any time, but the best time to run it is right after you install MQNext. But you can run it as many times as you'd like, it'll just warn you that your configuration will get overwritten (since that's what it's doing). Sic has a good video on how to run it, but it's basically just run it with powershell. As far as what you have to copy manually...nothing that I'm aware of.

IsBoxer/InnerSpace forces EverQuest to run as administrator. This isn't required, it just does. So in order for MQ to be used with InnerSpace, you have to run MQ as administrator. You can right click on the MacroQuest.exe and go to properties and set it to always run as administrator and that will solve that problem. We also have a bug where sometimes it doesn't inject on startup, so I recommend launching all of your characters using IsBoxer and then launching MQ as admin. That works every time.

No adjustment required, if it works with legacy MQ2 it's going to work with MQNext.

er...get used to crashing less? You can look at this list for a list of issues we've closed: https://gitlab.com/groups/macroquest/next/-/issues?scope=all&state=closed . You can look at the changelog for recent changes. There's a page up on the wiki that has a brief outline (that we didn't really maintain) of what changed. But for the most part, you're not going to need to adapt much. Think of MQNext like "MQ2 but more."

Any closed source plugin that the author doesn't want converted isn't going to be converted. The ones I know off the top of my head are easyfind and slotcolors. There's probably more. If it's open source and you're missing it, tell me and I'll convert it. I usually do that on the weekends. so if you ask on say...a Monday...gonna feel like a long time before I get to it. (Sorry @Douler -- I'll get to it :D ).

The issue you're going to have running both side by side is just trying to keep your configuration changes in sync. As long as you are okay with that, it's not a big deal. If you make changes in one, you have to go edit the config in the other, or you have to copy the config over (or always make your changes in MQ2 and just keep running the migrator over and over). You can actually point your macros at the same directory if you want, but it's not a great long-term solution.

As for switching back and forth, that depends on what you mean. Sometimes MQ2 fails to unload and I've got a bug with MQ2Discord right now that causes it not to unload with Next so trying to unload one and load the other while in game is probably gonna give you bad results. But other than that you just load the one you want.

Now that it's in the launcher and we have a migrator...try it out and see if you have questions. The F in FAQ stands for "Frequently" asked and the most frequently asked question is "Where my easyfind, yo?"

Speaking of which...

Where is my easyfind, yo?

(definitely said in jest.)
 
Greetings to all... Question or 2. I was trying to put up a Kiss ini for a starter Necromancer. It seems that MQNext does not support this as of yet. (1) "/plugin mq2kisstemplate load" and then type /maketemplate to create the .ini ) The question is do we just c&p whats in the KissAssist_choosename.ini from notepad ++ or wait for the plugin to be added to MQNext? I am good with either way. Inquiring minds are scratching heads and going hummmmmm.
 
anyone else getting Varset+0 mq2main.dll crashes when zoning? It happens pretty frequently when going to specific zones
 
The question is do we just c&p whats in the KissAssist_choosename.ini from notepad ++ or wait for the plugin to be added to MQNext? I am good with either way. Inquiring minds are scratching heads and going hummmmmm.
I will add it to my list, but most of your KA is already anonymous.
anyone else getting Varset+0 mq2main.dll crashes when zoning? It happens pretty frequently when going to specific zones
Do you have crash reporting turned on and if so did this happen about 45 minutes ago? What specific zones?
 
I think crash reporting is on by default? Here is screenshot. Happens alot from nek -> lava, dreadlands -> fv, ej -> com, and some other zones I can't remember.
 

Attachments

  • Screenshot 2021-07-25 224133.jpg
    Screenshot 2021-07-25 224133.jpg
    22.7 KB · Views: 19
Vanilla - Very Vanilla MQ (Live Servers)

Users who are viewing this thread

Back
Top
Cart