remember you can use semicolons for multiple assignments. ie
x 3; y 8; z 9;
i’d prefer not to scroll the init screen. an extreme init could also use the TL. i’ve considered TL as a super-long scratchpad as well as a sequential execution system.
i don’t like the idea of calling scripts from other scenes-- i would discourage pursuing this. primarily for the reason that for scenes to inter-read one another they’d all need to have static indexes, ie script 1 of scene 3 called by script 3 of scene 5. ugh. this is unmanageable and unshare-able. if someone wants to share a scene, it should be possible as a single elegant little bundle. cross-scene communication would be a mess in many ways-- require scenes to be loaded at specific index positions in order to function. so, again, there are better ways.
for those on the fence about TL: imagine another screen, like TRACKER. it scrolls. lines start with a number.
200 TR 1 1
200 X ADD X 1
200 M.ACT 0
300 TR 2 1
so, for example, you want to extend script 1:
TL.CALL would execute the TL at the given position. when it hits BREAK it’ll quit.
thinking while typing, sorry: the BREAK might not even be needed, as the idea for TL was to be operated from a timer. but perhaps explicit CALLs would make the system clearer. ie:
0 TR.P 1
100 TR.P 1
100 TR.P 2
150 TR.P 1
X ADD X 1
X MOD X 200
so this is a manual execution, but it lets you do some interesting things. anyway, i should sit down and work with the design. any comments welcome.
and to clarify, each scene has their own TL script.
i don’t like this idea because again it makes it so scenes have dependencies.
this is a spectacular idea. it’s an editor feature, not a language issue. it keeps scenes atomic.