Ill sub if u make a crossy road video In all seriousness though, this isn't really the place to be advertising your YouTube channel (don't anger the mods)

Okie, thanks Dare

This is a very interesting find if this is correct, I do not know of anyone else who has experienced this. Good luck!

Yes... the coins collected in the run are doubled at the end - he only collected 319

I agree with all points made by Nrrillinthas. Further, the rule stated in the forum post: General Rules states "Pausing is not allowed in runs. If it is unintentional, we won't reject your video, but you must unpause ASAP." It makes no mention of preventable pauses, only unintentional ones, thus invalidating the argument of "Oh he should have just plugged it in, it was preventable." Therefore there is only the question of if the pause was intentional. This is ultimately ambiguous and up to the refs, however due to BigPhatDog's integrity in both his prior submission and in the LCS competition, and because of the smaller positive impact a pause here gave him (as opposed to at other times, if we assume the worst, that it is always being charged while staying at low battery if it were to be unplugged or something similar), I would assume referees would come to a negative conclusion.

This however does call into question the validity of the rules themselves - should they focus on preventability as opposed to intention? Is anything potentially advantageous assumed to be intentional? Etc. How should abuse of this be recognised and dealt with?

Whatever the outcome, I think that the run obeys the rules and verification standards of the time of its submission, and should therefore remain on the leader board until proven illegitimate.

So Beesley's mobile red coin HS (638) (https://www.speedrun.com/crossy/run/zxdwlv5y) includes a coin doubling glitch that as far as I can tell from discussion with other players is mobile only and random, and is random ie cannot be purposefully induced. I think that these runs should have their scores halved so the score reflects the actual number of coins collected, rather than the difference between ending and starting amounts. Also seeking verification that this is allowed, and was not an oversight or some such by mods.

Request to remove unrestricted death%. death% is already a stupid category, and unrestricted literally can't be faster the (restricted) death%. No one does this category, and there is even less skill involved in it than in death% IDK how it is even possible to fail tying the restricted death% time on unrestricted. Like I might as well just submit my restricted run into the unrestricted category.

This has already been suggested and enacted. I vote to delete this thread.

Would like to point out this is one of the easiest speedruns to fake/splice ever... But eh, if you have faith in the community whatever

Just found another discrepancy (maybe) - if you look at 28 (death score) - the 'top score' is displayed twice with a gap between. It doesn't scroll on from the side of the screen, which is normal, but then there is a frame where there is no text. This first instance appears for only one frame. Furthermore, on the frame after this, the cars do not move, only the screen... I dunno

My main issue with this is the ease of splicing whenever deaths occur - 100 coins also has this problem in my opinion - runs could be grinded until quick deaths were achieved 10 times, then the fastest put together into one video. Hence I vote no for this category - it's easily cheat-able and also pretty niche

I wouldn't say that mate, mods have experience in these, and I'm sure it is possible that it isn't. That isn't polite to Hexl, or the mods for that matter. This is not conclusive evidence and should not be treated as such, and if it was 'definitely fake' I would love an explanation.

All righty..... here we go I was watching this run - amazed as most, but more than a few things bothered me.

1. Maths - CR is 60fps, 25 hops requires 24 frames from the 1st hop. This equates to 0.400 seconds. This is assuming double clicks are impossible, which I believe they are. I have gotten one (see last points of 1000 Pac-man run), but I assume it is lag induced. One frame below this is Hexl's run, which going frame by frame, includes several doubles in a frame, as well as not gaining points on a frame.

2. Scroll wheel better than autoclicker? Using an autoclicker to my knowledge should have the same effect as rerouting left click to the scroll wheel. However, I was unable to obtain double clicks, and gained extremely consistent 0.400s using an autoclicker running at more than 15 clicks per frame. I note this based on Hexl's own reply to 'How?' of "scroll wheel"

Now the stuff other people probably didn't see... I found these after finding nothing contradictory to 1. and 2.

3. Audio file contains ending sound during run. This is also clearly audible on the video itself. I maybe to cover up janky sound from a double click? Maybe a bug?

4. Character turn animation: Character turn animation is separate from forwards movement. If you use an autoclicker and compare the turn animation the fox between your's and Hexl's, you should see a noticeable difference. You should also see a disturbing similarity between one forwards input (one frame press and release), and the turn animation of Hexl's fox - around 11/12 frames before it is pretty much straight, whereas an autoclicker run, the fox is about only halfway through turning in the same number of frames.

I will say in Hexl's defence that he dies on the correct lane, cheating if it did occur was not that blatantly obvious.

Id love any input, and would welcome being disproven. Otherwise, I firmly believe that 0.400s is the absolute maximum for this category, even with click + button tech, which I have tested - any release of both on the same frame causes only one input.

I have not yet looked at the 500 category, but I hope I don't find anything similar there. Edit: 50 seems to be at current theoretical maximum, double 25, + 1 frame as no. 26 is included, but score 1 isnt, I see no need to investigate further

can I ask why this is?

unless I have an outdated version, no

Yeah, I understand you, but I really don't agree with that scoring system - no side hops, both llamas, toughest enemy beaten, and most coins are all far more skill intensive than categories such as death%, 10 coins/lilypads, even if they have less competition. (If you didnt notice those categories were under the 2x section)

I think that I will make my own scoring system, but you can use the file for your system if you like. The main reason for this is the complete absence of the bashy beaver, penguin, and polar bear categories :)

I don't really know what you mean by "category extensions" or "the last box", also the points for ties by who achieved the time first is already in place, but people who get the same time later, e.g. on 25 mobile, can get no points if they are after 10th place

Top 10: 678 - me 615 - k200 369 - miguelg 170 - Dare 169 - Wh0misDS 149 - Niloquì 84 - Dugongue 78 - manztellen 70 - hexl 64 - Nrrillinthas

Just finished a table for PC: https://www.dropbox.com/s/5uirl0q9sn2qjor/CR%20scores.xlsx?dl=0

Notes: I haven't differentiated for ties, only put in order that are on the leaderboard, mainly a problem in the low speedrun categories Everything is case and spelling specific, also had to change one name (Bobby J I think) in order to have it be able to become a variable, so if you see any inconsistencies, please please please tell me Also this was made on excel 16, dont know if it will work on other versions. If anyone has a solution to the tie issue, feel free to let me know, or if you see a different one If you want to help keep this up to date, please tell me, all that needs to be done is changing the leaderboard lists at the top of the spreadsheet, all else is based off that.

Also turns out I only have 678 points Dare :|

Im simply stating that how fast that even occurs is entirely dependent on processing power - autoclicker clicking every frame, and my record is consistently .1 seconds behind

I do now realise that the timing wasnt a mistake, they were a frame apart, so thank you for that