So the debate is really whether (a) Masterjun's run should be unlabeled and Bahamete's run should note that it avoids the credits glitch, or (b) Bahemete's run should be unlabeled and Masterun's run should note that it uses the credits glitch, or (c) both should be called something else.
The branch name needs to be clear, it should not allow any interpretation.
The main issue with glitched/any% categories is that it would lead to very ambiguous 'low-glitch' categories. For example‚ if someone ever makes a 'no memory corruption' OOT TAS (i.e nom RBA/WW)‚ how would it be labelled? I mean‚ it wouldn't be the most glitched category‚ but it would still skip 8 of the 10 dungeons of the game. So the best category name would be 'no memory corruption'‚ i.e actual naming convention.
As a very simple example, we know from physics that the kinetic energy is equal to 1/2mv2. Does that mean that lurking behind every moving object is a square with a side whose length varies proportional to the velocity? Or perhaps even more to the point, I know that when I drop an object from a height h, its speed will be v = sqrt(2gh) just before it hits the ground. Does that mean that "somewhere" there is a square I can draw with great physical significance that has a side of length sqrt(2gh)?
I completely understand and agree with having movies that show off more gameplay than the fastest run. But here's the problem: for almost any speedrun on the site, it is possible to make an alternative run that shows off more of the gameplay. However, in many cases these would simply be (1) suboptimal and (2) arbitrary. So how does one distinguish a "non glitched" run from a "suboptimal" or "arbitrary" run? We need to be able to answer that to stay true to the site goals. Even in the few hours that this thread has run, it already has half a dozen different definitions; that doesn't help.
Tool Assistant maybe?
One says that the smallest pixel on the screen is only blue, yellow or red, the three primary color. His reasoning is that, since a computer screen is like 1024 X 768 thingy, that means there is more than 700 000 pixel to color. And if we assign a different color to each pixel, the amount of information is huge. Why don't we see only in blue, yellow or red on a screen? it's because the pixel are so small the eyes can't distinguish it. With yellow and blue (50% 50% for example), in a certain region, we should see green. etc. One says that, sionce we can color green on a single pixel with GIMP or photofiltre, a pixel is not necessarily only red, yellow and blue.
Good, so it's the subpixel that are blue, red and green!
Wait, I'm confused. What if the current movie gets obsoleted by a run that doesn't use...whatever the heck happened here but ends up being very dull? Does that mean separate branch, rejection or moved to vault? :o
Just so you know, Bobo the King, Javascript only has to be syntatically correct to compile. Unlike a language like C# or Java, and like languages like Python, it can attempt to call non-existent methods, manipulate non-existent fields or variables, etc. and the code will fail (sometimes silently!) at runtime.
What exactly is "me"? The player? If so, that seems redundant and confusing.
Could I see that solution? I gave a similar solution a try, but wasn't able to make it quite so short.
it's mostly you trying to enforce your vision
You whine and whine and whine
He wants to (in the poll), be able to express that while he was not entertained, he found the movie to be high technical quality (or not).
Too long, didn't read.
