Quote
Originally posted by Lequis MX:
**I'm working on this ridiculously huge TC Plug. It features:
500+ systems
30(about) ships with all new rendered graphics
a preposterous # of governments
somewhere around 30 landing pix+planets
And I am having trouble structuring it. ShipWrite is helping me piece together most of the ships, but I'm not sure about corresponding resource IDs to PICTS and stuff. Any help/advice would be appreciated, although I'm not willing to send a 15MB e-mail attachment for beta testing or something...(yes, it's that big already... :frown:)
Summary:
Are there any efficient ways to lay out a TC while you try to structure its IDs and stuff?
-Lequis
**
Okay, first off, Pontus' EVO Formula Calculator is in the add-on's page of this site. Very, very handy for figuring out all those little resource numbers -- ShipWrite gets most of them right, tho, and the big display is helpful in indicating if you forgot any.
I was just over at the internet gaming company my friend works for, and I read a couple books on interactive storytelling. Out of all that, all I can really tell you is to be organized. Start off with a prose work describing exactly what your plug intends to do. Then another prose work detailing the history and back-story. Then another piece of creative writing for each of the major missions, told in story form all the way through that mission chain.
Okay, then you flowchart the durn thing. I'm not into software planners; just get a pad of graph paper and start drawing boxes. Each box has the mission number at the top, some descriptive note to yourself in the box proper, and Y/N choices at the bottom.
But, really, the best advice is that which my engineer father gave me; DIVIDE AND CONQUER. Divide any problem into smaller problems. Divide any plot into smaller plot chunks. Divide any universe into quadrants. Divide your ships into basic classes. That way, you can test, say "All the Earth Govt military ships" as a seperate plug and rule out any problems with them -- rather than dig into a 17 meg plug-in looking for one bad resource!
------------------
everywhere else, it's --
"Nomuse"