Friesland, NetherlandsI would like to add that you're not the only one who shares these opinions. Not everyone was/is a fan of death clipping. This is why we have split the categories into 4 separate levels of brokenness after a long conversation in the community. This is arguably too much for a game that doesn't show thát much activity, but at least this way there ís something for everyone. I think 'any% no save glitching' would be most up your alley: https://www.speedrun.com/unreal1/full_game?h=Any_No_Save_Glitching&x=9d8jr9qk
As for the rule clarification: That seems good and I'm happy to implement it. Extra clarification is always good.
I moderate the ODC boards. When a run has no ms specified (null value), that run will be scored a higher position than a run that does have ms specified.
This is unfair, because this allows runners to gain positions simply by not showing the MS on the in-game timer. I feel rejecting these runs goes too far, but now I have to put an ugly '999' just to push a run to the bottom.
The answer to your question can be found when you press the 'view rules' button for Any% Console:
"Since these consoles have no In-Game Timer, no IGT is to be submitted. Use Real Time only. Because of this, timing may stop at the start of the final cutscene, rather than the end."
Please read the rules again to ensure your submission is done correctly in the future
Mod Note:
- Run is missing the initial loading screen. Please show the initial loading screen. I will let it slide this time.
- Video time is submitted instead of actual run time. Gonna leave the excess time as compensation for the above point.
- Game Time submitted as Time Without Loads. Rectified.
Mod note: Submitted time was horribly off by more than a minute, rectified.
Mod note: Console runs do not use IGT. RTA was 10ish seconds too high. Rectified
Mod note:
- IGT has erroneously been listed as TwoL. This has been fixed.
- TwL was missing. An attempt at fixing it was missing, but the menuing before the run is missing. Taking the time of the part that is visible and adding 20 seconds.
Mod note: Removed specified time without loads, corrected mistimed time with loads by 15ish seconds.
Mod note: IL runs use in-game time. A real time was submitted. This has been corrected. (The ingame timer in the top left is not shown, so the time displayed in the menu is used instead)
Moderator note: No IGT in top left corner enabled in settings. Using menu-displayed top time instead. This was not submitted correctly. However I have fixed it.
Moderator note: Time was submitted as IGT instead of Tw/oL. Fixed.
I would like to draw attention to the timing section in the rules and instructions for the leaderboards again. I am getting a lot of incorrectly submitted runs.
Real Time (with loads) for full game runs:
Timing begins when the 'Yes' button is pressed on the 'are you sure you want to start a new game' prompt.
Timing ends when the cutscene where the chef screams 'no no nooo' is skipped and the map ends.
Do not submit miliseconds for this time.
In-game time for full game runs:
This is the time listed in the top-left during the credits in the cinema and does include miliseconds. It can be enabled in the options menu. This time can also be used for ILs (the final miliseconds tally will be visible briefly during the level ending fade).
Real Time without loads:
Leave this blank. Speedrun.com breaks if it is disabled.```
And the addendum for console:
```Since these consoles have no In-Game Timer, no IGT is to be submitted. Use Real Time only. Because of this, timing may stop at the start of the final cutscene, rather than the end.```
Note:
Real Time (with loads) is NOT equal the length of your video. The video of your run should end up being slightly longer than this time as you show the menu at the start and the credits at the end. It is also NOT the time on your livesplit when you fail to stop it when the run ends and you leave it running for 2 minutes after the run is complete.
I understand runs being mistimed by 1 or 2 seconds, but I'm receiving runs that are mistimed by up to 20 or 30 seconds, sometimes even multiple minutes. These mistimed runs amount for perhaps as much as 50% of all submissions. Put some effort into this. So far I have fixed these issues myself when they showed up, but one day I will be in a foul mood and simply reject your mistimed run.
If you spot a mistimed run on the leaderboard, do not hesitate to let me know.
Some rules, particularly with regard to timing, have been altered slightly to reduce the amount of homework one needs to do when submitting runs.
All previous runs have been changed to reflect these rulechanges, and where applicable grandfathered in. Around 5 runs previously on the leaderboard have been rejected due to providing too little information to work with (eg no vod and no time submitted.)
To summarize, these are the rules changes: Timing will be done with 'time with loads / real time' and 'ingame time'. All consoles that support IGT must specify the IGT as listed during the credits sequence (for full game runs), or during the fade/circle to black at the end of ILs. This includes miliseconds. PS4/XBone does not support such a timer, so only real time needs to be submitted.
DO NOT BOTHER TO TIME WITHOUT LOADS YOURSELF. You'll just be wasting your precious time, do more runs instead ;)
Note: IGT includes the final cutscene where Chef screams 'no no nooo'. From now on, it is highly recommended you skip this cutscene for extra speed.
Real Time: No clear rules were specified in the past. A small community poll in the Discord server has established the following start and end points for the run:
- Start: When pressing Yes on the New Game confirmation screen.
- End: When the 'no no noooo' cutscene is skipped and the last map ends, in synchrony with the IGT timer. (Yes, this means that the final cutscene is now INCLUDED in the timing. Immediate skipping is recommended.) From now on, this will be enforced. Past runs have been given quite the leeway when it comes to this, which could cause inaccuracies of up to a dozen seconds between runs.
No Real Time needs to be specified for ILs, for both Console and PC. Instead, PC/Mobile runs can use the IGT as shown in the top left, and console can use the top times as shown in the level select screen. Please ensure these are visible at the end of the video.
Furthermore: I'm considering removal of the Shorts category. These two maps have been given their own IL already instead. For now, I'll leave the category until I decide, but it currently uses only real time, and no IGT.
All rules have now been written down in the game rules for quick future reference. Press 'show rules' at the top of each leaderboard.
I do not check these forums often, and I will forget I posted this. Please join the Discord server or contact us by other means of your choice if you have any questions. Thank you, and happy running! RBRBRBLRBLRBLRRBL
Speedrun.com's filters option already allows for filtering out PC runs. A category split between yes and no caves noclip seems excessive at this moment considering the inactivity of the game's speedrunning scene, but might be worth considering in the future.
Yes, I verify runs whenever Speedrun.com does not lock me out of my account and I have some free time. Feel free to nag me about it next time.
Interesting. A load remover timer might be needed if this turns out to become an issue.
