Here is the run this post references: UV-Pacifist in 01:09.430 by BigTWONeli - Doom (Unity Ports) - Speedrun.com

To provide context:

You submitted a 1-minute UV-Pacifist IL run that neglected to follow the rules laid out for non-Any% runs - specifically, you quickloaded to a death save to start the level (there is a long paragraph in the ruleset detailing how you can start runs on non-Any% difficulties; quickloading to a death save is not allowed and never has been). Instead, you posted a secondary link of the entire recording (~11 minutes), of which 10 minutes were failed attempts. As I said in the rejection message, it is not the moderators' job to review your entire recording and ensure that you did didn't quicksave at any point and/or tamper with your initial save.

Quite frankly, the length of the recording does not matter - the moderators are not obligated to cover for you, regardless of how much extra footage you link. Your run did not follow the rules, and thus it got rejected.

If you were to submit an 11-minute run, then absolutely, it is the moderators' responsibility to review the run in its entirety. But it is not the moderator's responsibility to review your entire recording (regardless of length) because you chose to ignore the rules. Making a public post like this in which you omit crucial context is incredibly disingenuous and embarrassing.

One correction: The run did not start via a quickload, it started via an actual death. However, this still does not comply with the ruleset, which states that there are only two valid ways to start a non-Any% run:

1. enter from the main menu, or
2. load to a (normal) death save after showing save info.

Dying and restarting the level is not a valid way of starting a run for this board.

I apologize for incorrectly stating that the run used a quickload, but that doesn't change the fact that you did not follow the rules for non-Any% runs. As such, your run got rejected. Everything else in my initial post still holds.

It is not stated in the rules for IL that you cannot die and restart. it is stated in the IL rules that I cannot load from a death save, which you already stated I didn't. It's fine if that was supposed to be a rule but In the rules section it is not specifically stated that I cannot restart via death. It should be stated in simple terms on there that I cannot do that.

"If a run on UV is loaded via a quicksave, it will still be rejected" This is referring to starting a run on UV from a death, using quicksaves.

Also in the IL section of the rules has this

Which means you are not allowed to restart from a death on any other difficulty besides any%.

The only time you are allowed to start your run from a death on UV/UV+ is from the pause menu's save/load system.

It is indeed stated very clearly that you cannot start from a death on UV, you are just misunderstanding. And to add, it's absolutely not the mods jobs to sift through 11 min of failed attempts just to find where you're difficulty was shown. Start from the main menu, or use the pause menu in game system like everyone else. It's not hard at all.

I'm also confused as to how sorting through 11 min of failed attempts is ensuring fair play... That doesn't even make sense lmao

It needs to be stated clearly in the rules "restarting from death even without saving and loading is not permitted on anything besides any%" it isn't state anywhere. you showed me things that are already known. I did not load from a save, I did not save at all. during the run I died and restarted the level via death.

Honestly, BigTWONeli, you're right - the rules could be a bit more specific, and I'll look into making them more satisfactory. However, there are some things I want to lay out.

The reason I assumed your run started on a death save is because your primary video does not show you dying - it starts with you already dead. From this point, it is a common assumption that this start is via a quickload to a death save; this is also an effectively correct assumption since it makes no difference whether you actually died or just loaded a death save, since RNG tables reset once you press space either way.

The only real distinction between a quickload to a death save (or equivalently, an actual death) and a manual load w/ save info displayed is... well, that the save info is displayed. The immediate (and that's key) display of the difficulty information is the only reason we require the save info to be displayed for non-Any% difficulties. Again, your actual death can be treated the exact same as a quickload since, for speedrunning, they are the exact same thing.

The reason immediate information is important is for the same reason I rejected your run: it is not the moderators' responsibility to look through an entire recording (regardless of length) to ensure fair play (viz. discreetly choosing a different difficulty at some point). However, if the information is immediately displayed, that saves moderators a heck of a headache and shows beyond a shadow of a doubt what difficulty the player is on. Quickloads to a death save (and, again, actually dying and restarting) do not display this information, at least not immediately.

TL;DR: your run can effectively be treated as a run started via quickload to a death save, as can any other run in which the player dies and restarts the level. I can make the rules more specific to lay this out in plain language, since they are kinda pathetic in their current state imo.

Edit: I have since updated the rules to be more specific. Honestly, I think the changes I made are kind of pointless and self-obvious, but that should be the point of a ruleset anyway: lay everything out for the sake of pedantry if nothing else.

I see the problem now.

Note: This still means if a run on UV is loaded via a quicksave, it will still be rejected.

This SHOULD say;

Note: This still means if a run on UV is loaded via a quicksave, or started from a death in any other way than what's stated above, it will still be rejected.

@Thomastd You might wanna change that. That's on me. Sorry.

However, this changes nothing. Runs on UV are still not allowed to start from a death, unless it utilizes the pause menu load system, to ensure difficulty is correct. Sorry for the inconvenience. I am the one to blame, not the current mods.

To add, the biggest reason we don't allow long ass videos for 10 second runs (not that this is that), is because people in the past HAVE submitted 7 hour long highlights for a 9 second E1M1 run. Shit like that is unnecessary so we require that you cut your video down properly, and show difficulty before every run (excluding any%) so we don't have to waste our time searching.

That’s fine. Just a little irritated that it wasn’t specified. All good, I’ll do it again and resend it. Thanks for being so responsive :)

It was in the past, when we discovered the pause menu stuff, I was the one that changed it, and forgot to respecify it. Figured the note was good enough. Completely on me I apologize.

Jeez I missed something

What if you died and restarted but you showed the whole footage of you level and difficulty selecting before it, like if you difficulty/level selected, died, and then finished your run in one video?

The short answer is that it wouldn’t make much difference - it would be rejected as it is in violation of the ruleset.

However, it honestly depends. The practical reason for rejection (the reason for the rule in the first place) is that, as previously stated, it is not the moderators’ responsibility to watch your entire recording to vet and verify a single run. Now, if someone’s recording was just, for example: level select, first attempt, die, respawn, second attempt, succeed; then this would maybe get accepted since it’s not too much of a headache to verify (though keep in mind that this is the exception, not the rule).

As with most of the rules, the final call is up to moderators’ discretion. Legalistically, a run in violation of any of the rules is not entitled to be accepted, even if the violation is minor or petty. However, depending on the moderator’s (singular since typically a single mod reviews a given run) discretion, the run may be accepted anyway if the violation is insignificant.

Unfortunately, this may cause inconsistencies in the enforcement of specific rules if unchecked, which is a reason for coordination among the mod team. If you experience run rejections that you believe to be unfair or inconsistent, feel free to let one of us know (preferably via DM), though we try our best to keep these incidents to a minimum obviously.