AislingVT
-
Posts
7 -
Joined
-
Last visited
Posts posted by AislingVT
-
-
Update: I changed my Toogle sprint/roll key to Ctrl, and bullet-jumping while sprinting works wonderfully now with no issue.
Maybe it's something with my keyboard and my Shift button (which is unlikely, as my Shift button works fine outside of the game) But it's highly that there's something that messing with the game while pressing Shift. I strongly advice changing the "Toogle sprint/roll" key to something else to see what will happen.
-
Those PICTURES. They sold me. What's your clan tag? Are you guys open for invitation?
-
I'm new to this game, just played 1 week but already noticed how frequently this bug happens. And even when i tried to log off and on again, i still can't jump. However, when i opened the chatbox and try to type something in, the SHIFT button didn't work so i must assumed it has been stucking the whole time. Tried to use the SHIFT button outside of the game and it works fine. So i opened the game and tried to press SHIFT consecutively and it seemed to solve the problem.
Like the topic above, it DOES involve the "toggle sprint" option. I'll try to turn it off, for now, until i notice any significant changes.
"Ability in Use" Bug: Disables All Abilities, Transference, and More
in General
Posted · Edited by duyhung2h
Quoting from a similar post i found on reddit:
So, as a programming nerd i am, in my speculation it's about threadlocking and action synchronizing.
All player's input action has to be send to the server (in this case, the host player) and return back to the client (player). There's no loss if you are the host because it takes almost absolutely no time for the action to return as action outputs in your game.
But if you're the client and experiencing network issue, it might take a while to send that action to the host and let it came back as output in your game. By the time the action input of yours returned as output in your screen, the action's duration is already done, thread closes and your game outputs a dead action. So it stucks as a "loop" or "exception", and here you go the infamous "Ability is in use" bug.
I think it's best to sum this up by me expressing it as a string of java code:
while(ability.cast()){
server.accept(ability); //server register the action
//some wait time as the server accepting the action and go back to the client
client.register(ability); //sometime server already casting the ability so the client just calling a dead thread
}
class ability(){
float duration = ...;
cast(){
thread.wait(ability.duration);
thread.close(); //remove ability casting when it finishes its duration
}
}