RussiaNew links
Demos: https://disk.yandex.ru/d/6Hduee7zVslSpw
Splits: https://disk.yandex.ru/d/yi7XZ_VXOstnzQ
Live Recording: https://disk.yandex.ru/i/2C_wi4fwQQpb-A
New demos link: https://disk.yandex.ru/d/lah6Mu48lSD4zQ (I figured editing the run would send to to the verification procedure again.)
dont read; some detailed explaination about mentioned problems
speaking of the the reasons why mid-run changing difficulty is banned: currently the argument "it cannot be done w/o console" doesnt mean anything in the borders of the paradigm which is established in console-exclusive commands region of rules. it is way more complicated: skill is a console-exclusive cvar (not when you start the game, but while you are playing the game) just like all others (means that it's status must be decided by the majority), but there is also "Difficulty" column (where you submit the run) where there are only 3 game difficulties: "Easy", "Medium", "Hard". in the paradigm, there must be no exceptions, so we cant call skill a "special" command. therefore, while the current paradigm is in use, the argument doesn't make sense.
about "sv_cheats 1" problem exec said about eariler. currently it is not "generally banned by common sense", because the Whitelist -- the current solution to console-exclsuive commands problem (and sv_cheats 1 is a console-exclusive cvar like all others). and in the Whitelist sv_cheats is red, i.e. banned. Theoretically, it is banned because the majority of runners agree that it must be banned. Practically, this cvar was instantly banned without revealing the majority's opinion ("coz yeah, common sense, should be banned, everybody agrees"). So, sv_cheats 1 is absolutely not "special" by any means and making a bullet point about it in the rules is ridiculous (then we need to make a bullet point for all 600+ commands)
