• Hail, we're RedGuides. We want you to play six (yes, 6!) EverQuest characters at once. We have scripts and a friendly community to help, please join our playstyle and say hello! 👋
  • We've added LLM sections to our Terms & Rules and Resource Rules, for everyone's sanity & in-game safety.
    Read more
    a. Do not replace your voice with an LLM. This goes for your posts and your scripts. Drafting and editing with a tool is fine, but don't take you out of what you share.
    b. Do not replace your EQ character's voice with an LLM. We don't want scripts that speak over /ooc, /shout or other public channels. This has been an unwritten rule that's kept casino scripts off the site for decades, but we're now compelled to make it clear: keep automated communication private.

    Why Does RG Review Scripts?
    Nearly every LLM-written Lua script we see is making your character do impossible things, and rarely in a way that's beneficial to you. We've seen heavy server hammering, /target over impossible distances when /nav spawn would passively accomplish the same thing, a spawn search that fires 20+ times per second, and other pointless actions that are likely annoying GMs.

    You are welcome to use LLMs as a tool to structure, draft, and edit your work, but please read critically before hitting /lua run

Problem - MQ2Start caught a crash. NewVarset crashed (first time running EQ with MQ2)

Torx

New member
First time user of MQ2. When I try to launch EQ manually a window pops up with "MQ2Start caught a crash. NewVarset crashed at address 0xXXXXX". I emailed the dmp file to eqmule@hotmail.

Any suggestions?
 
First time user of MQ2. When I try to launch EQ manually a window pops up with "MQ2Start caught a crash. NewVarset crashed at address 0xXXXXX". I emailed the dmp file to eqmule@hotmail.

Any suggestions?
you can PM the dump to me and i can take a peak before mule gets a chance

folks will probably ask for a plugin list etc to try and narrow down the possibilities - but i'll be able to see what plugins you have in the .dmp
 
I'm trying to set up auto login for aradune, the new progression server but when I specify aradune for the server, it doesn't seem to work.

This progression server is supposed to allow 2 boxing right?

Thanks
 
I'm trying to set up auto login for aradune, the new progression server but when I specify aradune for the server, it doesn't seem to work.

This progression server is supposed to allow 2 boxing right?

Thanks
aradune is a trubox - mq2 will not work there.

perhaps that is your crash.
 
Does Truebox block the program somehow or is this just a policy? Aradune specifically says "Boxing any more than 2 characters will result in the following actions taken against your account.... "
 
Does Truebox block the program somehow or is this just a policy? Aradune specifically says "Boxing any more than 2 characters will result in the following actions taken against your account.... "
MQ2 does not work on Truebox servers.

MQ2 is by design not working on progression servers designated as Truebox servers, and will not unless changed the macroquest Developers (Like Brainiac and EQMule)

Here is a list of servers and what their designation is:

Works on "Live servers", Antonius Bayle, Bertoxxulous, Brekt, Bristlebane, Cazic Thule, Drinal, Erollisi Marr, Fippy Darkpaw, Firiona Vie, Lockjaw, Luclin, Povar, Ragefire, Rizlona, The Rathe, Trakanon, Tunare, Vox, Vulak'Aerr, Xegony, Zek

Does not work on: "Truebox" servers, such as Aradune, Corinav, Phinigel, Mangler, Selo's, or Agnarr (other tools such as MySEQ are available)

See also: Test Server version, Emulated Server version.
 
Is there a way to force MQ2 to not load on my TLP account im logging in but still run on my other live account?
running both tlp and live simultaneously? No, if MQ2 is running, it hooks all EQ processes, which then triggers the safeguards if it detects you connecting to a TLP server, it drops you out.

Correct me if I'm wrong, but I believe that TLP and Live are connected via the same EQ client/launcher (unlike, say Test server, which uses a different version of the client), so there's no good way for MQ2 to know which process is or is not going to connect to TLP and attempt to ignore it.
 
While that's correct about Live and TLP having the same client, MQ2 is injected via the tray utility. Launch the tray utility, launch your Live client and let MQ2 inject, then close the tray utility. Launch your Truebox client and there you go.
 
While that's correct about Live and TLP having the same client, MQ2 is injected via the tray utility. Launch the tray utility, launch your Live client and let MQ2 inject, then close the tray utility. Launch your Truebox client and there you go.

I've actually wondered about that - is it safe to have MQ2 injected instances running at the same time you log into a TLP without MQ2, or does MQ2 leave a DLL or some other remnant active that TLP might be scanning for (even though it isn't trying to inject itself into the TLP instance)? As in - has anybody here actually logged into a TLP, while MQ2 was running on a different server, in a different window, but on the same computer - and not had something happen to their account a day/week later?
 
There isn't cross client communication or shared memory if that's what you're asking. But Truebox used to prevent you from launching a second client. I think running one elevated and one not probably works. As well as anything that sandboxes, though I don't personally play on Truebox.
 
Problem - MQ2Start caught a crash. NewVarset crashed (first time running EQ with MQ2)

Users who are viewing this thread

Back
Top
Cart