View Single Post
Lt. Commander
Join Date: Dec 2007
Posts: 120
# 7
04-26-2011, 06:19 AM
As I can see, the textual script input was asked during the Cryptic phone conference. But I'm sure it was mentioned even before that.
Creating a 3rd party editor to produce and process that mission script would be a piece of cake.
The Shared asstes problem would be solved instantly.
Procedurally AIDED mission design would possible.
Interpreting the plain text file would save bandwith and server resources at Cryptic's side.

Since the scrip has to go through Cryptic they can check for errors and throw out wrong lines. With only a series of create this, create that lines, you can't really go wrong server side.

My mapping tool comes somewhere close to this (export file input and CSV input-output), but that is still limited in many aspects.