Quote:
Originally Posted by 5./JG27.Farber
Nope were going to stick to the script and run the last mission for next week. These are all lesson for next time.
I think we will have to wait for the next campaign until this CTD to be fixed or at least if someone can find a solution...
Hopefully next time, we will have an online section where people can log into to get briefings, a seperate TS3 for RED/BLUE and stats. We also aim to run double the number of missions. Also have some red attacks! 
About the one spawn thing, we are considering different options but really I think there is only 3:
1.Use the same system (No respawns after X amount of time)
2.Use SNAFU's server script 1 life/multiple aircraft - but does this account for being captured?
3.Dont use any restructions but shotern down the mission so a respawn is a waste of time...
Now I can hear some of you thinking, why have one at all why not fly as much as we want?! The answer is simple, with no consequnce people fly wrecklessly and unrealistically. So if you only get one life or one chance to fight you will bring your best flying skills! It also seperates it from being like a public server and makes it allot more exciting (or frustrating). |
Sounds great Farber.
I'd go for options 1 and 2. Allow a window for spawn problems, even takeoff-crashes and collisions among guys just not used to doing this. Then if you can script in 1 life and respawns that would be great.
You could also perhaps script in a takeoff delay for bailed pilots. If it were possible to identify which side of the channel they were on you could delay their takeoff for say 15 minutes if over friendly territory or 30 mins if over the channel or enemy territory. Or just a global delay. Just a thought
Here's a couple more ideas from what we've done before, probably for way in the future.
Have everyone pre-register for this and assign them to their (preferred?) unit in advance. Also allow this to be done by CoD Squadron with expected numbers (well, we do this now).
Walk-ons would be reduced and easily handled on the night.
Have a Command structure (by direct request or volunteered during registration?). Axis/Allied Commanders could even discuss the campaign, settings (not specific targets of course) but most important be made aware of their order of battle and the amount of 'intelligence' available to them. The main advantage would be a focal point for each side.
Commanders decide tactics and issue briefings to their unit leaders in advance. Spreads the load and gives some structure instead of trying to work it out on the night and perhaps not knowing who is doing what. We haven't really cracked that yet.
Only issue the server password to unit commanders via the appointed Teamspeak server on the night so that everyone is encouraged to actively co-operate and prevents gate crashing (we're partly there with passwording). Also allows a clear and definitive 'GO' to be issued to the Commanders when the server is started.
Just a nicety really, everyone could turn up 'in uniform', i.e. if they are assigned to 74 Sqdn they turn up re-badged as say 74RAF_klem or JG52/3_Farber.
Looking forward to Sunday.... and the next one