Interesting...I didn't know that
Thanks for the tip:tiphat:
---------- Post added at 04:55 PM ---------- Previous post was at 04:33 PM ----------
Okay, here are some basic rules (none of them apply to practice sessions
) :
Record all sessions in which you have to make a maneuver or do any burns. No need to record if you are just doing an update. Post a playback of what you did, and the updated scenario file, so that the next person can d/l it and continue the mission.
No time compression
I was advised against this, but completing the mission in a realistic time frame is part of the challenge, and it seems to me it should be quite rewarding. This is in "interrupted" real time, meaning you simply load the scenario every now and then, bring up the scenario editor, hit Date, then "Now", and then save the current state over the scenario file. This way no one has to leave their computer running for three and a half months
If a burn comes at an inconvenient time, just do it as soon as you can,
then update the scenario.
It should go without saying that if you die, you are off the team, whether it's through your mistake or someone else's. So let's try real hard not to kill anybody
Now I'm not out to create a permanent VSA here, so if you die in this project, you are of course welcome to join the next one (no details yet--still classified
)
That's pretty much it
Again, first posting of the scenario will be March 24. Thanks to all involved and good luck:thumbup: