(i used speedhacks)

would this count has cheating? this would invoke "no using the next level option" but you use it at the end of the level screen, so it should be changed to "no using the next level option before collecting the golden carrot"? its very precise hitting the next level before you cant press any of the pause button, but also after hitting the golden carrot. its most efficient at the start of the run, because the run starts at level 1s timer, and doesnt count the retry before, but if youre fast enough, it could save one loading screens worth of time in every level! should it be legal or not? whats your opinion?

Well, firstly I will probably remove the bug from the game, seeing as this was definitely not intentional. Secondly, I think that the level isn't really complete until you have hit the level end screen or else it could be quite time consuming trawling through each run to see if the player actually did hit the golden carrot BEFORE hitting the 'next level option'.

However, I totally understand if people want this to be kept in the game as a challenge to master and explore to reach the fastest times possible. It would just mean that the verifying of runs would have to be very precise and strict and would probably mean a lot of runs could be turned down if the player had tried to do the glitch but failed. It is a problem because if you don't hit the golden carrot, you have essentially just skipped the level without completing it but it is possible for this to happen if they do it correctly.

Alternatively, a new category could be created in which players can do the 'next level glitch' on any level, given that they do it correctly. This way, we could encourage people to master this glitch (even if unintentional) and it could lead to some pretty insane times.

It all comes down to what the community wants and feel free to leave your thoughts on this topic.

Thanks.

a lot of games allow players to play on different versions of the games for different glitches, is this not enforced in this game?

a way to enforce this would be to have a way to show inputs in real time while the run is happening, like nohboard, a rule would have to be made, like "if you want to do pause skip (thats what ill call the glitch for now) then you must have a real time way of showing your inputs" or something like that, it really only saves like half a second, and since the any% board is somewhat un-optimized, a wr could still be achieved without this glitch! so i think it should be allowed