• 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) (7 Viewers) 3.1.52471.11

No permission to download
Join us with Level 2 access RedCents
Overview Updates (603) Reviews (7) History Discussion
Not sure why it wouldn't be there.


Can Try This
[/QUOTE]


I figured out why the "Run with PowerShell" didnt come up when I right clicked on it. I was right clicking MacroQuestMigrator while it was still in my download folder. Once I moved it to desktop and right clicked the PowerShell option appeared! I am guessing nobody else will do something this dumb but if you are like me and having this issue maybe this will save you some time.

Thanks for the help. On the the next problem....
 
Ok, my next problem. I installed MQnext into a folder I created using the Launcher. I then followed Sic's video and used the MacroQuestMigrator and all went well. I started up MQnext and loaded up a toon. First thing I notice was my autologin macro didnt work but I finished loading toon up manually. When the toon is loaded in, there is no NPC info on the in game map like there normally is. I tried starting MQWar, nothing. I loaded in the Pally and tried loading up RGMercs, nada. I just get the message the they are not valid commands.

The MQnext files all appear to be there (at least it populated with lots of folders) and the inis for CTWN/Sic Plugins and RGMercs are all there. I show the little purple MQ icon on my taskbar. Not sure where to go or what to check from here. Quitting for the night but will pick this up again tomorrow so any ideas in the meantime would be appreciated.

Never Give Up, Never Surrender.
 
My first thought is you probably run EverQuest as administrator. Are you launching from something like IsBoxer? If so, you'd need to elevate MacroQuest since we don't automatically do that (there's really no reason to run EQ as administrator either, but IsBoxer forces you to).
 
Knightly said:
My first thought is you probably run EverQuest as administrator. Are you launching from something like IsBoxer? If so, you'd need to elevate MacroQuest since we don't automatically do that (there's really no reason to run EQ as administrator either, but IsBoxer forces you to).
Click to expand...

You sir are a genius. I didnt list that I use ISBoxer because I didnt think it was relevant to the MQnext problem (this is why I am not paid to think by anyone). Starting MQnext in Admin mode did indeed solve the problem. So now instead of spending the rest of the day troubleshooting the problem I can now play EQ.

I start MQnext with the launcher and not want to have to start using a desktop icon and use the Admin prompt every time and didnt know how to do that. I did a little digging and found a solution that starts MQnext in Admin automatically. I will post what I did for anyone else as clueless as I am.

Go to the EXE file, right-click and select Troubleshoot compatibility. A dialog box comes up, select "Troubleshoot program". There you'll have an option to select that the program requires additional permissions at which point the program will be changed to run as administrator. Save the changes and you're all set.

Thanks for the help Knightly
 
I’m not sure what you mean. How are you launching it that causes it to be admin that you’re not sure how to undo? (Or is the updater running it as admin?)
 
eqgame.exe was not modified to run as admin, none was set to admin. MQNext wont inject unless i run it as admin. Is there a way to find our what's causing this?
 
It seems that the plugin for mq2mule(gui thing for mule assist) does not exit in the plugins directory. It is support on next?
 
No worries I can always swap to live update ini and copy the ini for next. Or there are other plugins out there.

Thanks for the quick response.
 
Tavrn said:
No worries I can always swap to live update ini and copy the ini for next. Or there are other plugins out there.

Thanks for the quick response.
Click to expand...
the muleassist macro itself still operates correctly - just the plugin component doesnt
 
I agree the macro continues to operate well. I like the gui to assist in upgrading the ini on levels. Much easier to click buttons then spell correctly. :D
 
Sic said:
eqmule hasn't updated it for next, and its not an easy 1:1 update, so it will be something that mule will need to migrate, unfortunately
Click to expand...
eqmule or someone he designated has to migrate it because it’s his closed source plugin, which has has less to do with migration difficulty.
 
edit: this was replying to a post that the author has since deleted, so it may seem out of context.

Okay…but if I wanted something done and didn’t want to do it myself, I would probably ask for help from someone who knew how to do it (although in my specific case I would just say “it’s open source, have at it”). So I think implying it’s too difficult when every open source plugin someone has asked for has been migrated is being disingenuous. It makes it sound like Next is hard to migrate to when one of the core things that we did was specifically try to make it fairly easy to migrate to. We spent a lot of time on backwards compatibility and informative messaging. I understand that “it’s not easy 1:1” is technically true, but for the most part migrating to next is fairly easy.

Right now you can even migrate a plugin and only fix errors (ignoring all the warnings) in a very short amount of time. It’s understanding the changes and cleaning up the warnings that takes time, but that doesn’t impede migration at all since the functionality still works (it’s just annoying to have that many warnings).

This may not even be what you meant, but I want to stifle the impression of “it’s so hard only eqmule can do it” because, again, that has less to do with difficulty and more to do with closed source (or poor initial programming). And I want to be clear those aren’t _next_ issues.
 
Last edited:
I just started using MQNext, had something that seemed strange and I know why its happening. Searched this thread and https://gitlab.com/macroquest/next/mqnext/-/issues before posting to see if it had been address.

My 4k monitor and EQ crappy none scaleable UI don't work well together. Not sure how everyone else deals with this but I launch EQ through ISBoxer and it goes to 2560x1400 window size, but then my monitor upscales it 150% so it fills up my 3840x2160 screen and I can still read everything without needing a magnifying glass. Ok I know this can cause issues but for years its worked flawlessly and "just works".

Fast forward MQNext windows, such as the console and very awesome boxhud.Lua windows. Pull either one of them up and looks great, then I Alt+Tab or switch over to another character and bam the MQNext floating windows are now 100% scale and not 150% scale. Now I can't read them so well, and I can't resize the boxhud.Lua window for some reason at all. The MQNext console window I can resize but it stays 100% scale so its very tiny text on my screen compared to what it was. Then they bug out and I can't switch back to the original character, and I have to Alt+Tab and Close the MQNext console/hud window to get it working again and relaunch that window on my driving character.

Anyone else have such a wierd setup and seen something similar?
 
craggyisland said:
I just started using MQNext, had something that seemed strange and I know why its happening. Searched this thread and https://gitlab.com/macroquest/next/mqnext/-/issues before posting to see if it had been address.

My 4k monitor and EQ crappy none scaleable UI don't work well together. Not sure how everyone else deals with this but I launch EQ through ISBoxer and it goes to 2560x1400 window size, but then my monitor upscales it 150% so it fills up my 3840x2160 screen and I can still read everything without needing a magnifying glass. Ok I know this can cause issues but for years its worked flawlessly and "just works".

Fast forward MQNext windows, such as the console and very awesome boxhud.lua windows. Pull either one of them up and looks great, then I Alt+Tab or switch over to another character and bam the MQNext floating windows are now 100% scale and not 150% scale. Now I can't read them so well, and I can't resize the boxhud.lua window for some reason at all. The MQNext console window I can resize but it stays 100% scale so its very tiny text on my screen compared to what it was. Then they bug out and I can't switch back to the original character, and I have to Alt+Tab and Close the MQNext console/hud window to get it working again and relaunch that window on my driving character.

Anyone else have such a wierd setup and seen something similar?
Click to expand...

There's a spot in boxhud where I specifically set window font scale, because I had personally wanted things to actually be a bit smaller when i was fitting it on my monitor, but that was at 1080p. I'm not sure if that setting somehow applies to all the running imgui windows / somehow resets and doesn't change after tabbing away in your case, but you could try out removing the line from boxhud and see if it makes a difference.
Search for ImGui.SetWindowFontScale and either remove the line completely, or experiment with different numbers, and see whether it has any impact?
As far as resizing, its size is fixed based on the defined column widths because .. reasons. Mostly I had just never gone back and looked into how it works with resizing columns.
 
Oh, if you’re changing the scale that way you probably want to set it back to it’s original value. Cuz yeah, it’ll carry over to everything after
 
aquietone said:
There's a spot in boxhud where I specifically set window font scale, because I had personally wanted things to actually be a bit smaller when i was fitting it on my monitor, but that was at 1080p. I'm not sure if that setting somehow applies to all the running imgui windows / somehow resets and doesn't change after tabbing away in your case, but you could try out removing the line from boxhud and see if it makes a difference.
Search for ImGui.SetWindowFontScale and either remove the line completely, or experiment with different numbers, and see whether it has any impact?
As far as resizing, its size is fixed based on the defined column widths because .. reasons. Mostly I had just never gone back and looked into how it works with resizing columns.
Click to expand...

Changing the value of SetWindowFontScale did make it easier to read the font for sure, but the window still changes scale. Deleting it had no effect just did same changing scale.

brainiac said:
Oh, if you’re changing the scale that way you probably want to set it back to it’s original value. Cuz yeah, it’ll carry over to everything after
Click to expand...

Were you saying I should delete that line, or do something else. Thanks for quick replies guys!
 
@brainiac @Knightly

Couldnt do an issue report on git for some reason but /removebuff will remove the 1st buff if the requested spell is not found.

Example: /removebuff "BuffName" if BuffName is not found, the command will automatically remove the buff in top slot (assuming slot 0)
 
Ladon said:
DAMN YOU SIC I WAS TRYNA BE HELPFUL

giphy.gif
Click to expand...
Pika!
 
evianwater said:
Couldnt do an issue report on git for some reason but /removebuff will remove the 1st buff if the requested spell is not found.

Example: /removebuff "BuffName" if BuffName is not found, the command will automatically remove the buff in top slot (assuming slot 0)
Click to expand...
Thank you for the report (and brainiac for the issue). This is fixed, next build will have the fix.
 
ok i might be mising somthing but i followed sic's "migration" and all work fine.. but i cant fire up an eqbc server aint it supos to do that? (is migration in combo whit creating a next folder and hiting instal on rg launcher all thats needed or do i need to add somthing more?)
 
You can use the EQBC server of your choice from your original MQ2 directory. Either copy paste to the MQ directory or just shortcut from its original location.

I'm unsure of what the expected behaviour of the "migration" technique is. I'm a workaround's guy!
 
Sorting out the different copies of EQBC is on my list, and when I’ve done that I’ll compile for MQNext, but for now rhiza has the right of it.
 
Last edited:
Tested out Next. Pretty slick process and I appreciate all the hard work people have put into this. One thing that took me a bit of time to resolve were the missing hotbuttons in the group window. Turns out this was due to the split of mq2targetinfo and needing to enable mq2groupinfo.

Suggestion: A FAQ tab for this project could be helpful to others trying to follow the breadcrumbs for items like that one. (Thanks Sic for providing this in the other mq2targetinfo thread)

"it was split, so there are now 2 plugins mq2targetinfo and mq2groupinfo"
 
Last edited:
@Knightly Another bug for ya...

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
 
Good things: I used the downloader and got the latest MQNext installed. Very very smooth process and a huge kudos to all the hard work that went into this. I envy your skill.

Not quite as good: I had plugged in all my security info about 2-3 weeks ago. On startup, MQNext went diligently about the process of logging in my chars. On each account eq would pop up messages like your login information could not be validated. MQ then appeared to try 2-3 more times and it got through 5 / 6 of my accounts.

What I just noticed is that the saved character profile information is scrambled. The one account that didn't get through was an enchanter, but it says its a druid. That might be a clue. It has been a few levels since I last logged in.

I quit out of one instance that seemed like it would get to a certain point then try repeatedly. It was really erratic. I think it's related to the saved profile information being out of sync?

I would give more information but it all flew by so fast I couldn't catch the precise messages. If there is a way to log the login process I'd be happy to do so.

Edited for clarity.
 
Last edited:
Note: I did this same process again without MQNext running and it still happens. I need to re-enter my account information into eq and try again. Somewhere along the line things have gotten scrambled up somewhere. No idea where the issue lies. All I can do is report my experience.

----

I started from scratch with my profile ini and restarted so I could plug in fresh information. I couldn't remember which character went with what account. I should have written a list somewhere.

I logged into EQ with one of my accounts manually, this went fine. I noticed the window in the upper right corner had a box to auto-log in the character, clicked that, and then saw a selection dropdown. I had to keep my mouse pointer in there or it would disappear.

Plugged in my login for that account. Of course eq wouldn't let me log in another char, so logged out that client completely.

Restarted EQ manually, selected a different account to log in. Lo and behold, when it got to the character select screen, it had still used the previous account. MQ appeared to have overrode my account selection within its machinations.
 
AmericanNero said:
Restarted EQ manually, selected a different account to log in. Lo and behold, when it got to the character select screen, it had still used the previous account. MQ appeared to have overrode my account selection within its machinations.
Click to expand...
I’m going to make a couple assumptions here and you can tell me if I’m wrong: When you say you restarted EQ manually, you’re talking about launching through the EverQuest patcher?

If so that’s not actually MQ doing that it’s MQ misinterpreting the information it gets from EQ. When you log in via eqgame.exe directly (which is what launching from the macroquest launcher does) and bypass the patcher, information about which account you used is written to a file. On subsequent logins, eqgame.exe reads this information from the file.

The interesting part about this is that this still happens regardless of whether you use the patcher or not. Whatever account is in that file gets loaded into memory.

For the most part, this doesn’t matter. When you log in via the patcher it’s just extra information that happens to be correct. However, when auto login gets involved in the mix (right now) it doesn’t know that you logged in via the patcher and it sees the information from that and says “I should log you in.” And it’s a little aggressive on that score. Your success in this area will be purely based on how fast or slow your computer is. But for the most part, for now, if you’re using the patcher to log in you probably want to turn off autologin.
 
You must log in or register to reply here.
Vanilla - Very Vanilla MQ (Live Servers)
Next unread thread 🦁

Users who are viewing this thread

Total: 8 (members: 0, guests: 8)
Back
Top
Cart

Cart

Total -