So instead of ordering execution affecting every function in the script I’m wondering if it would be a useful feature if you could for instance have it split into Script Initialization Order and Script Update Order.
It would look something like this:
I would love a feature like this but perhaps it would be bad practice
What are your thoughts?
I don’t like using ANY of those order of execution things and here is why:
From the perspective of inspecting the code, it is completely invisible.
If I do explicit order handling in my own code, with extra dependent calls from script A to script B if the order truly matters, it has multiple great effects:
-
the code is portable between any two Unity projects without mysterious failures (two years from now if you go back to copy this code, will you even remember the execution order stuff?)
-
the code itself is the actual source of truth for running. With source control history this is essential for forensic problem solving.
-
it really encourages you to code in a way that minimizes actual order dependency.
I highly recommend you get away from using script execution order completely. I never use it ever, as it is a global source of confusion and code misbehavior.