GermanyThank you, Info, for your work as a mod over all of these years. Lots of decisions had to be made and lots of responsibility had to be taken to guide and maintain our community. I'm happy, you have taken it upon yourself to invest so much time and effort in our beloved freetime activity. gg wp
Hey there,
sorrily I'm not aware of Scripted with savewarp strategies for this game. I've never done it myself. You might wanna try and get in contact with Bloodvez or Fodder directly and ask them.
Regards qd
Change of Individual Level Setups
Change: For the Individual Level leaderboards new Setups have been made.
The Individual-Levels-Runs (ILs) have formerly been done by executing Configs, placing the player in the first map of the chapter, giving them all the items they could have acquired until then. You were not able to setup your entry into the chapter like you would do in a Full-Game-Run; in Nihilanth, you didnt have a suit; in many levels, you either had too much armor, or after IHD did not have enough Health. For these reasons, the Individual Levels were far from the actual Full-Game-Route, which made them less appealing to a lot of runners. These IL-Setups are now called "Legacy". Runs done for these setups will remain on the leaderboards with an according mark (Legacy).
To make Individual-Level-Runs more appealing, new Config- and Save-files have been made and uploaded to the resources (named "Individual Levels: Configs and Saves") to closer resemble the actual Full-Game-Route. Under the IL-Label "Current" you can now submit ILs using this new Setup.
Setup: Place the Configs in your valve-folder, place the saves in your SAVE-folder. When in the game, execute the configs by typing "exec <CONFIG-FILE-NAME>.cfg". The map before the according chapter will load to give you time to prepare, and demo recording will start. The timer will start when entering the chapter, and the timer and demorecording will automatically stop when finishing the chapter.
You can reduce the weapons, ammo, armor and health given in the configs by changing the values; but you must not increase them past the limit given in the config. Reaching stop triggers before the end of a chapter makes the run invalid.
The configs and saves have carefully been prepared, but have to be tested further and might be adjusted.
Thanks to Kananga and nyddesson who came up with this new method for setting up ILs.
Allowance of all -commands, -bxt-commands and bxt_trigger_setcommand
Rule change: All the -commands (normal HL-base-commands with a "-" at the beginning, and all -bxt-commands) as well as bxt_trigger_setcommand (still banned in individual levels) are allowed in runs.
We have discussed whether some commands that are currently disallowed should or should not be allowed. We have decided to allow the -commands since they do not affect the run. Usage of bxt_trigger_setcommand is still banned in Individual Level runs, since custom triggers for timing might be installed for IL-timing in the future.
Allowance of all -commands, -bxt-commands and bxt_trigger_setcommand
Rule change: All the -commands (normal HL-base-commands with a "-" at the beginning, and all -bxt-commands) as well as bxt_trigger_setcommand (still banned in individual levels) are allowed in runs.
We have discussed whether some commands that are currently disallowed should or should not be allowed. We have decided to allow the -commands since they do not affect the run. Usage of bxt_trigger_setcommand is still banned in Individual Level runs, since custom triggers for timing might be installed for IL-timing in the future.
Permanent demo storage requirement
Rule change: "Demos of your latest PB have to be available permanently to the moderators, either online via the download link, or on your local harddrive if the download link expires."
Some of the formerly submitted and verified runs are missing demo files and cannot be viewed or checked anymore. Demo files of your PBs (not of your obsolete runs) have to be available at all times, either by saving them permanently online, or by being able to provide them directly to the moderators if the link provided in your verified PBs does not work anymore (for example due to deletion of the uploaded demos by the hosting site).
For permanent storage online, you usually have to have an account on a platform to ensure your uploads will not be deleted after some time. You can use platforms like Google Drive, Dropbox, or Mediafire.
If demos cannot be made available for your PB on the leaderboard at any given time, it can result in a rejection of your run on the leaderboard.
This thread is going to show current rule changes for this leaderboard. If you follow this game on srdc, you are going to be notified about these changes in this thread by the bell-messenger in the right top corner next to your nickname.
We hope this helps to keep you up to date. All major rule changes will be reported here.
Allowance of all -commands, -bxt-commands and bxt_trigger_setcommand
Rule change: All the -commands (normal HL-base-commands with a "-" at the beginning, and all -bxt-commands) as well as bxt_trigger_setcommand (still banned in individual levels) are allowed in runs.
We have discussed whether some commands that are currently disallowed should or should not be allowed. We have decided to allow the -commands since they do not affect the run. Usage of bxt_trigger_setcommand is still banned in Individual Level runs, since custom triggers for timing might be installed for IL-timing in the future.
Allowance of all -commands, -bxt-commands and bxt_trigger_setcommand
Rule change: All the -commands (normal HL-base-commands with a "-" at the beginning, and all -bxt-commands) as well as bxt_trigger_setcommand (still banned in individual levels) are allowed in runs.
We have discussed whether some commands that are currently disallowed should or should not be allowed. We have decided to allow the -commands since they do not affect the run. Usage of bxt_trigger_setcommand is still banned in Individual Level runs, since custom triggers for timing might be installed for IL-timing in the future.
Allowance of all -commands, -bxt-commands and bxt_trigger_setcommand
Rule change: All the -commands (normal HL-base-commands with a "-" at the beginning, and all -bxt-commands) as well as bxt_trigger_setcommand (still banned in individual levels) are allowed in runs.
We have discussed whether some commands that are currently disallowed should or should not be allowed. We have decided to allow the -commands since they do not affect the run. Usage of bxt_trigger_setcommand is still banned in Individual Level runs, since custom triggers for timing might be installed for IL-timing in the future.
Allowance of all -commands, -bxt-commands and bxt_trigger_setcommand
Rule change: All the -commands (normal HL-base-commands with a "-" at the beginning, and all -bxt-commands) as well as bxt_trigger_setcommand (still banned in individual levels) are allowed in runs.
We have discussed whether some commands that are currently disallowed should or should not be allowed. We have decided to allow the -commands since they do not affect the run. Usage of bxt_trigger_setcommand is still banned in Individual Level runs, since custom triggers for timing might be installed for IL-timing in the future.
Allowance of all -commands, -bxt-commands and bxt_trigger_setcommand
Rule change: All the -commands (normal HL-base-commands with a "-" at the beginning, and all -bxt-commands) as well as bxt_trigger_setcommand (still banned in individual levels) are allowed in runs.
We have discussed whether some commands that are currently disallowed should or should not be allowed. We have decided to allow the -commands since they do not affect the run. Usage of bxt_trigger_setcommand is still banned in Individual Level runs, since custom triggers for timing might be installed for IL-timing in the future.
Allowance of all -commands, -bxt-commands and bxt_trigger_setcommand
Rule change: All the -commands (normal HL-base-commands with a "-" at the beginning, and all -bxt-commands) as well as bxt_trigger_setcommand (still banned in individual levels) are allowed in runs.
We have discussed whether some commands that are currently disallowed should or should not be allowed. We have decided to allow the -commands since they do not affect the run. Usage of bxt_trigger_setcommand is still banned in Individual Level runs, since custom triggers for timing might be installed for IL-timing in the future.
Allowance of all -commands, -bxt-commands and bxt_trigger_setcommand
Rule change: All the -commands (normal HL-base-commands with a "-" at the beginning, and all -bxt-commands) as well as bxt_trigger_setcommand (still banned in individual levels) are allowed in runs.
We have discussed whether some commands that are currently disallowed should or should not be allowed. We have decided to allow the -commands since they do not affect the run. Usage of bxt_trigger_setcommand is still banned in Individual Level runs, since custom triggers for timing might be installed for IL-timing in the future.
Allowance of all -commands, -bxt-commands and bxt_trigger_setcommand
Rule change: All the -commands (normal HL-base-commands with a "-" at the beginning, and all -bxt-commands) as well as bxt_trigger_setcommand (still banned in individual levels) are allowed in runs.
We have discussed whether some commands that are currently disallowed should or should not be allowed. We have decided to allow the -commands since they do not affect the run. Usage of bxt_trigger_setcommand is still banned in Individual Level runs, since custom triggers for timing might be installed for IL-timing in the future.
Allowance of all -commands, -bxt-commands and bxt_trigger_setcommand
Rule change: All the -commands (normal HL-base-commands with a "-" at the beginning, and all -bxt-commands) as well as bxt_trigger_setcommand (still banned in individual levels) are allowed in runs.
We have discussed whether some commands that are currently disallowed should or should not be allowed. We have decided to allow the -commands since they do not affect the run. Usage of bxt_trigger_setcommand is still banned in Individual Level runs, since custom triggers for timing might be installed for IL-timing in the future.
Allowance of all -commands, -bxt-commands and bxt_trigger_setcommand
Rule change: All the -commands (normal HL-base-commands with a "-" at the beginning, and all -bxt-commands) as well as bxt_trigger_setcommand (still banned in individual levels) are allowed in runs.
We have discussed whether some commands that are currently disallowed should or should not be allowed. We have decided to allow the -commands since they do not affect the run. Usage of bxt_trigger_setcommand is still banned in Individual Level runs, since custom triggers for timing might be installed for IL-timing in the future.
Hi,
you can bind keys to save under any name as a hard save and load that hard save. For example:
bind <key> "save name1" bind <key> "load name1"
That way, you can make an infinite number of separate saves, if you can manage the keys you need to save and load them on the fly.
Guide section clean up / Guide Compilations
Change: For the sake of order and having a better overlook in the guide section, all guides have been checked and partly restructured.
Full game tutorials or subject tutorials (like "setup", "strategies", "category specific" etc.) have been decided to remain stand-alone-tutorials. A few guides however only contain a single strategy or a small section of speedrunning the game, and were united according to two broad categories: "Config Guides" (2 Guides), and "Strategy Guides" (10 guides). These guides can be seen in this Table.
These 12 guides have been merged and published as compilation guide entries in the guide section as Config Guide Compilation and Strategy Guide Compilation. The single guide entries of these guides now comprised in these compilation guides (plus one guide where the video was not available anymore) have been deleted from the guide section.
This information is posted in the Rule Change Log because it was sort of a bigger change within the SRDC leaderboard. We want to emphasize that this decision was not based on personal grounds; it is a structural decision.
Thank you to everybody contributing information and knowledge by making guides and the like!
Run start in ba_security1
Rule change: "Timing starts after you load the map "ba_security1" (pls use malte's start save from the resources) and ends on the first frame that the credits text appears."
Because of the initial clip from ba_tram3 to ba_security1, in the past there have been used different timing methods and start saves to start a Blue-Shift-run. The rule has been changed to clarify some misunderstandings. Please use the run start save by maltemller provided in the resources. It is considered to mark the run start accurately.
Due to the standardisation of methods to this one method of timing, some of the runs have been retimed.
