I wonder how many people have actually read things I linked.
The word
clear was used 5 times in this thread to indicate how
clear chatty branch labels are. The movie I linked above (
1944M) once had branch label "no null sprite spit, no stun glitch". Because people who gave it that branch believed that it was
clear. The fact that they were vested editors, not judges, doesn't help. When admins saw that branch, it was
clear to them, that things can't go that direction. Interestingly, despite of hearing from a lot of users how
unclear such branches would get in the end, people changing them believed that they were
clear too strongly, so no one was heard until it was too late.
A huge
conversation was spawned, and the result was that neither "X", nor "no X" is what the majority prefers. There was no majority. The community exactly halved.
When 2 such camps have contradicting opinions, forcing any of these opinions disrespects half of the crowd. So we abstracted from the dilemma and switched to the approach that doesn't enforce any side. We started simply relying on statistics, labeling explicitly things that are uncommon and options that are equal. Why blind statistics? Because
clear is subjective, and it can't be used as a reason. Each camp I mentioned considered their preference to be
clear.
Memory corruption is an uncommon category, because it's hard to pull off. Branches utilizing that technique usually have the
major skip glitch category as a result. It's also uncommon. Additionally, some people really hate game breaking glitches, so considering such branches any% isn't perfect. So we retired the concept of any% from branch structure altogether. It only matters for deciding Vault eligibility. Blank branch doesn't correlate with any% anymore. Why? Because any% is subjective as well.
So how do we apply the branching rules here?
As explained above, we don't have to mention forgoing the major skip glitch, because using it is uncommon, so forgoing it is implied. And it has only happened once that we had a game with
two major skip glitch branches at the same time:
[1978] SNES Super Metroid "X-Ray glitch" by Cpadolf in 21:25.12
[2558] SNES Super Metroid "GT code, game end glitch" by amaurea, Cpadolf, total in 14:52.88
With that exception, even within one game, there is only one major skip glitch branch, and all others avoid that tech. So yeah, it's use is uncommon, can be considered an exception, and doesn't need to be mentioned in the branch label explicitly.
About "phone numbers". Again, we need to check which option is common, or if they are equal, mention both. So far there's not much to choose from, this is only the second branch. This branch avoids phone numbers, the other one uses them. Since it's not a password system, but more of a helper, it can be arguably considered a legit technique. But the RTA doesn't. So I'm not sure what to do.
What if we simply mention this decision in the movie description? After all, not every little aspect necessarily goes to the branch label, and whenever there's possible clutter, we can use movie description to explain the exact set of rules. It is what happens here for instance:
[2339] SNES Chrono Trigger "completionist" by Saturn in 5:44:58.18
How much time would be gained in this submission if phone numbers were used?
