-
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! 👋
- Thread starter Knightly
- Start date
Many_Whelps
WoW was the first MMO
- Joined
- Jul 22, 2018
- RedCents
- 762¢
Raidutils has been working well so far. I've been using it to capture guild raid attendance and it's functioning as expected.
- Joined
- Sep 5, 2020
- RedCents
- 2,722¢
So slotcolors not getting converted?
I’ll have to rename myself to SadChicken.
Took me about three days to migrate, was putting it off and putting it off. I migrated myself manually. One it helps me learn the new structures and two when I started I had no clue the what F is was doing so I was certain there where better ways to do thing.
Really looking for to the new easyfind. Never realized how much I used it till it was gone.
Slotcolors was cool, but after I put that same info on the cursor it lost some of its worth, but still cool.
Everything is easy once you know how.
I’ll have to rename myself to SadChicken.
Took me about three days to migrate, was putting it off and putting it off. I migrated myself manually. One it helps me learn the new structures and two when I started I had no clue the what F is was doing so I was certain there where better ways to do thing.
Really looking for to the new easyfind. Never realized how much I used it till it was gone.
Slotcolors was cool, but after I put that same info on the cursor it lost some of its worth, but still cool.
Everything is easy once you know how.
Hi, I have tried to set up MQNext and I encountered one problem. Missing mesh (map) data.
I use the Migrator to put MQNext in a separate directory C:\RedGuidesNext1 (my regular Live one is in C:\RedGuides).
1) On my Live one there is a Launch Mesh Updater button but no such button on the MQNext one
2) I tried to put MQ2Nav folder both in the config folder and the \RedGuidesNext1 directory
Please help and thanks
I use the Migrator to put MQNext in a separate directory C:\RedGuidesNext1 (my regular Live one is in C:\RedGuides).
1) On my Live one there is a Launch Mesh Updater button but no such button on the MQNext one
2) I tried to put MQ2Nav folder both in the config folder and the \RedGuidesNext1 directory
Please help and thanks
you can use the migrator to copy over all your meshes, try running that again
mq2nav folder goes in the resources folder.
Yes MQ2Nav folder is also in the resource folder
MQ2Spawns is in the latest build. I use MQ2SpawnMaster and MQ2Spawns is a bit dicey so I did some guesswork, you’ll have to let me know if it’s working well or not.
This is fixed in the latest build. There’s also quite a few other autoloot fixes, hopefully improving stability and fixing some long standing bugs in Live (of course, chances are we introduced some new ones as well).
This is in the latest build with the caveat that it only works on ini files in your config folder. MQ will use the file in your macro folder or in your config folder, but I didn’t replicate that code in kisstemplate. It would probably be a good idea to do, but since it was previously hardcoded and would break if you moved your macros folder, this is a step laterally at worst. Maybe someone should change it to use the same logic as MQ proper, but if someone’s gonna do it, that someone’s not me. TLDR: If it’s not working, make sure your ini is in the config folder.
dannuic is actually pretty spot on. Sometimes working on MQ is just as fun as playing EQ.
But I do play at the very least every weekend. I have a set time that I play with a friend of mine from college and just recently my daughter and I started playing together on Live servers.
I don’t ever play more than 6 characters though and right now I’m just playing the two (one of them without MQ at all!)
But I do play at the very least every weekend. I have a set time that I play with a friend of mine from college and just recently my daughter and I started playing together on Live servers.
I don’t ever play more than 6 characters though and right now I’m just playing the two (one of them without MQ at all!)
That was always the plan. We have always called it MacroQuest between us, since that's what it is, "next" was actually a joke that just stuck when we were trying to differentiate during development. I call it a bunch of stuff -- Next, MQNext, MQ, MacroQuest. What it won't ever be called, though, is MQ2.
In fact, the only change in this thread name has been to change it from "MacroQuest Developer Preview (Live Servers)" to "MacroQuest (Live Servers)" since Developer Preview isn't really applicable anymore.
- Joined
- Dec 29, 2017
- RedCents
- 23,976¢
I still call it MQ2 because I hear it makes Knightly throw taco's at people.
Sum1
Warriors are inferior (read: crybaby) tanks
- Joined
- Jul 30, 2006
- RedCents
- 6,302¢
I get it, but if its a totally new program built from the ground up to be different from MQ2, then calling it MacroQuest will confuse people. There already was a MacroQuest, right? before MQ2 was MQ1? or, just MQ?
Sum1
Warriors are inferior (read: crybaby) tanks
- Joined
- Jul 30, 2006
- RedCents
- 6,302¢
So before MQ2 there wasn't an earlier version of MQ that had less functionality or was somehow structurally different from MQ2?
There was, it was MacroQuest. MQ2 now isn’t anything like that MQ2 though. It moved further out of asm and started the plugin architecture, but the current MQ2 code (outside of style) isn’t that code.
Regardless the 2 is still meaningless (which is evident by no one knowing what MacroQuest was or what makes 2 different).
MacroQuest is MacroQuest, we dropped the 2 because it’s never meant anything.
Hi Guys!! Had something strange happen. Logged in my characters on Rizlona. Group up just fine. SK was MT and MA. I ran the group around killing stuff. I worked fine. Now the problem. I went to give some food to one of the group and when I hit the trade key, the character I was giving it to crashed to desktop. I tried it with another group member and it crashed him out. Logged off everyone else.
Next step. I log in a group on a live server. Everyone grouped up. I moved them around and everyone did what they were supposed to do. I then went and killed a few things that worked well. I then tried to give a group member a bronze sword and booom he CTD. I then tried a different item to trade and boom she CDT as well. Now both of these groups were logged in on MacroQuest (MQNext).
Next thing to try. I switched from MQNext to Live. Refreshed everything. Launched MQ2 and then logged in the group. I moved them around and then tried to trade things. Work like a champ. I logged that group out and Logged in the group on Rizlona and was able to trade stuff. No problem.
So my conclusion is that something is messed up on MQNext with trading stuff.
Please look into this and let me know if its just me.
Zeb
Next step. I log in a group on a live server. Everyone grouped up. I moved them around and everyone did what they were supposed to do. I then went and killed a few things that worked well. I then tried to give a group member a bronze sword and booom he CTD. I then tried a different item to trade and boom she CDT as well. Now both of these groups were logged in on MacroQuest (MQNext).
Next thing to try. I switched from MQNext to Live. Refreshed everything. Launched MQ2 and then logged in the group. I moved them around and then tried to trade things. Work like a champ. I logged that group out and Logged in the group on Rizlona and was able to trade stuff. No problem.
So my conclusion is that something is messed up on MQNext with trading stuff.
Please look into this and let me know if its just me.
Zeb
- Joined
- Dec 29, 2017
- RedCents
- 23,976¢
Have you tried it without MQ2 running? Possible there is an issue with the xml file?
Might look in your everquest directory under UIErrors.txt
Morning all... Cwtn it works fine under MQ2. group loads up, everything works, and I can Trade items between group members... When I switch to MQNext everything works great but I can not trade items between group members. I can sell stuff and nothing happens.
The only thing I have not tried is to give an item to someone else not in the group or have someone from outside the group give me an item. My guess is that it will work and not cause a crash.
Zeb
The only thing I have not tried is to give an item to someone else not in the group or have someone from outside the group give me an item. My guess is that it will work and not cause a crash.
Zeb
I am no a dev, but from the point of a joe the couple of big things I like are as follows...
1. Lua -> basically an upgrade to macros but you can run multiple at once instead of just one. Macros are still usable. Specifically button master, make crew, boxhud. They are all great so far.
2. It is faster more efficient etc.
3. Built in frame limiter to help PC performance.
These are just the top few things that I found useful in Next.
1. Lua -> basically an upgrade to macros but you can run multiple at once instead of just one. Macros are still usable. Specifically button master, make crew, boxhud. They are all great so far.
2. It is faster more efficient etc.
3. Built in frame limiter to help PC performance.
These are just the top few things that I found useful in Next.
- Joined
- Jun 12, 2015
- RedCents
- 58,244¢
MQ2 is at best like a big bucket of bolt and nuts just mixed together nothing is tight or nuts matched to bolts.
MQNext has a ton of work done that makes it a box of much more aligned nut sand bolts matched together.
It has exciting new features too like for plugins to have a custom interface called imgui, thats similar to the nav ui, and it has a new scriptinglanguage called Lua, that allows for multiple Lua scripts to run at a time. check out the Lua section on the forums here for some of the scripts all ready put out, its really cool.
it has a great function called framelimiter that makes your copy happy by doing fancy things that lmites the cpu and gpu usagefor the eq clients but still allows them to work without getting bogged down.
The project has a more organized structure on reporting errros and issues and what nots.
MQNext has a ton of work done that makes it a box of much more aligned nut sand bolts matched together.
It has exciting new features too like for plugins to have a custom interface called imgui, thats similar to the nav ui, and it has a new scriptinglanguage called Lua, that allows for multiple Lua scripts to run at a time. check out the Lua section on the forums here for some of the scripts all ready put out, its really cool.
it has a great function called framelimiter that makes your copy happy by doing fancy things that lmites the cpu and gpu usagefor the eq clients but still allows them to work without getting bogged down.
The project has a more organized structure on reporting errros and issues and what nots.
Cybs
Well-known member
- Joined
- Sep 10, 2020
- RedCents
- 1,441¢
I agree with everything Tavrn and Kaen just said. In addition, MacroQuest (aka MQNext) is made by very competent, trustworthy people who have ensured it includes all of the same protections as "MQ2" had, but with the added benefit (and security) of not forcing players to load closed-source plugins or features like MQ2Ic.dll which had been found in the past to self-report (via game mail) those who were using "MQ2" to EQ's Senior GM and another person. MQNext (or simply MacroQuest) gets rid of that extra and unnecessary nonsense bringing MacroQuest back to what it was originally supposed to be in it's modern form.
I have no intention of ever loading obsolete "MQ2" ever again. MacroQuest (aka MQNext) is a huge upgrade!
Cybs, Tavrn and kaen have good points.
From my standpoint: There aren't any black box components in the base compile, which was pretty huge for me (even though I'm one of the developers). It should be huge for everyone... And there are multiple developers vetting the code that goes into anything we'd be changing (although, honestly, I only deeply review about 1/3rd of what brainiac and dannuic commit because they're both brilliant).
But, from a pure user standpoint... I think I stopped counting the number of bug fixes and features we added over MQ2 at around 50. That might not seem like a lot, but you can look at the activity on both compiles and see that one is way more active than the other, and that doesn't count all the updates to plugins. Personally, if I'm adding a feature or fixing a bug, whether it's in core or in a plugin -- I only do it for MQNext. The reason for that is because we made MQNext a lot easier to develop for. There are a lot of "quality of life" additions for developers to just...help make lives easier. And we're adding more all the time, so most of what we've added can't be done in MQ2. That doesn't impact users directly, but it does result in things that impact users.
There's a lot of bullet points on the first page, but the best advice I can give you is -- try it and see. It's not a one way transition, you can install it side by side with MQ2 and compare.
...but faster ;-)
from the stand point of the consumer.....I don't know if I could tell. I don't know how Sony makes TVs but if they want me to buy theirs and not stick with the Samsung that i have already need to know why......=)
I will say my main interest at the moment is Entropy and how it runs toons.
You'll be able to tell that piece of things, if nothing else from how aggressive autologin is. But, I'm also not trying to sell you anything.
If entropy's your thing, @exspes007 stopped updating for MQ2 a while ago, so your choices on that one are either go with Next or use an old version.