• 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 failing with ProjectEQ

ButtKoWitz

Member
Joined
Mar 23, 2023
RedCents
342¢
Howdie,
MQ2AutoLogin worked fine yesterday. Today I started the launcher and updated the LIVE setup in the launcher. MQ2AutoLogin continues to work just fine on the LIVE Server setups I have.

But the EMU Server launcher fails when I try to log into ProjectEQ. It hangs/crashes at entering the password at server log-in. The username is populated, but the password stays blank and nothing proceeds. There is no AutoLogin window displayed (I assume it crashed). I have edited the profiles, made new profile sets, and edited the MQ2AutoLogin.ini without solution. This all occurred today after updating the MQ launcher LIVE to latest version.

WIth MQ running in the background, I can log in 100% manually directly from EQ's shortcut, but MQ is not running at all -- something rather odd there. The AutoLogin window doesn't pop up, like it normally does when logging you in. There are no MQ chat boxes when viewing character selection, and absolutely no MQ running once in game.

Any guidance appreciated!
 

quote said:
Common Problems
Server ShortName = Server Login Screen (Exact name including spaces and characters)`
1: Not moving past the server login screen:
a: AutoLogin is: disabled
b: Server login screen not exact to what is on your server login screen (Different EQEmu hosts use different nomenclature)
2: Log into character select but then instantly log back to the server login screen
a: Server ShortName is wrong, This must match (characters in server ${EverQuest.Server})
 
Tried a number of modifications to AutoLogin.ini/profiles, nothing works. Again, MQ appears to be crashing, as there are NO MQ dialogs/chatboxes displayed at all at any point after selecting the profile to auto-load.

From my limited knowledge of how things run: appears to be shutting down due to failing to inject itself into eqgame.exe
[CODE title="log file"]
D 2023-04-20 07:58:09.507713 [MQ] Logging Initialized (C:\agent\_work\1\s\src\loader\MacroQuest.cpp:200)
I 2023-04-20 07:58:09.508162 [MQ] Starting MacroQuest Loader. Built Sat Feb 25 00:06:48 2023 (C:\agent\_work\1\s\src\loader\MacroQuest.cpp:1199)
I 2023-04-20 07:58:09.508779 [MQ] Initializing crashpad handler (C:\agent\_work\1\s\src\loader\Crashpad.cpp:98)
D 2023-04-20 07:58:09.508800 [MQ] Handler Path: C:\Users\gordy\AppData\Local\VeryVanilla\MacroQuest\Release\crashpad_handler.exe (C:\agent\_work\1\s\src\loader\Crashpad.cpp:99)
I 2023-04-20 07:58:09.509141 [MQ] Crash report submission is: enabled (C:\agent\_work\1\s\src\loader\Crashpad.cpp:104)
I 2023-04-20 07:58:09.509304 [MQ] Crash report guid: e8aa7ede-5326-4bf1-9328-943f2402cb53 (C:\agent\_work\1\s\src\loader\Crashpad.cpp:108)
I 2023-04-20 07:58:09.509314 [MQ] Using shared crash reporter for all MacroQuest instances (C:\agent\_work\1\s\src\loader\Crashpad.cpp:118)
I 2023-04-20 07:58:09.518591 [MQ] Starting NamedPipeServer thread for \\.\pipe\mqpipe (C:\agent\_work\1\s\src\common\NamedPipes.cpp:592)
I 2023-04-20 07:58:09.572163 [MQ] Process monitor started (C:\agent\_work\1\s\src\loader\ProcessMonitor.cpp:412)
I 2023-04-20 07:58:09.572204 [MQ] MQ2Main Path: C:\Users\gordy\AppData\Local\VeryVanilla\MacroQuest\Release\MQ2Main.dll (C:\agent\_work\1\s\src\loader\MacroQuest.cpp:1158)
I 2023-04-20 07:58:09.575212 [MQ] Build: MacroQuest [Apr 14 2023 (Live)] (C:\agent\_work\1\s\src\loader\MacroQuest.cpp:1178)
D 2023-04-20 07:58:09.577439 [MQ] Initializing injector (C:\agent\_work\1\s\src\loader\ProcessList.cpp:1182)
I 2023-04-20 07:58:09.581277 [MQ] Performing injections on any existing eqgame.exe processes (C:\agent\_work\1\s\src\loader\ProcessList.cpp:730)
D 2023-04-20 07:58:09.581331 [MQ] Injector thread started (C:\agent\_work\1\s\src\loader\ProcessList.cpp:1075)
I 2023-04-20 07:58:09.594624 [MQ] Waiting for events... (C:\agent\_work\1\s\src\loader\MacroQuest.cpp:1397)
I 2023-04-20 07:58:19.605072 [MQ] New process detected: 5052 (C:\agent\_work\1\s\src\loader\MacroQuest.cpp:1131)
I 2023-04-20 07:58:19.605162 [MQ] Requesting injection into process id 5052 with delay 1000ms (C:\agent\_work\1\s\src\loader\ProcessList.cpp:712)
D 2023-04-20 07:58:20.606117 [MQ] Injecting MQ into eqgame.exe: pid=5052 (C:\agent\_work\1\s\src\loader\ProcessList.cpp:939)
E 2023-04-20 07:58:20.637940 [MQ] Injection failed: unable to get version information from eqgame.exe. pid=5052 (C:\agent\_work\1\s\src\loader\ProcessList.cpp:993)
D 2023-04-20 07:58:49.950453 [MQ] Process closed: 5052 (C:\agent\_work\1\s\src\loader\MacroQuest.cpp:1137)
[/CODE]
 
No it's installed in Name/AppData/Local/VeryVanilla/MacroQuest/Release
As mentioned, it was running fine yesterday. Today prior to playing I updated the launcher (MQ-Live), and can autolog into Live servers just fine, but my EMU-Server launcher stopped working for ProjectEQ (peqtgc server).
 
Problem - Autologin failing with ProjectEQ

Users who are viewing this thread

Back
Top
Cart