Why would you disable sidetricks? I actually prefer them to up or down tricks on a lot of ramps

Personally when my classic starts acting up, I just give it a good beating and everything fixes itself lol

When I checked my playstats to see how much time I have in mkw (11x days) I realized I've only ever used one controller, meaning I have over 100 days on the same fucked up classic. Probably going to get a new one soon as backup and test the rpg hop with it. As it looks now, every classic tested except Brett's gives almost consistent hop (From what we know).

You do have some good points, the rules aren't solid at fucking all.

But I disagree with the claim that disabling the dpad should be allowed when in other mk games people do things like sanding down control sticks.

Because what you did was actually modifying the game, (I think) these people are doing controller changes.

And this game is different because there is a range of controllers that people can use, whereas with other games everyone uses the same control method.

For this game I feel you have to lock it down for the fairness of the competition because different controller mods could make one controller more advantageous than others.

So what do we do about it? Honestly do not fucking know. If only we figured this shit out a decade ago instead of waiting until now, but we can't.

Nothing on earth annoys me more than the fact hibiki’s run is counted but suiryu’s is not, someone please explain. (For the record, I don’t think either should be counted)

ALAKTORN wrote on 02/07/19 at 10:13:39:


get the fucking fuck out of here

The only reason hibikis time counts is because the community started bitching about how they didn't care if the time was potentially cheated, as long as it was the fastest run. Not to mention the fact that blaze was "racist" for not counting the time, what a shitshow.

Arvo57 wrote on 02/07/19 at 11:18:45:

Wouldn’t controller mods and pause buffering be on the same page? Cuz ya know they’re both used for consistency.

You really had Bean disable shit on your controller, Sword?

JawsTheShark wrote on 02/07/19 at 13:41:43:


Kind of a shame it was Bean, the mastermind behind the anti-cheating juggernaut known as CTGP. Clearly if anybody else submitted this request to Bean, he would have denied it. Favoritism in full display

Batman5112 wrote on 02/07/19 at 14:10:19:


You mean like how Bean coded a system to have ghosts not save if My Stuff was on? Yet a run that clearly writes it on the bottom of the fucking screen is counted?



Don't even talk to me about favouritism. Don't even drag him into it.

I was at his house doing a Wiimmfi Anniversary stream or some shit and my controller was acting up. He offered to open it and see what was up. I told him the buttons kept sticking/inputting when they shouldn't. He put tape over them. You act as if this was some intentional masterminded plan used to fool people. Like I did it to gain some kind of inherent advantage. I just wanted my controller to stop fucking me over.

He may not have even known I was going to use it on Time Trials. It was my only classic at the time so it was either use a defective piece of shit or find a new one (which at the time, were inflated to fucking hell)

I find it amusing that this always happens. People try to make some rule about one thing, then it derails into some other kind of thing. If it'll really help you sleep easier at night, remove my SGB time. But I guarantee you there are countless more times hiding in that page where people have done stuff to their controllers; to gain an advantage or not.

There was a HUGE misunderstanding here, I was under the impression that bean gave him some code back I 2011 that would disable the other dpad buttons. I had no idea he was just talking about taping the contact down to make his controller usable again when he was playing it in 2017.

Seems like a lot of other people were under this impression too, so yeah things got a bit mixed up.

Regarding controller mods:

I think controller mods are fine as long as they are not electrical (e.g. remapping buttons or changing the output signal of the controller).

Putting on tape to prevent D-pad inputs seems fine imo. As Sword said, this is not too different than what's allowed in SMK/MKSC with regards to modifying the D-pad.

But doing something like rewiring the controller so that the side D-pad inputs instead give D-pad UP inputs shouldn't be allowed imo. Since then mashing diagonal could give you more chances at chain wheelies.

Regarding pause buffering:

Bryce729 wrote on 02/05/19 at 18:46:00:


Sword wrote on 02/07/19 at 14:15:06:


Winbag4 wrote on 02/05/19 at 21:04:07:


These are are all similar points, and I think this is the main reason why some people are against this rule.

IMO it is always up to the competitive community to create the best ruleset to maximize the enjoyment and competitiveness of a game. To me, that is better than having rules that perfectly match with what's possible in-game, but I see why some people disagree.

I have already given this example, but imagine if MKWii also had the MK64 timer glitch, where you could leave your console on for days to get faster flaps. Since flaps aren't played as much in this game let's say this also worked for 3laps (e.g. pausing at the beginning of the 3lap for a few days causes the timer to move slower when you resume). It's something possible in-game, so if we make our rules based on what's possible in-game then it should be allowed. Hunter offered an explanation that this kind of thing shouldn't be allowed since it's a "glitch". But aren't we supposed to allow everything in-game, since everyone can do it and is on a level playing field? To me, I can't see why any competitive community would want to allow something like this where they have to take multiple days to do one attempt. Therefore, allowing everything that's possible in-game seems like a bad strategy for making rules.

So then the question is whether pause/HOME buffering negatively impacts the game enough that it warrants banning it. In my opinion, it does. I feel that pause buffering takes away from the spirit of TTs, since TTs should be driven in real-time. Pause/HOME buffering takes away many aspects of skill from the game, such as timing, input speed, consistency, alignment, reaction time, etc. Overall it would be less enjoyable to compete in a game with widespread pause buffering, and I think many of the top players would agree with this. MKWii with widespread pause buffering is almost like a completely different game that is more akin to doing TASes on Dolphin. Those runs are impressive in their own right but it's generally different types of skills being tested there. I think we should stick with the type of game we already have (real-time TTs).

I am convinced that banning pause buffering is the best course of action for the long-term competition in this game. Brett feels the same way which is why he wanted to give up his own WR. The poll (even though it was 2 years ago) also shows there's many people who don't think pause buffering belongs in competitive TTs.

Many games that use IGT (in-game time) or high scores ban pause buffering. I looked at Cyberscore and "pause abuse" is banned for most games. There are some that allow it though, for example the Smash Stadium games seem to allow it (homerun contest). But imagine for example playing a score attack on a fast-paced puzzle game. If you were able to pause every few frames to give yourself infinite time to plan your moves it would basically trivialize the competition. A similar concept applies to MK. It takes away from the spirit of the game and the removes the skill involved.

Other MKs ban techniques that are only possible with pause, even though they are apart of the game (SMK/MKSC). I imagine that the other MK games wouldn't allow pause buffering either although they probably haven't had the discussion like this thread.

In RTA (real-time attack) Speedrunning, it's a bit different since pause buffering has a tradeoff between losing RTA time by pausing and saving time in-game using the buffered inputs. So there's more strategy there, and I can see why most speedruns allow it. In IGT and score-based games pausing can be way too anti-competitive though, since you can pause as long as you want without losing time/score.

Sword wrote on 02/07/19 at 14:15:06:

I see your point but I also think that a fully HOME buffered 1:17.8 on MC3 wouldn't feel like a real WR in the eyes of many. It's better to handle this situation now before it gets out of hand.