When making additional envvars that control the program/code flow like cac2be7 it is important to consider that it is not automatically documenting itself or making itself known in anyway.
It might be possible to make a rust function that mandates a documentation string, and that could be printed in some way by the program, imagine stardust-xr-server --list-vars. The way --list-vars could be populated is by a function like stardustxr_make_feature which would take a documentation string and env var as arguments, therefore making it impossible to make an envvar lookup that doesn't document itself and make itself known within the code.
When making additional envvars that control the program/code flow like cac2be7 it is important to consider that it is not automatically documenting itself or making itself known in anyway.
It might be possible to make a rust function that mandates a documentation string, and that could be printed in some way by the program, imagine
stardust-xr-server --list-vars. The way--list-varscould be populated is by a function likestardustxr_make_featurewhich would take a documentation string and env var as arguments, therefore making it impossible to make an envvar lookup that doesn't document itself and make itself known within the code.