North Carolina, USAAlright, Timmi broke the "meme replies only" boundary, so let me hop in here.
Can you cite a specific grievance? I ask because when I think of how someone might say "a casual player", it seems to me like they would be describing ¤¤specifically¤¤ a casual player, and that the false dichotomy would be in that case in your own head. We know that there are other ways to play games. We aren't blind to the rest of the world. There is high score play. There is restricted/challenge play. There is marathon play. There are speedruns. There is relaxed, feet-up-on-the-coffee-table casual play.
Everyone has a goal when they play a video game. For speedruns, it's to go fast. For score runs, it's high score. For casual play, it is to have a fun time. What in that description feels offensive?
Do you find the term "casual" triggering? I play tons of games casually. It isn't a "four letter word". No one is trying to insult by calling something casual. Who are we protecting here by erasing "casual" from our vocabulary?
The opposite of "professional" isn't "casual", it's "amateur". Some semantic policeman you are.
Yellow is too much talking. I can't deal with that. Definitely does not roll deep.
I gotta word this. Gonna have to go with the tried and true RGB. Red #1 (kick ass transformations like a motherfuckin dragon or some shit), Green #2 (this shit right here makes the speedrun go round), Blue #3 (free EVO points? uh, sign me the fuck up!)
What volpe said. There is an important distinction. The cloud isn't acquired via ACE. Acquiring cloud leads to an unavoidable ACE that we don't make use of. The community has chosen to allow this distinction in an effort to encourage innovation, since many chuck-eat glitches result in ACE.
You can filter them via a pulldown menu at the top if you want to see, but we don't separate them into subcategories. The category is 11 exit, irrespective of what glitches you do. The "run type" field is just so that you can see at a glance what method was used. 10:50 glitchless is far more impressive than 10:50 cloud, so it is nice to have access to that info.
Frikkinfriks14, I remember you. I really enjoy it when people who don't speedrun SMW try to tell us what should and shouldn't be a category.
The decision was made (like 2 years ago) that we didn't feel like the category should only be completeable by way of a glitch. For reference, that same exit could also be obtained with the orb, since that exit is considered DGH's normal exit. In general, it is more faithful to the spirit of the category to leave it as 95 exit.
If you were interested in running a 96 exit no cape category, that would be fine, and I wish you all the best. It just wouldn't replace the historical 95 exit category.
Everyone knew you could beat the game from Week 4. It's just unbelievably uninteresting. But if you're having fun, go nuts :^)
The rules for Any% No EG have always stated "Start from Week 1 and go till you defeat Ganon."
Seems strange to change the rules for the established category out from under old runs. At least make a new category if you're just gonna run Week 4 only.
I've been summoned.
I've never heard of anyone doing this, but the generally accepted answer is more of a philosophical one: if it doesn't allow you to do anything that can't be done on stock hardware, than it should be allowed. It is this rule that disallows turbo controllers on almost all consoles and overclocking your NES (which is something I've never actually heard of anyone doing). So to apply the same logic to the issue of moving the power/reset buttons to a controller, (in my opinion) as long as it isn't giving you an advantage with a game perhaps that would have you mash the reset button quickly or something (not that I've ever heard of that being a thing, just giving an example) and is purely for your own convenience, I'd say go for it.
Yes, and it became unclear, so we changed it.
11 exit means 11 exit 0 exit means 0 exit (credits warp)
Just for the sake of clarity, SMW doesn't use terms like Any% or 100% (and we only use Low% for tradition, sorry Rezephos)
Thanks. Sorry if I got frustrated, but keep in mind that the timing rules really aren't important, definitely not worth clearing a leaderboard for. :)
#1 There is no reason to change the timing method again. Selecting "Story Mode" makes the most sense for the timing start (like selecting 1P/2P on Super Mario World, which is SRL standard). SRL/SDA "standard" doesn't matter. SDA "standard" is start of control to end of control, which you haven't made better, you've made worse. SRL doesn't have a "standard", but it's usually just last menu selection, which is "Story Mode" in this case.
#2 You don't delete runs because you make up new rules. You re-time the runs. Deleting runs because you want to add one extra menu press makes no sense. Please fix this back to the way it was.
Lower the encoder settings to make your OBS recording lag less. A few dropped frames isn't a big deal. Most people stream/record at 30fps anyways. If you find it difficult to record both together, then don't. Record your game alone, time it yourself, and we can re-time it to get it right.
