RomaniaAyy, nice find! So many optimization for Any% at this point :D
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 now 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 now 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 now 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 now 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 now 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 now 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.
Nice, I didn't realize it's so early on but it makes the run so much easier and faster.
Hello YouSon, if the speedometer is not activated by default you can use "bxt_hud_speedometer 1" to enable it.
It didin't affect me at all so you don't have to tell me sorry. I made this post just to prove the point that having the skill command white listed without detail could mean anything. Thanks for explaining and resolving the cause of my problem anyway, keep this community alive.
I understand, but how could we know if we're not allowed to use it when it's white listed? My run was rejected for a reason that's not written anywhere, I even have a friend that did the same thing and got accepted, rules are the same, different moderator, different outcome.
Still waiting for a moderator's response since skill is white listed in the row 870 with nothing specified. Even if they change it now the run should be accepted since the rule was changed now.
My run got rejected for changing difficulty from 3 to 1 because I forgot to. The problem is that I wouldn't have done that if it was written in the rules that I can't.. ¤ Timing starts as soon as the map 'c1a0' is loaded and ends on the final hit dealt to Nihilanth (first frame that the blue lightning appears) ¤ fps_max must never exceed 100 (99.5 if playing on SteamPipe). ¤ Using inputs/saves from a previous playthrough is banned ¤ Demo submission is required to verify all runs. Even if you decide to record/stream the run you will still need to submit all demos from when the timer starts to when the timer stops. Demo recording guide: http://www.speedrun.com/hl1/guide/m3lo4 ¤ Runs must follow the command whitelist that can be found here: https://goo.gl/t8b3hh ¤ Runs must be done using the latest version of Bunnymod XT ¤ _bxt_save_runtime_data_in_demos must be 1
Runs done in this category must not use the 'wait' command or any scripts, aliases, macros, turbo buttons, hyper-scrolling and so on..
