Problem - MQ2 Login is repeatedly getting me killed

[RoboClaptrap4]

As of about a week ago, something is very wrong with some component of MQ related to login. I made no changes to my MQ2AutoLogin.ini file from what I had before, and yet this is constantly logging characters in without my permission, thus getting them killed, it is beyond infuriating. When I reach character select, on the in-game MQ2 window, there's a message saying "Selecting ToonName in 3 seconds. please Wait...or press the END key to abort". This has never happened before last week and I have no idea why it's happening now, but it's severely disruptive and completely unhelpful. Here's how MQ2 auto-login used to work for me:

1. I would launch all my EQ instances with ISBoxer, which would take 3-4 minutes
2. MQ2 AutoLogin would take them all to character select, and stop there, which is exactly what I would want
3. Once everyone was at character select, I would log them all in at once

Now, here's what happens

1. I launch all my EQ instances with ISBoxer
2. Whenever a character reaches character select, they Enter World 3 seconds later
3. I frantically alt tab from window to window, unable to see which window actually has focus since the EQ client doesn't shift focus properly while zoning, hitting the End key to try and abort logins
4. Every single character who I miss logs all the way in and gets killed one by one

This is so unforgiving that it isn't even possible to /camp a character unless I do each one in sequence, since I have to wait for it to reach character select so I can hit the end key before it logs them right back in. Sometimes, the characters get logged back in before the character select screen is even visible. This is seriously approaching unplayable. Here is what should happen:

1. When I open an EQ instance, MQ2 AutoLogin should go to character select AND STAY THERE
2. When I /camp a character, it should never, ever, ever log them back in without explicit action from me

How do I fix this?

 

[kaen01]

So the first case for you, is not autologins behaviour , thats entirely isboxer i believe.
Second case is how autologin is supposed to work.

i think what you might have had happening to you, is that you never really used the full effect of autologin, but had ixboxer log them in, and in your mq2 tray icon had mq2autologin disabled, i would try and do that again if i was you.



Make sure the mq2login is not enabled, and i think it should go back to normal behaviour, since you are using isboxer to log in your toons, and not the autologin profile system.

 

[RoboClaptrap4]

I don't think ISBoxer is actually logging me in, it doesn't know any of my passwords. Before I started using MQ, ISBoxer would launch everquest instances and they would sit on some opening screen where you have to hit an Accept button and I would manually do things from there. When I first started with MQ and created an MQ2AutoLogin.ini file, what started happening was that as soon as the EQ window opened to that splash screen, it would start clicking through things, enter my password, log in, and jump onto the correct server. It definitely wasn't ISBoxer that did that, it was some aspect of MQ (which I assume was MQ2AutoLogin because it started happening as soon as I filled out that INI file).

 

[kaen01]

hmm.. then i am at a loss i know you have to setup autologin differently for using isboxer, the ini file that is.

 

[RoboClaptrap4]

I just turned off MQ2Login on that context menu, then closed and restarted MQ. Then I logged into character select on a new account. Right after the stupid Rizlona pop-up asking me to accept terms and conditions, I saw the same message about "logging in in 3 seconds, press END to cancel".

There was a recent change to support Rizlona:

May 28 2020
- Updated MQ2AutoLogin to support rizlona logins.

I wonder if whoever did this made a mistake and set MQ2AutoLogin to automatically make you Enter World on Rizlona if it detected that the EULA accept dialog wasn't present. This always tries to log me into whatever the currently selected toon is, even though I never had anything in my auto-login settings about that toon

 

[kaen01]

can you show me a snippet of your autologin ini , specifically the [settings] section

 

[RoboClaptrap4]

I can, but I'm looking at the changelist:

MQ2 Auto Sync 05/29/2020 02:38:45 (710e5e8e) · Commits · RG Creators / LegacyMQ2 · GitLab

An unmaintained legacy version of MacroQuest2 for 32-bit EQ clients.

gitlab.com

This is about the time this started happening and seems directly related to this problem.

Here's the ini though. This worked perfectly up before last week:
[CODE lang="ini" title="ini snippet"][Settings]
# Must be disabled.
UseMQ2Login=0
# NOTE: The following line is optional, as it defaults to off. However, it cannot be set to 1 to use sessions.
UseStationNamesInsteadOfSessions=1
KickActiveCharacter=1
InstantCamp=0
Debug=0
WinTitle=EverQuest
KickActiveTrader=1
UseAuth=0
LaunchDelay=1000
NotifyOnServerUP=0

[Something!]
StationName=SomeStationName
Password=lolnope
Server=rizlona
Character=
[/CODE]

 

[Knightly]

I think what you are seeing is that prior to that update, MQ2AutoLogin wasn't working on Rizlona. It would take you as far as the character screen because there was nothing built in to click the agreements at the character select screen.

So, effectively, autologin was getting "stuck" and couldn't log your characters in.

Now, however, that was fixed and it no longer gets stuck.

One workaround you could use is to just give autologin the name of a character on that account that doesn't exist.

 

[kaen01]

knightly sounds right, and everything in ini looks fine for isboxer use.

knightly would it be possible to have a checkbox added to autologin that only takes us to character select and selects that character but does not hit enter world.. i know its a small group of people that like it that way, but sometimes it be nice to have it load all and then you can just select your trader instead of having to add 10 more profiles.

 

[Knightly]

It's absolutely possible (in fact, I wasn't 100% positive it didn't already exist), but just giving it a character name that doesn't exist will solve it for now.

 

[RoboClaptrap4]

Will it actually solve it even in the short term though? I'll try it but based on that code snippet, it doesn't seem like it will help. The issue seems to be that, after that code change was made, if the confirmation dialog ever pops up, MQ2Autologin automatically clicks yes then decides to log in 3 seconds later. Because Rizlona is a weird server and that stupid confirmation dialog pops up at strange times (such as occasionally when I /camp), it seems like no matter what the INI file actually says, the code will start a log-in process 3 seconds after that dialog box gets detected and dismissed

 

[Knightly]

I didn't look at eqmule's changes, but prior to that change if the character name didn't match it would stop. I just assumed his changes were only to handle the dialog box change. If it doesn't work I'll look at it.

 

[bb4]

It's absolutely possible (in fact, I wasn't 100% positive it didn't already exist), but just giving it a character name that doesn't exist will solve it for now.

I've got 2 profiles. 1 with the names that logs me in all the way and a 2nd one with "warrior" and "cleric" to sit at character select. Easiest workaround ever.

 

[eqmule]

There is a bug where eq shows the rule consent dialog every single time u login, i think the intention was to show it only once. Due to that mq2autologin clicks it, unfortunately when u camp out it pops again and autologin thinks aha, u are at charselect for the first time again, time to log u in. Now i can fix it probably but it would be much better if dpg stopped showing it every single time u get to charselect. Dreamweaver said they are aware.

 

[RoboClaptrap4]

Thanks for the reply, Mule! Glad to see what I thought was happening is indeed happening.

It looks like, however, that putting a gibberish character name does indeed short-circuit the undesired login that happens every time the dialog is dismissed. Before I added a fake character name to my ini file, it would just try to log in whatever the current character is. Now, whenever it dismisses the dialog, it tries to log into the fake character (and thus stays on character select). Thanks for that suggestion Knightly

 

[kaen01]

i has fixed it for you guys, that would atleast resolve the issue easily

 

[Many_Whelps]

Nice shop

 

[Sadbull]

I had the same problem, Its not ISboxer, its MQ2. When in the character select screen, MQ2 windows states it will log in the character in 3 seconds unless you press the end button.

My MQ2 login was disabled by it still did it anyways. I was able to get it to stop by editing the MQ2 ini file. If you right click the icon, there is a INI File button that opens the INI file. Inside the file there will be a [plugins] block.

[Plugins]
mq2autoaccept=1
mq2autologin=0
mq2cast=1

Changing that to zero stopped my characters from automatically logging in after I camped them, got rid of that logging in in 3 seconds message.

 

[virtuoso65]

I think what you are seeing is that prior to that update, MQ2AutoLogin wasn't working on Rizlona. It would take you as far as the character screen because there was nothing built in to click the agreements at the character select screen.

So, effectively, autologin was getting "stuck" and couldn't log your characters in.

Now, however, that was fixed and it no longer gets stuck.

Oddly now after the fix if I log in a toon then log out they will instantly log back into that toon,

 

[methodx]

Oddly now after the fix if I log in a toon then log out they will instantly log back into that toon,

Yeah getting that too, as a dirty workaround if I'm on a char and want to go to character select screen and stay there I just do a /switchchar fhdjdjxhd

It will then camp out and the plugin will try log in a character called fjdhsjfkgk so it just stays at character select until I'm ready.

Can log in whoever when you're ready

Haven't been able to stop a character logging in by pressing END key within the 3 seconds since the plugin was fixed to deal with the EULA

Now that I'm playing on a couple of different servers from time to time the plugin will just load a character from a previously played server, but this is intermittent. Say I was last playing FV but now everyone is logged out. If I click to load a six man on rizlona, it could be the 4th client loading up that will go to firiona instead and load in a random character, not even the one I was playing last

Just a few bugs, still beats manually loading the client and logging in. I don't tend to log out anywhere too dangerous so it hasn't got me killed... Yet

 

[jande]

Yeah getting that too, as a dirty workaround if I'm on a char and want to go to character select screen and stay there I just do a /switchchar fhdjdjxhd

I took it a step farther /switchchar fhdjdjxhd is too much for me to type, yeah I am lazy
so
/alias /zz /switchchar fhdjdjxhd
then just use
/zz

So So very lazy

 

[methodx]

Good idea, never thought of a zzz command

 

[Turaj Steelfist]

I know that hitting the "home" key turns on the auto login function, is there key press that disables it? I have not been killed by this auto login feature, but I have found it to be extremely annoying. I can see the benefit of auto logging in for someone that runs many toons, but since I only run 2 at most 3 (rarely) I want to choose when a toon logs in. And since my "home" key is used to level my toon's perspective, changing that to a different key after 21 years is not an option with muscle memory and all. I don't run isboxer or anything like that its just MQ2 and EQ.

 

[runcade]

Got killed by this for the first time now. When I camp out I really don't want it to countdown from 3 and log that char back in.

 

[Knightly]

That's actually posted higher up in this thread, Fueil, but what they're reporting is a bug.

 

[Fueil]

Oh my bad! What I get for not reading it all. Lol

Removed it.

 

[dontrootmebro]

i has fixed it for you guys, that would atleast resolve the issue easily
View attachment 22051

Why isn't this a thing yet?!