A tweak on the above idea: since it's highly doubtful anyone's writing any new ZScript code that specifically targets 2.3.0 ('cause it's old), the only time people are going to run into this exact error message, practically speaking, is because they forgot to put a declaration. So perhaps
only if the assumed ZScript version is
exactly 2.3.0, amend the message to read something like:
<class> not accessible to ZScript version 2.3.0. Did you remember to declare a version number in your ZScript code?
This patches the hole without impacting any actual mods built for 2.3.0.
[Wording suggestions welcome, of course.]
A tweak on the above idea: since it's highly doubtful anyone's writing any new ZScript code that specifically targets 2.3.0 ('cause it's old), the only time people are going to run into this exact error message, practically speaking, is because they forgot to put a declaration. So perhaps [i]only[/i] if the assumed ZScript version is [i]exactly[/i] 2.3.0, amend the message to read something like:
[quote]<class> not accessible to ZScript version 2.3.0. Did you remember to declare a version number in your ZScript code?[/quote]
This patches the hole without impacting any actual mods built for 2.3.0.
[Wording suggestions welcome, of course.]