Utilities that mappers can use in their GSC scripts that affect core systems of the mod.
Triggers with targetname "no_save_zone" should not allow the player to save their position.
Triggers with targetname "load_position" should load the player's last save.
Triggers with targetname "end_run" should end the player's run.
Triggers with targetname "bhop_zone" should only allow bhopping inside the trigger.
...
Mappers can use these features to restrict players from doing certain actions, therefore allowing new freedoms in designing visuals for their maps (antirigging becomes much easier). Also things like no_save_zones can introduce unique gameplay challenges and bhop zones can decrease confusion in whether a jump is supposed to be a bhop or not.
Targetnames can obviously be changed, those are just few examples of what I could think of. Also the effects these custom triggers bring should be only enabled during a run.
It's obviously up to the mappers if they want to make use of these. It would also standardise some common scripts that people try to implement in their maps. We could eventually have a tutorial for mappers in the website that shows a few examples.
A discussion could also be had whether custom triggers could be used for certain checkpoints. For example the mapper could draw a trigger in a weird shaped platform to help with checkpoint boundaries, but implementing something like this I imagine would not be easy.
cod2 uses "nosave" as targetname for trigger_multiple
load_position can just be a trigger_multiple that calls some script
end_run wtf?
bhop_zone could just be a nosave trig right?
Utilities that mappers can use in their GSC scripts that affect core systems of the mod.
Mappers can use these features to restrict players from doing certain actions, therefore allowing new freedoms in designing visuals for their maps (antirigging becomes much easier). Also things like no_save_zones can introduce unique gameplay challenges and bhop zones can decrease confusion in whether a jump is supposed to be a bhop or not.
Targetnames can obviously be changed, those are just few examples of what I could think of. Also the effects these custom triggers bring should be only enabled during a run.
It's obviously up to the mappers if they want to make use of these. It would also standardise some common scripts that people try to implement in their maps. We could eventually have a tutorial for mappers in the website that shows a few examples.
A discussion could also be had whether custom triggers could be used for certain checkpoints. For example the mapper could draw a trigger in a weird shaped platform to help with checkpoint boundaries, but implementing something like this I imagine would not be easy.