Not sure why this is happening though.
In level 1, you neglected to keep going over the edge at the end?
In level 3, isn't it beneficial to walk on the carts so they start moving, giving you a boost? I don't remember if it works like that.
You bumped into a wall after bouncing off a penguin. Can't that be prevented?
I think some lag can be reduced if you opt to take the time to kill enemies.
Brock Through Walls is memory corruption (game reads a ton of unrelated values as cutscene walk data). The precursor, Brock skip, is not.
What I'm getting at, this submission would be a blank branch by our standards. Note that blank branch not equal to our definition of any%. We do not explicitly highlight any% in any way, because it doesn't help with organizing the branches. So when labeling runs, we rely on statistics instead. If a run sets unique goals that other runs don't, we put them in a label if such goals are actually rare overall. "ACE" is a rare category, hence we call it out. "No ACE" is not a rare category, it is overwhelmingly common through the whole speedrunning community. Hence in the case of this submission, we don't need to say "no ACE" in the branch: it's so common that it's implied. Same about SRAM or memory corruption. They are rare, avoiding them is common, no branch label needed.
However, this doesn't mean that the actual goals of this movie are arbitrary. In no way they are. They are quite common, and they were what the overwhelming majority of the runs were for games where no memory or SRAM corruption techniques were known. But then they were discovered. Does that mean the whole branch that avoids them is effectively dead? Of course not. As long as people keep competing in it, and as long as it features unique TAS content, it's alive.
I disagree with the assumption of difficulty in defining glitch. The "glitchless" category used in the RTA community is based on a very straightforward definition of "no arbitrary code execution."
On the other hand, trying to follow the intended sequence of the game would also necessitate beating Erika before Koga before Sabrina before Blaine, which has never been suggested as a requirement for glitchless Pokemon runs before by anyone, classic or no classic.
I do understand the desire to not publish competing classic and non-classic runs that have very similar category definitions if they both existed, but for the moment there is no classic category TAS.
Not specific enough tbh. In some situations it might be a glitch and other situations it might not. Depends on the exact kind of movement required to pass through.
Can you really draw an absolute line through intended sequence vs unintended sequence? For plenty of games, the intended sequence itself is unclear. Sure, this particular instance seems pretty clear but there are many games where it is not, and developer intent is largely ignored anyways.
Again, I would describe this as a sequence break rather than a glitch. I'll give you an example in another genre. If a developer intends you to not be able to make it across a gap, but you can still do it with a tight jump, is that a glitch? I wouldn't think so.
We have the co-op diploma Red/Blue branch that maximizes game content (including going through the Rocket Hideout), this should not be an issue.
I don't see what intended methods of game progression has to do with whether or not something is a glitch.
The fact that this is a sequence break does not seem relevant to the branch goal.
Would using a pokedoll on Marowak after using silph scope be allowed? According to the glitchless classic rules it would not be allowed, but it has nothing to do with event sequence in that case, which was your primary argument.
My interpretation of RBY "glitchless" has always been "no memory corruption", since that conveniently handles unavoidable glitches such as 1/256 miss and Viridian Forest no-encounters oversight. Then using the Poke Doll on Marowak and the (fixed in Yellow) Bike Shop keep-instant-text oversight don't count as memory corruption.
i know that my tas isnt good enough. its just my first tas.
Hello, Is it normal a submitter can vote for his own movie? One vote can change everything in the mind of judges to say if a movie go on Vault or on Moons x). I don't log in automatically if it's a bug.
Click