Wow... you could have destroyed my time with a better blue platform cycle during the ending! Quite impressive an impressive run.

Well, that was surprisingly easy! Thanks for agreeing without any argument :)

I'm so glad that you agree! Hopefully @MichaelChan will as well.

@Swskrei and I have extensively discussed the matter of @Krackerz's AAL15 run, and have concluded that his run was falsely rejected. We are both experienced TAS makers, and this run looks nothing like one. We know that he could have made it look more "human," but if we use that logic, then every run could be TASed. Your only evidence is as follows:

I'm not sure if you made a TAS before, but that's not how it works. A TAS doesn't have to wait to perform a spike edge; they can keep going like what @MichaelChan says is normal for a human. If @Krackerz really is this TASer that @MichaelChan says he is, then wouldn't he not stop during a spike edge to throw off suspicion?

Additionally, this piece of evidence isn't true at all. The only times that @Krackerz stops for a spike edge is the first one, (which @MichaelChan himself and I do as well) and the third, which @Swskrei, @MichaelChan, and I do the same. That pixel perfect would be much harder if you held left the entire time. His other spike edges are done "normally."

@Krackerz only slightly stops; he still has momentum. Again, other people have done similar things and @MichaelChan has still verified their runs. For example, in @DapperScratcher's AAL14 run, she basically does the same thing, but with even less momentum and more pausing. Everyone plays a bit different; just because other people's spike edges aren't the same as your spike edges doesn't mean the run is invalid.

There's really no good reason to doubt @Krackerz's run more than anyone else's. It's not like he just randomly got this without any prior runs; he had a less optimized time before he got his 19.7 run. He's clearly a great player who has gotten a bunch of incredibly optimized times. It's simply not fair to reject this run when there's no clear evidence of it being a TAS. It may look like a TAS to @MichaelChan, but honestly, when one puts such a large amount of time into a level, they start to look like one themselves.

So, @MichaelChan, please reconsider your decision. You know how it feels to pour hours into a run, only for it to be rejected, even though you didn't cheat. The same thing happened with some of your runs. Unless @MichaelChan can provide better arguments than the ones listed above, @Krackerz's run deserves to be up on the leaderboards.

I'm sorry, but your argument seems to be undecipherable. The logic you use to come to this conclusion is seemingly nonexistent!

@Swskrei already provided a numerous great counterpoints to yours, although I'll add a couple more.

For your point regarding "he cant beet my time," just because someone has beat your speedrun does not mean they are a cheater. Swskrei has grinded 100+ hours on the Appel for his runs, and it is unsurprising that his times are more optimized than yours.

Additionally, your image "evidence" is quite misleading. You only screenshotted a small portion, if you would've read the rest of his post, you would have noticed that he was merely providing an example. Please keep this in mind if this happens in the future.

You need to provide much better reasons to call Swskrei a cheater.

Agreed... there's no foolproof solution; smarter cheaters who are better at coding will always find a way to get around them.

Well, that's fair. I was simply suggesting that cheaters might use this forum to TAS their runs undetected.

Honestly, I think the "past runs" strategy is the best we have. I mean, there's always the off chance that someone didn't have access to speedrun.com or simply didn't want to join, but they still speedran Appel.

Firstly, considering that there is no way to figure out if someone is cheating using TAS or not, this simply helps cheater instead of hurting them.

Secondly, you can't just import the code from Appel TAS Maker into Absurd Appel. Even if you tried to just copy it by hand, the variables are different and it wouldn't work well.

Thirdly, yes, I know any four characters will satisfy the replay. However, since the cheater in question would add random "l's" and "j's", meaning that they would not follow the same rules that Replay Codes do. However, this does not matter much, since we wouldn't be able to tell the difference.

Lastly, I actually have nothing to counter this. If what you say is true, my third point is countered as well, since you don't actually have to add any characters.

Well, not to be too much of a downer here, but I'm not sure it was the best idea to share it with the community. Now, anyone who is skilled in making TASes can use this strategy... as you said, I'm not sure if there's a foolproof solution to this.

One thing we could do is study the beginning of a Replay Code. You said that you can delete "TAS_" from your username, as long as you add an equivalent. The cheater in question would be forced to add random "l's" and "j's", and they could be a sign of a cheated run if they do not follow the ordinary rules of a Replay Code.

...although, I have no clue what the beginning of a Replay Code would look like, so unless someone can figure it out, this is an unusable solution.

Lastly, about the run by @Krackerz, I don't think this is proof that his run was TASed. His Replay Code included "R's", meaning that there is no way that one is cheated, since the Appel TAS Maker uses "l's" and "j's."

What are everyone's thoughts on this?

Well, since speedrun.com measures by milliseconds, I will as well. So, I just say that the TAS and I are tied.

Anyway, your WRs aren't getting "DESTROYED into the dirt!" They're just a bit outmatched. I'm sure you can tie this time with a bit of work!

Also, if you continue speedrunning, you'll be able to beat all of my times, since this is my last run!

Are you just going to keep tying Luis_sm for every level!? This is crazy...

Already a WR!? Great job!

Fun Fact: You've tied both of Luis_sm's PBs so far!

Honestly, a really optimized time! You would've saved so much time if you waited for the proper cycle, though...

Well, I can't say this was an unexpected, but great job!! I'm not going to comment on all of your new runs, but all of them are insane! If you need me to post any more runs, just ask :D

Also, I don't know if I will, but I might try and beat this time.

Sidenote: Just so people don't get confused, Swskrei made a typo. I didn't beat it 12 hours before Swskrei! I just beat it in 1 or 2 hours less.

I've never seen you before, and you come out of nowhere and get two good runs? Impressive.

Also, in response to the mode note, that is quite strange that you have to use turbowarp to view the run. I can view it on scratch just fine.

You're so good that you accidentally got a new PB!!

For sure! I always thought it was a bit unfair that people who could click faster or just had a better mouse had an advantage over others.

Personally, I think it would be better if you could wait at the start, for better cycles. It'll make the category more fun and interesting!

I tried it myself, and while it is really fun, it might not be so fun for speedrunning. However, I think that a remix would be quite fun, especially if you make all of the levels possible!

I would definitely play it.

Yes, the time is 21.1. Sheer destruction of this time.