Jul 31st '18, 03:04
What exactly are you having trouble with?
If you place the terminal texture on a wall in Vasara, it should pop up a screen asking you whether it's a save or text terminal, and what script to use. If you want to use a different texture for a terminal, I think that can be set up with MML but I'm not sure how.
Best way to learn how to code them is to open up existing terminal files and see how they're structured. I recommend looking at Eternal's, where there are some fun things like multiple logons and static, and Rubicon, which makes use of the #TAG to control things in the level by reading terminals.
But, to boil things down to the essentials, every terminal entry is structured as follows. Green text is mandatory, yellow text describes a variable number, blue text is for optional sections, red text is mandatory for multiple state terminals, white text is for comments
#TERMINAL terminal id
#UNFINISHED
various content tags such as #LOGON pict id followed by up to one line of text, #LOGOFF pict id followed by up to one line of text, #PICT pict id followed by many lines of text, #INFORMATION followed by many lines of text, #STATIC duration in ticks?, #TAG tag, #SOUND id, #BRIEFING level to teleport to followed by many lines of text, #CHECKPOINT id followed by many lines of text
#INTRALEVEL TELEPORT polygon or #INTERLEVEL TELEPORT level
#END
#FINISHED or #FAILED failed is for m1 rescue missions only
various content tags as above
#INTRALEVEL TELEPORT polygon or #INTERLEVEL TELEPORT level
#END
#ENDTERMINAL terminal id
Use ; to comment out a line. Use $B and $b to enclose bold text, $I and $i to enclose italics, $U and $u to enclose underlines, $C[number] to switch colours (default is green, should reset to green at the beginning of each new # section)