• 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

Problem - Autologin not working all of a sudden

adamk10288

New member
Joined
Aug 31, 2016
RedCents
32¢
Basically it goes to the login screen and gets stuck there. The login screen has the username typed in like this:
groupname_server:charactername
i.e.
maingroup_test:myname

Any thoughts on what could have changed?
 
means you need to unload and reload or re-inject MQ2. a system reboot usually also solves this issue...

- - - Updated - - -

Also verify that you have the latest patch for MQ2....
 
If the combined length of maingroup_test:myname
is longer than 30 it will not be able to read it due to a client limitation.
If this is test server are you sure you have the latest eqgame? Maybe they patched it?
If all else fail , kill the macroquest tray icon and kill eq start mq again and then launch your profile.
Are you using the mq login system? Or some other launcher?
Is mq2autologin being loaded?

How big is your mq2autilogin.ini ?
I think there might be a size restriction that I should look into. Can't remember if I dynamically allocate memory or if it's hard coded to 64k or something.
 
not to derail the thread but it may be relevant,

I get this same thing everyday I get home on the first client I try to load, or after one of the sessions craches.

re-injecting fixes this (mq2autologin picks up and logs in) but if I have not been playing for a while, the first session does this.... OR if I have a client crash out (and get the "MQ is blocking sending..." message) the very next client start up does this.

If I start up 1-3-6-12 clients in a row or all at once... just the first one has odd info like adam is describing.

Anyways, thought it may be relevant (what he is seeing) if not, my apologies.
 
If you're using Methods 2 (patchme) or 3 (Isboxer) listed here, you need to UseMQ2Login=0 or it will produce and 'issue' exactly what you're describing. Not sure if that's your issue, just throwing it out there. If you aren't using either of those methods, I'm not sure.

Also, I updated the plugin wiki to reflect this.
 
Problem - Autologin not working all of a sudden

Users who are viewing this thread

Back
Top
Cart