1. The ability timer is set as an unsigned (only positive) number. The code that triggers when her meter reaches 0 doesn't because of you triggering the ability again, next game tick the decreasing code doesn't check if the ability is at 0, so it subtracts 1 from 0.
So, the counter goes from 0 to the limit, an underflow, it "rolls over" like a mechanical counter. So then the remaining miliseconds/seconds (probably ms considering they do abilities that last for a second an a half) will go to either 4.294.967.295 if they used a 32bit counter, or if they used 64bit (unlikely, it'd be a waste of memory) it'd go to 18.446.744.073.709.551.615. Then it would keep counting down again until it reaches 0 and the code triggers to stop it again. I think this is unlikely, because probably then the bar would just stretch to the edge of the screen leaving the UI. I've seen games do this, like when you cheat more health in Undertale.
The fix for this bug would be to make the code that decreases the timer check if the timer is 0 before decreasing it, and not doing it if so.
2. The ability timer is set to a signed (can be negative or positive), number. In this case, 0 just goes to -1, but the ability code disables the ability when the timer is *equal* to 0. Then it's a similar case. The time decreasing code just keeps running until it hits the lower limit, -2.147.483.648 for 32bit, -9.223.372.036.854.775.808 for 64bit. Then it underflows back to the limits for signed integers. These are smaller because you use a bit to store the sign (not exactly, but simplifying you do in practice). They are 2.147.483.647 for 32bit 9.223.372.036.854.775.807 and for 64bit.
Then it would keep counting down to 0, where the code to disable the ability will trigger. I think this case is more likely because the values for these timers would normally be small, and programmers are lazy. The default is usually signed numbers, and also if you take into account the UI meters being empty. Depending on how they are set to render, this could make sense.
Easy fix for this would be to make the code that disables the ability, do so if the number is ≤ (less-or-equal) to 0
In the above two cases, the ability is not really infinite. It would just be a really long time. The lowest would be on the unsigned 32bit if it's milliseconds, and it would still take seven weeks for the ability to run out.
However, I believe it may be infinite under a certain condition.
3. Depending how the game processes events and triggers, the "Disable Xilonen Ability when it reaches 0" event might be exhausted, or locked. I suspect that might be the case seeing how you can swim with it, the event to disable the ability is gone from the event queue, the game believes the ability is not in use, or the code responsible for it is locked. A desync, two parts of the code believe something different, because of a lack of a single source of truth, which also happens quite a lot in games since even if it is prone to bugs sometimes it's faster (or it might be just bad code). The game believes it already disabled the ability, probably because one of the above two cases trigger.
This bug is harder to fix, specially the cause of the issue is the problem, if it's a race condition (when pieces of code that run simultaneously produce different results if triggered in a certain order or not, thus the name, the pieces of code are "racing" each other) , of the player re-triggering the ability fast enough to mess with the code that disables it.
The deep or correct fix is for example, to use a Mutual Exclusive Lock, or Mutex, on the code for handling the ability. Making sure the player can't trigger it while the code that is disabling it is running.
This is all speculation, I would need to either test, or poke at the games memory, the latter the anticheat won't be happy about. Either way, I'm just a coder, not specifically a game developer, so other things might be at play here. Someone else from the field might offer more insight.
The only problem is that uh we can’t regenerate stamina but we can eat stamina restoration foods though to get stamina and we sadly can’t climb on uh the "Phlogiston rocks" which we can normally climb if we used Xilonen or Kachina’s skill
man the timming was really hard
i stream on Twitch frequently!! come join and I'll say hi! 🙂 https://twitch.tv/kettletoro
Join our Discord!: https://discord.gg/kettletoro
All i see is 1600 primogems
A couple days ago, a nice (fellow simp who also yelled at me for not leveling up my Father) person taught me this trick!
Oh it still new bug, i can skate whole place now
That pole dance be wild
Why it doesn't work for me 😭
Hoyo if u patch this give us 1600 primos PLEASE
mr kettle, have you seen the hu tao bug where shes very cute and appears in your character list randomly with a 70/220 crit ratio
Hoyoverse we want apologems
It's gonna suck when this is patched
But how do you get rid of it?😭
Side note, i dont think it works in co-op
Wish these bugs worked on mobile 😢
Welp there’s goes something good
My hypothesis as a coder:
Three things can be happening here.
1. The ability timer is set as an unsigned (only positive) number. The code that triggers when her meter reaches 0 doesn't because of you triggering the ability again, next game tick the decreasing code doesn't check if the ability is at 0, so it subtracts 1 from 0.
So, the counter goes from 0 to the limit, an underflow, it "rolls over" like a mechanical counter. So then the remaining miliseconds/seconds (probably ms considering they do abilities that last for a second an a half) will go to either 4.294.967.295 if they used a 32bit counter, or if they used 64bit (unlikely, it'd be a waste of memory) it'd go to 18.446.744.073.709.551.615. Then it would keep counting down again until it reaches 0 and the code triggers to stop it again. I think this is unlikely, because probably then the bar would just stretch to the edge of the screen leaving the UI. I've seen games do this, like when you cheat more health in Undertale.
The fix for this bug would be to make the code that decreases the timer check if the timer is 0 before decreasing it, and not doing it if so.
2. The ability timer is set to a signed (can be negative or positive), number. In this case, 0 just goes to -1, but the ability code disables the ability when the timer is *equal* to 0. Then it's a similar case. The time decreasing code just keeps running until it hits the lower limit, -2.147.483.648 for 32bit, -9.223.372.036.854.775.808 for 64bit. Then it underflows back to the limits for signed integers. These are smaller because you use a bit to store the sign (not exactly, but simplifying you do in practice). They are 2.147.483.647 for 32bit 9.223.372.036.854.775.807 and for 64bit.
Then it would keep counting down to 0, where the code to disable the ability will trigger. I think this case is more likely because the values for these timers would normally be small, and programmers are lazy. The default is usually signed numbers, and also if you take into account the UI meters being empty. Depending on how they are set to render, this could make sense.
Easy fix for this would be to make the code that disables the ability, do so if the number is ≤ (less-or-equal) to 0
In the above two cases, the ability is not really infinite. It would just be a really long time. The lowest would be on the unsigned 32bit if it's milliseconds, and it would still take seven weeks for the ability to run out.
However, I believe it may be infinite under a certain condition.
3. Depending how the game processes events and triggers, the "Disable Xilonen Ability when it reaches 0" event might be exhausted, or locked. I suspect that might be the case seeing how you can swim with it, the event to disable the ability is gone from the event queue, the game believes the ability is not in use, or the code responsible for it is locked. A desync, two parts of the code believe something different, because of a lack of a single source of truth, which also happens quite a lot in games since even if it is prone to bugs sometimes it's faster (or it might be just bad code). The game believes it already disabled the ability, probably because one of the above two cases trigger.
This bug is harder to fix, specially the cause of the issue is the problem, if it's a race condition (when pieces of code that run simultaneously produce different results if triggered in a certain order or not, thus the name, the pieces of code are "racing" each other) , of the player re-triggering the ability fast enough to mess with the code that disables it.
The deep or correct fix is for example, to use a Mutual Exclusive Lock, or Mutex, on the code for handling the ability. Making sure the player can't trigger it while the code that is disabling it is running.
This is all speculation, I would need to either test, or poke at the games memory, the latter the anticheat won't be happy about. Either way, I'm just a coder, not specifically a game developer, so other things might be at play here. Someone else from the field might offer more insight.
We want 1600 apologems
apologems now
Unrelated to video but I got Xilonen on my second wish and I'm super happi:D
If you have trouble. Set ur FPS to 30. Also Hoyo we demand 1600 primos
This is no bug, is a feature, literally the tool i used to reach 100% exploration on whole Modsdadt.
Hoyo, PLEASE, DON'T FIX THIS!!!!
Reminds me of the Kokomi water walking glitch 😂
We got poll dancing in Genshin before gta VI
Very funny 👍 pole skating
FREEMOGEMS!!!!!
Today a patch update came and it says the one of her glitch got fixed and that's is her skating on water ( i guess this one got fixed sadly).
Where is our 1600 primos hoyoverse..
The only problem is that uh we can’t regenerate stamina but we can eat stamina restoration foods though to get stamina and we sadly can’t climb on uh the "Phlogiston rocks" which we can normally climb if we used Xilonen or Kachina’s skill
I hope they dont fix this 😭😭
1600 primos for this one hoyo
Imma use this to get all the chests I didn't bother with in liyue
Ugh, I hate her so much. Why does everyone give her so much hype?
(Draw her from gatcha just in time)
I love her 😍
Shoot I gotta try that now!
First thing she does is make Xilonen pole dance 😂
We demand 16 million primogems for this absolute monstrosity
This character actually looks fun to traverse the world with
i wouldve pulled for her if i knew it wouldn't be fixed, i dont even care if theres a speed boost or anything, i just wanna infinite skate
Alright Hoyoverse, we expect to get 1600 primogems
– cus this was cool and u took away happiness
– cus we need primos
10 years?!?!
I see grainfruit
Alright Hoyo that’ll be 1,600 primogems😤🫴
That one ddlc sound effect
As much I love people trying it out, I’m sad it’ll probably get patched because the genshin ccs are making vids on it 🙁
I can’t do this BECAUSE QIQI MADE ME LOOSE MY 50/50!! >:,(
Ok hoyo pls leave this and you don’t have to give us primos plsss