View unanswered posts | View active topics It is currently Mon Nov 20, 2017 2:46 am



This topic is locked, you cannot edit posts or make further replies.  [ 4 posts ] 
 RULE BOOK - RED FLAG & JOINT WARRIOR 
Author Message
Site Admin

Joined: Thu Oct 04, 2012 1:35 am
Posts: 144
(A) Pilot ID

Participants must use the same callsign as the one showed on the SA rankings; there is a search box on top of the rankings table to easily spot yourself; if you are driving a fighter, find your callsign here-->http://sa-sim.com/rankings/ and if you are driving a bomber, find your callsign here-->http://sa-sim.com/dcsfc-a2g-rankings/; if you did not find your callsign, it means you do not feature on the SA rankings yet, in which case, you need to stick to your usual callsign.

(B)Fratricide

(1)Firing bullets, active or heat-seeking missiles in the direction of a friendly is forbidden; Penalties will be applied in case of a reckless teamkill including point deduction and possible suspension.

(2)If merged with an enemy, a pilot must broadcast own position to the rest of the team immediately via TS using Bulleye as reference (ex. [callsign]merged, BE, south west, 15 miles). Failing to do so, a player will be held accountable if teamkilled.

(C)Mid-air Collisions

Air collisions will count as a loss just like any other crash with no option to rejoin, so caution with close formations.

(D)Vulching

Attacking player-controlled aircraft on the ground is allowed using air-to-ground guided and unguided weapons as well as guns and is forbidden using air-to-air missiles.

(E) Ejecting

If you eject, do not exit the server until the crash is confirmed by the server; failing to do so will result in a 50% unit value penalty against the offender.

(F) Re-Spawning

(1)Unless stated otherwise, each pilot is granted one life only. Re-spawning is not allowed under any circumstances without the consent of an administrator; this includes joining spectators without exiting the server or re-connecting to the server after loosing connection.

(2) Skipping the Refuel/Rearm (R/R) process by spawning in a new unit is forbidden; a 50% unit value penalty will be counted against offenders

(3) If upon landing you are unable to R/R for any reason (ex. empty tanks, gear damage, stuck on grass), you must notify an admin then purge a 10mn penalty before spawning in a new unit; any further damage while landing will result in an exit and a counted loss; landing on roads is not allowed unless it is in the immediate vicinity of the air base (realistically the aircraft can be easily towed back onto the runway)

(4) In case of a mid-air disconnection, we will see if anyone is complaining about it first, normally people can be aware when the target they were engaging has disconnected; if no complain, one would be allowed to join the server again; now if it appears when watching Tacview that the disconnection was during a merge, turning fight, while being fired upon or under any threat or danger, a loss will be added to the pilot who disconnected; in addition all points scored after the disconnection will be canceled; conversely, the opposing pilot will be credited with a kill.

(G) Landing and Refueling/rearming

(1)By default, landing is only allowed on departure airfields; landing may also be allowed on additional airfields, which will be specifically designated if applicable; landing anywhere else will count as a loss and offender must exit the server.

(2) Refueling/rearming is forbidden on the runway.

(3) Landing must be performed on the left side of the runway and pilot must remain there until exiting the runway. U-turns while taxing must be performed with caution after a shoulder check.

(4)Landing before the end of the mission is a must; A "Knock it off" call will be broadcast via chat 15mn before time is up after which all engagements must stop immediately regardless of the situation and all pilots must head back home for the final RTB; The server will close precisely after 3 hours; failing to land before the server shuts down will count as a loss.

(H) Flight Duration and Substitution

(1) A participant must fly actively at least 50% of the battle duration to validate own stats. Not reaching the minimum flight time or flying passively (not engaging) will result in a canceled run.

(2) Replacing pilots is only allowed at half time; exiting pilot must land and come to a complete stop before exiting the server; substitute can connect, spool-up, taxi and hold short and not take off until the server confirms that the other pilot has exited the server; both participants must notify an admin and get a permission beforehand.

(I) Claiming and Reporting

Each participant must review the ACMI generated by the server, which is posted by the host after the competition and claim events that have not been reported or report any discrepancies with what actually happened; all claims must be posted within 48 hours after the publication of the of the official ACMI and must be supported by evidence either from the official ACMI itself or from own ACMI. Claims posted too late will not be considered, especially if the rankings have already been updated.


(1) Maneuver kill:
You have fired on someone and he crashed while attempting to evade your missiles or you are involved in a dogfight and your opponent crashes in the middle of it. You can claim it here whilst specifying who was involved, at what time in Tacview and a description of the situation.

(2) Assist / Kill share:two or more pilots can share the same kill if they were all involved in destroying the target. Involved means having fired on the same target before it got hit and missiles were close enough. Missile from the second pilot must impact the target within 10 seconds if the target was destroyed after the initial hit. There is no time limit if the target was still able to fly after the first hit.

(3)Reporting a clean run:Sometimes a pilot fights and survive the whole match but without scoring points; in this case, the pilot may be still be eligible to receive ranking points (depending on how many pilots scored higher); to claim a clean run, a pilot must submit own callsign, flight start time and end time and it will be looked into for confirmation and a chance to get ranking points (SA points).

(4) Reporting an oversight:While we try to be as accurate as possible with the results, oversights can happen, so this is why we try to involve you the pilots. Anything odd or unclear, you can also post here whether it be your flight or someone else's.

(J) Check in and mission launch

(1) Make sure you do a fresh reboot and unload any unnecessary application from your Task manager before joining TeamSpeak; this will ensure all your computer's resources will be dedicated to DCS; Decreasing the graphics profile to medium or low is also recommended for most specs in order to improve the frame-rate in the heavy MP environment.

(2) The check in starts one hour prior to the kick off on a specified TeamSpeak channel. Failing to check in at least 30mn before the start of the battle will make you loose your slot to someone from the wait list.

(3)You may enter your aircraft upon joining the server and re-arm your aircraft but you must wait for clearance to start your engines from event staff after which the fight will be on.


Thu Jul 16, 2015 2:21 am
Profile
Site Admin

Joined: Thu Oct 04, 2012 1:35 am
Posts: 144
22.07.2015 - Update to rule "G-4" - Came into effect after JW4

Former statement
"Landing before the end of the mission is a must; A reminder for the final RTB will be given usually 10mn before time is up; failing to land before the server closes will result in a loss counted against you."

New Statement
"Landing before the end of the mission is a must; A "Knock it off" call will be broadcast via chat 15mn before time is up after which all engagements must stop immediately regardless of the situation and all pilots must head back home for the final RTB; The server will close precisely after 3 hours; failing to land before the server shuts down will count as a loss."


Thu Jul 16, 2015 2:06 pm
Profile
Site Admin

Joined: Thu Oct 04, 2012 1:35 am
Posts: 144
11.01.2016 - Added vulching rule (D) - Came into effect before Red Flag 4

Attacking player-controlled aircraft on the ground is allowed using air-to-ground guided and unguided weapons as well as guns and is forbidden using air-to-air missiles.


Sun Jan 10, 2016 9:11 pm
Profile
Site Admin

Joined: Thu Oct 04, 2012 1:35 am
Posts: 144
Added Rule B-2 - Came into effect after Red Flag 4:
If merged with an enemy, a pilot must broadcast own position to the rest of the team immediately via TS using Bulleye as reference (ex. [callsign]merged, BE, south west, 15 miles). Failing to do so, a player will be held accountable if teamkilled.


Expanded on Rule (I) - Came into effect after Red Flag 4:

Each participant must review the ACMI generated by the server, which is posted by the host after the competition and claim events that have not been reported or report any discrepancies with what actually happened; all claims must be posted within 48 hours after the publication of the of the official ACMI and must be supported by evidence either from the official ACMI itself or from own ACMI. Claims posted too late will not be considered, especially if the rankings have already been updated.

(1) Maneuver kill: You have fired on someone and he crashed while attempting to evade your missiles or you are involved in a dogfight and your opponent crashes in the middle of it. You can claim it here whilst specifying who was involved, at what time in Tacview and a description of the situation.

(2) Assist / Kill share: two or more pilots can share the same kill if they were all involved in destroying the target. Involved means having fired on the same target before it got hit and missiles were close enough. Missile from the second pilot must impact the target within 10 seconds if the target was destroyed after the initial hit. There is no time limit if the target was still able to fly after the first hit.

(3)Reporting a clean run:Sometimes a pilot fights and survive the whole match but without scoring points; in this case, the pilot may be still be eligible to receive ranking points (depending on how many pilots scored higher); to claim a clean run, a pilot must submit own callsign, flight start time and end time and it will be looked into for confirmation and a chance to get ranking points (SA points).

(4) Reporting an oversight:While we try to be as accurate as possible with the results, oversights can happen, so this is why we try to involve you the pilots. Anything odd or unclear, you can also post here whether it be your flight or someone else's.


Thu Jan 21, 2016 6:24 pm
Profile
Display posts from previous:  Sort by  
This topic is locked, you cannot edit posts or make further replies.   [ 4 posts ] 

Who is online

Users browsing this forum: No registered users and 1 guest


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Search for:
Jump to:  
cron
Powered by phpBB® Forum Software © phpBB Group
Designed by ST Software.