-
-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Autoteleport activating while attempting to mount triggers infinite loop of failed teleports #8
Comments
Hello! Please update to 1.0.0.9 and let me know if that helped |
Still getting the same problem, I'm afraid. |
Are you possibly use any programs or plugins that alter FFXIV's action processing? such as Xivalexander, Bossmod, Noclippy, Reaction, etc. |
I just looked into xivalexander because the name rung a bell, and no, I don't use anything like that. I'm fortunate enough to have very low ping. |
@coredumperror if you go to settings and enable debug mode, you will be considered conductor and you can send messages to echo channel that will be parsed, for example: |
I'm going to be pretty busy for the next few nights, but I'll see if I can find some time to do that at some point this week. |
Managed to make it trigger again with debug mode. Watching the recording, I noticed that there was a different error message at the start of the glitch (at 0:22):
That message shows up a few times, then the infinite teleport glitch starts happening, though I didn't notice it until i'd mounted and remounted a few more times. |
Just to note: this is still happening in DT. I've learned how to mostly avoid it by not mounting up when a new flag is about to go out, but it'd certainly be nice to not have to worry about that. |
Unfortunately, I never could reproduce the issue myself, while I could reproduce "Unable to use. You are currently using another item." I never got teleport action being blocked. Is there a way for you to test it without any other plugins (except teleporter or lifestream)? Because I never heard reports about this issue from other players and I couldn't reproduce it myself too. |
OK, I'll give that a try. I recently found a plugin that should let me reliably recover from the teleport lockout multiple times in a row, so it'll be easier to test. |
Confirmed to be in-game bug |
Oh cool, good to know it's been replicated by someone else, at least. I'm trying to sign up to that forum to reply to that thread with more details, but the damn thing always fails when I try to select my "main character", so I'm completely locked out of posting. >_< |
@coredumperror - I bet you were clicking the rectangle and thought you already selected your main character. Instead, you'd want to check the character's picture, there is star on the upper left corner. That's the one you have to click to assign the character as your main. (You can say "add as favorite") Anyway, I encountered this issue as well. The way I replicated this was:
|
OMFG thank you! The UI on that site is so freaking opaque! |
I've found a rather serious bug with this plugin that has ruined a number of hunt trains for me in recent weeks. Sometimes, if the conductor sends out a flag for the mark in the next zone while I'm mounting up, the game will end up in an infinite loop of teleport attempts, all of which fail instantly with this error message:
The only way to make it temporarily stop spamming that error is to move or cast a non-instant spell, though as soon as I stop moving or casting, it starts spamming the error again.
And what's worse, this entirely breaks my ability to teleport. Even after disabling the plugin to make it stop the infinite loop, I still can't manually teleport, as I get the same error.
It's like the game has gotten into a state where it thinks I'm currently casting Teleport, even though I'm not.
The only way to get it out of that state seems to be either casting Return, after which teleports start working again, or dying and using the auto-Return. But this infinite loop actually happened to me three times on the last hunt train, which put both Return and BLU Self-Destruct on CD, so I was stuck in Mare Lamentorum for several minutes, haha.
The text was updated successfully, but these errors were encountered: