Quote
Originally posted by UE_Research & Development:
**Notes can then be made as to which mission branches off to which. When it comes time to actually code the process is then a cut-and-paste (although I recommend you make some sort of mission map detailing how your mission strings will unfold).
Hope this was of assistance.
**
Yeah. I'm doing somethng similar, but making use of tab delimited spreadsheets and linking to different sheets to make something that the NovaTools txt<->rsrc program could handle.
I guess I was hoping for some crafty tool that would allow the user to 'walk' though missions by forcing either fail or completions. What it cmoes down to is I was hoping for something that would make me stop imagining an tool in my head. The voices in my head paint the following word picture:
An application that reads in existing misn data and presents the user with a simple window. The window has a few buttons. You select a mission and are then displayed the intro text. You can then hit the Accept, Decline or Buttons. The user is displayed the appropriate text. There is another button called Continue which then displays the next mission in the thread. If there are several choices as to what would be the next available mission, the user is offered a choice. IN this way the user could test run missions without actually loading up Nova. The voices also tell me that the user would be able to program/edit missions in the same fashion. So, for example, if the user walks through an entire thread and there are no next available missions, the user is presented with a Make Next button allowing them to define the mission they want.
Just a thought.
-STH
(get out of my head!)
------------------
"Create enigmas, not explanations." -Robert Smithson