We've seen plenty of TASed replays before here-I just took the opportunity to ask about a means of play that could create a replay that looks the same, though without any slowdown.
But seriously it's surprising that many users started to talk about my replay just because it's TA (I used only CE Speedhack 0.2~0.5), it's really like the first time you see a TA replay, THE FIRST TIME.
It's the first time I've seen a TASed replay submitted to a score thread, where the submitter said it was TASed. That's why discussion was had (that, and...)
The game doesn't slow its FPS when applying Speedhack and it thinks it's going at full speed.
But it's not going at full speed, and that's really what matters in the end. The FPS is running lower than 60, the game is just tricked into believing it is running at 60.
I DIDN'T KNOW THE RULES (YOU DIDN'T ALLOWED TA REPLAYS)[/abbr].
TASed replays are perfectly allowed to be posted, they just don't go in the score threads (and should be obviously marked as a TAS, which you did). There's no specific rule saying "no replays using Cheat Engine" because there shouldn't need to be one-it should be pretty obvious, especially with the rule about slow rate (which says if your average framerate is less than 57, it's too slow). i actually ran a short experiment a couple years back with IN spell practice, I made 15 replays, TASed some with only slowdown in Cheat Engine, and the aggregate of everyone successfully pegged every replay I TASed, even though some of the replays were < 15 seconds.
I'd say splitting the discussion off from the SA score thread was a good move, given that it very quickly got off of the topic of SA scores.
Well, you can let me know if it'll be approved or not, then simply close this theme (if rpy rejected) [2] or restore the things as they were! (if rpy approved)[1].
I may not be a moderator or admin, but I do know that the thread probably won't be locked (as discussion is happening), and that the replay will definitely not be put on the scoreboard (that said, getting a NMNB run isn't exactly the easiest thing to do even with slowdown, so kudos for that).