I'm a person which visited this place just to check the times. I run other games, I am not interested in running this game, but I have read the rules, and some of them really should not be there.

Speedrunning is all about finding new glitches. The name "Any%" by default means the following: "Reach the end ASAP, we don't care how much of the game you actually complete" (hence the name Any%).

If you want to limit the glitches, create categories for this. You can see most of the games have some categories that limit certain glitches:

• Ori and the Will of the Wisps or Hollow Knight have "No Major Glitches" category
• The Talos Principle 2 has "No Photomode No Launching" category
• Portal 2 has "No Save-Load Abuse" category, and this category is in fact the default one

However, in all of the games above, traditional Any% category exists too as an option.

I won't even mention that the sub-category name in this game is "Unrestricted".

The only glitches that game speedruns tend to ban are the ones that create a major hardware-dependent advantage. That's why restrictions like FPS caps are very accteptable.

I will now go through every single rule and suggest an improvement to it. You may use it or not, but I personally think it will only do good for how speedrunning community of this game develops.

Rules 1.1, 1.2 and 1.5 are logical.

Rule 1.3: Make categories for difficulty levels. Make categories that allow and disallow respawns.

Rule 1.4 could have better wording: "All runs must be done on a single real-time attack, without exiting to the main menu"

Rule 2.1 is unnecessary.

Rule 2.2 and 2.6 should absolutely not be there. Spedrunning is about completing the game as fast as possible, and such skips should be a bless and something very welcome (it makes you fast, after all). Limiting such glitches should only happen in categories.

Rule 2.3: While it is boring, this glitch should also by limited by categories only. It doesn't mean it would be widely used or ran frequently (Minecraft's Any% run in-game time is less than 10% of RTA, the rest is loading screens). However, we should not take away any option.

Rule 2.4: That's what glitchless is for. New glitches should always be welcome (unless they create hardware advantage).

I can't say much about rule 2.7, because I don't know the nature of these glitches. However, most likely that rule also falls under what I said about 2.2 and 2.6.

Rule 2.5 is the only rule in this section that makes sense.

Rules in category 3 are typical game-relevant rules, nothing to be said here.

Rule 4.1 and 4.2: Simply say "video proof 30FPS or above is required". Don't restrict platforms, no game does that. You can merge 4.4 with this too.

Rule 4.3: Input display might be a recommendation, but never a requirement. Even games that use frame-perfect glitches, like The Talos Principle 2, don't require input display.

On the other hand, games usually require sound to be heard, however not all games do this, so you may keep it.

no

@quackexcmark Mybe at least tell why? Have you ever watched Games Done Quick?

@quackexcmark wow i just love when games have power tripping moderators, im sure rejecting different opinions with no explanation whatsoever is the best way to benefit the community

please don't diss me :(

So, basically main reasons and all:

1. being discussed to be added (I already started to write the rules and all for some of them such as a trueany% category)

2. just that he doesn't know the game and/or how the rest of the community feels about some of the stuff: "Rule 1.3: Make categories for difficulty levels. Make categories that allow and disallow respawns." the difficulty modes in this game don't even change anything about the map or the difficulty, beginner just adds the checkpoints and other options, and for lava mode, yeah you get it, lava. And about the respawns, if you are talking about checkpoints, well we don't accept beginner mode runs and for the other options, they are banned for various reason - however the "Previous Safe Location" option is authorized when the runner is stuck only.

3. did you really read the rules or atleast know why it's added? for: "Rule 1.4 could have better wording: "All runs must be done on a single real-time attack, without exiting to the main menu" ", we litteraly don't use RTA except for the ILs and since the beginning of this leaderboard leaving to the main menu is needed between each runs for a specific reason. "Rule 4.3: Input display might be a recommendation, but never a requirement. Even games that use frame-perfect glitches, like The Talos Principle 2, don't require input display." this has NOTHING to do with frames, and it's not like we were asking for it to like the top 50-100 or more, we ask for it to the top 10 to make sure they don't use macros or anything, which was useful cause thanks to that, we have been able to discover that a top 10 player was using a macro :)

4. for some of the stuff you bring up, like the Any% thing, you are right and like said before, I was thinking about adding a trueany% before but didn't and now I will probably create it for the next leaderboard update.

again i don't say that everything is stupid, just that most of the true stuff you think of were to be probably added soon (i know you can't guess that).

I personally don't think speedrunning is all about glitches. Some glitches break the game so much it makes running the game unfun. The categories and rules in Chained Together speedrunning community are fine and fun.

If we have category for all different ways to play the game it adds more work to mods who are not getting paid and not all mods run all categories. Every time run is submitted it needs someone to verify it. I feel like current rules and categories are fine. Only thing I would change is that game sounds should be required to make it easier to spot possible spliced runs, but I'm fine with current rules as long as I don't have to verify runs. :D

@quackexcmark I might have sounded a bit rude in my first message, which was not my intention

Anyways, thanks for a longer reply

I think the main point of those rules are the simple fact that it's not about the glitching, it's about the haxs made for this game. There's one that you can simply do a single jump from the bottom of hell and sail straight to heaven in under 3 min. I think it's actually right around 2 min and 9 seconds or something. Which by and large is not even close to playing the game. I want to say that these rules are not about power tripping mods, it's literally about playing the game normally without obvious hax in the fastest way possible.