Just a totally untested (I don't have a setup to compile it), first stab at a suggestion for File/Message I/O.
On ship 1, anywhere in game, add an LCD named "Write:FromSixty". Set its text to "Hello!"
On ship 2, anywhere in game, add an LCD named "Read:FromSixty". Its text will be auto-set to the contents of above message.
On either ship, add an LCD named "FileIO" for debug information. This can get spammy.
This is limited to Factions. Factions can only see their own files. Over reboots, a Reader might blink, due to the Writer not being read yet.
Why add this?
Combined with "CargoOut@*", this can allow scripters to add a request system. Add "AmmoName:10000" and if there's any in the base, base can push 10000 to CargoOut@(id)
Collect Data from several ships and scripts into one location. Have ships write their statuses to Write: LCDs and collect them all with Read: LCDs.
Other possible ideas/changes to this code:
Make it more like a semaphore. When a non-empty "Write:*" LCD is read, clear it. Then clear the file when it's "written" to a "Read:". Only write to a "Read:" if there's a value saved. So scripts can clear its text to wait for next writing
Just a totally untested (I don't have a setup to compile it), first stab at a suggestion for File/Message I/O.
On ship 1, anywhere in game, add an LCD named "Write:FromSixty". Set its text to "Hello!"
On ship 2, anywhere in game, add an LCD named "Read:FromSixty". Its text will be auto-set to the contents of above message.
On either ship, add an LCD named "FileIO" for debug information. This can get spammy.
This is limited to Factions. Factions can only see their own files. Over reboots, a Reader might blink, due to the Writer not being read yet.
Why add this?
Other possible ideas/changes to this code: