Rules
"COLDWAR echo" project is made to simulate combat flight conditions as close as possible to real world.
Version from 10th of January 2011
1. Rules for pilots:
1.1 Every pilot has only one life per event.
1.2 Only standard payloads are allowed (if not mentioned otherwise in mission briefing).
1.3 Launch of R-27T/ET without "Launch Authorized" command (maddog) is forbidden.
1.4 Any usage of cheats, PrintScreen key is forbidden.
1.5 Refuel and rearm are allowed only on few air fields list of which you'll get in mission briefing. Refuel and rearm are allowed only in parking area (not on taxiway or runway) with engines shut down.
1.6 Landing on road is allowed, pilot and aircraft will be resulted as saved (on ally territory), but current event for this pilot will be over.
1.7 Vouching is allowed.
1.8 After crash (death) pilot must leave server within 2 minutes.
1.9 Simulator Requirements: LockOn: Flaming Cliffs 2.0.
2. Rules for server:
2.1 External views - disabled.
2.2 Labels - disabled.
2.3 Map - enabled with only "my aircraft".
2.4 Log in chat window - disabled.
2.5 Server's admin is not allowed to shut down server after "EVENT STARTED" command while there is at least one "alive" pilot on the server, or up to official confirmation from both side organizers that battle is over. If mission time is limited in briefing, server will be shut right at that time.
2.6 If possible Flight Control software and TeamSpeak will be installed on the server, sides will be informed about it in advance.
2.7 Event holding is successful and doesn't restart after 40 minutes after "EVENT STARTED" command, reported by "NO RETURN POINT" command.
3. Rules for sides:
3.1 The event is declared started after side organizers said in chat "US are ready" and "CCCP готовы", and administrator give "EVENT STARTED" command.
3.2 Flight Controllers are allowed (but not more than 2 per side) who will use special software (ATC JaBog or other).
3.3 Flight Controller must make an audio record in TS and after event give the recording to opposite side.
4. Rules for results calculation:
4.1 Success of each side is measured in percentage system (100% = accomplish of all tasks and saving all aircrafts) with accuracy up to hundredth part.
4.2 Each side will have one primary objective which is valuable of 45%.
4.3 Each side will have two or three secondary objectives which are valuable of 12,5% and 8,33% accordingly.
4.4 Saving all aircrafts is valuable of 30%.
4.5 Each objective can be accomplished partially (for example, secondary objective is to destroy column counted 10 vehicles, if 6 units are destroyed then - 12,5/10*6=7,5% success).
5. Rules for mission:
5.1 Mission will be developed by group of organizers, who do not participate in the battle and not interested in certain results.
5.2 Mission will be available to the sides only on the event.
5.3 Sides will be briefed and get objectives in one month before battle.
5.4 Sides will get additional info about mission once per week (3 times from briefing to battle) - "Recon Reports".
6. Force majeure:
6.1 On lag or connection drop (not piloting mistake) pilot have opportunity to reenter to the server, before "NO RECONNECTION ALLOWED" declared (10 minutes after "EVENT STARTED").
6.2 Pilot with ping higher than 300ms must leave the server, or be substituted.
6.3 If server crash before "NO RETURN POINT" declared, mission will be restarted and all results will be cleared. If server crash after "NO RETURN POINT" declared, mission will not be restarted and all results on that moment will be counted as final.
7. Participation in event:
7.1 For participation register in our forum and place application in according thread.
7.2 All applications will be reviewed by US and CCCP organizers accordingly.
8. Penalties:
8.1 Penalties are: warning, ban for participation, reducing result number by penalty points, reducing number of slots for side in next event.
8.2 Violation of any rule from section №1 will be punished by warning and/or ban for participation, if violation affected on result, then it will be punished by reducing result and/or reducing number of slots.
8.3 Violation of any rule from section №3 will be punished by reducing result and/or reducing number of slots.
8.4 Other violations will be punished according to its weight after project's administration review.
Version from 10th of January 2011
1. Rules for pilots:
1.1 Every pilot has only one life per event.
1.2 Only standard payloads are allowed (if not mentioned otherwise in mission briefing).
1.3 Launch of R-27T/ET without "Launch Authorized" command (maddog) is forbidden.
1.4 Any usage of cheats, PrintScreen key is forbidden.
1.5 Refuel and rearm are allowed only on few air fields list of which you'll get in mission briefing. Refuel and rearm are allowed only in parking area (not on taxiway or runway) with engines shut down.
1.6 Landing on road is allowed, pilot and aircraft will be resulted as saved (on ally territory), but current event for this pilot will be over.
1.7 Vouching is allowed.
1.8 After crash (death) pilot must leave server within 2 minutes.
1.9 Simulator Requirements: LockOn: Flaming Cliffs 2.0.
2. Rules for server:
2.1 External views - disabled.
2.2 Labels - disabled.
2.3 Map - enabled with only "my aircraft".
2.4 Log in chat window - disabled.
2.5 Server's admin is not allowed to shut down server after "EVENT STARTED" command while there is at least one "alive" pilot on the server, or up to official confirmation from both side organizers that battle is over. If mission time is limited in briefing, server will be shut right at that time.
2.6 If possible Flight Control software and TeamSpeak will be installed on the server, sides will be informed about it in advance.
2.7 Event holding is successful and doesn't restart after 40 minutes after "EVENT STARTED" command, reported by "NO RETURN POINT" command.
3. Rules for sides:
3.1 The event is declared started after side organizers said in chat "US are ready" and "CCCP готовы", and administrator give "EVENT STARTED" command.
3.2 Flight Controllers are allowed (but not more than 2 per side) who will use special software (ATC JaBog or other).
3.3 Flight Controller must make an audio record in TS and after event give the recording to opposite side.
4. Rules for results calculation:
4.1 Success of each side is measured in percentage system (100% = accomplish of all tasks and saving all aircrafts) with accuracy up to hundredth part.
4.2 Each side will have one primary objective which is valuable of 45%.
4.3 Each side will have two or three secondary objectives which are valuable of 12,5% and 8,33% accordingly.
4.4 Saving all aircrafts is valuable of 30%.
4.5 Each objective can be accomplished partially (for example, secondary objective is to destroy column counted 10 vehicles, if 6 units are destroyed then - 12,5/10*6=7,5% success).
5. Rules for mission:
5.1 Mission will be developed by group of organizers, who do not participate in the battle and not interested in certain results.
5.2 Mission will be available to the sides only on the event.
5.3 Sides will be briefed and get objectives in one month before battle.
5.4 Sides will get additional info about mission once per week (3 times from briefing to battle) - "Recon Reports".
6. Force majeure:
6.1 On lag or connection drop (not piloting mistake) pilot have opportunity to reenter to the server, before "NO RECONNECTION ALLOWED" declared (10 minutes after "EVENT STARTED").
6.2 Pilot with ping higher than 300ms must leave the server, or be substituted.
6.3 If server crash before "NO RETURN POINT" declared, mission will be restarted and all results will be cleared. If server crash after "NO RETURN POINT" declared, mission will not be restarted and all results on that moment will be counted as final.
7. Participation in event:
7.1 For participation register in our forum and place application in according thread.
7.2 All applications will be reviewed by US and CCCP organizers accordingly.
8. Penalties:
8.1 Penalties are: warning, ban for participation, reducing result number by penalty points, reducing number of slots for side in next event.
8.2 Violation of any rule from section №1 will be punished by warning and/or ban for participation, if violation affected on result, then it will be punished by reducing result and/or reducing number of slots.
8.3 Violation of any rule from section №3 will be punished by reducing result and/or reducing number of slots.
8.4 Other violations will be punished according to its weight after project's administration review.