Jump to content

Добро пожаловать на проект
Weekly Open Games

Weekly Open Games — это проект для людей, которым интересен хардкорный тип игры. Мы стараемся максимально эффективно использовать структуру, слабые и сильные стороны, а также технику и вооружение различных сторон конфликта, но не ставим перед собой цель провести 100% сбалансированного боестолкновения. Командная игра, командное взаимодействие — фундамент нашего проекта.
О проекте WOG Как начать играть Правила серверов
Sign in to follow this  
phlps

WOG project rules

Recommended Posts

Actual rules regulate in-game and out-of-game situations created by players taking part in WOG project, by administrating game sessions and by affecting on technical and moral-ethic parts of game play.

 

Administration has right to change these rules, make corrections and introduce additions in them, and create new rules. Players will be notified about them by news. Also every in-game and out-of-game situation will be overwatched separately in case it was reported to administration but there’s no rule about the situation.

 

Rules section #1.

Engagement of slots, re-enter in game session.

After administrator turns on missions and makes re-assign, slots are engaged by:

Side Commander and Squad Commanders (“Squad” status on WOG project)

Squad members

Guests of WOG project

Gaming groups (Not in current rotations despite being a registered Squad)

Single players(Single engage slots after administrator’s command. Punishment: Warning kick out of slot by administrator. Repeating the violation will cause restriction of access till the end of mission)

Forbidden:

Engagement of another’s slot without agreement with the player having engaged that slot before (in case the player got crashed and wants to continue playing)

Engagement of slot when the player’s not in TS.

Engagement of slot without permission of Squad Leader who controls the slot (in case of lone slots – without permission of Side Commander).

Re-enter on any slot after the death.

Re-enter to any other bot (who wasn’t engaged before) after the start of mission (except cases written below).

Allowed:

Re-entering on any free slot in 5 minutes since the beginning of mission as a result of unintentional team-killing.

Re-entering on any free slot in 10 minutes since the beginning of mission as a result of bugs, lags on spawn point or as a mistake of map-maker.

Note:

In case Side Commander isn’t in any Squad, he must notify Game Administrator.

You engage first slot (and it’s probably engaged by someone else) when you enter the lobby.

Penalty:

 

AR 1.1 – Denied access on project’s servers on term – up to 4 game days, if repeated – up to 12 game days.

AR 1.2 – Denies access on project’s servers on term – 3 game days, if repeated – up to 9 game days.

AR 1.3 – Denied access on project’s servers on term – 1 game day, if repeated – up to 9 game days.

AR 1.4, 1.5 – Denied access on project’s servers on term – up to 96 game days, if repeated – on undetermined term (violation of most important rule: “One game – one death”).

 

Rules Section #2.

Killing of player(s) on the same side.

In case of dying by the hands of friendly player, spoken agreement between player (squaddies, commanders, leader etc.) about it is preferred. Reports of friendly fire in court martial are not welcomed.

Teamkills are part of game play. Below are examples of friendly fire’s cause, where the responsibility is on the suffered ones (in case of second example will be found out reasonableness of such friendly fire):

False Identification:

Is followed by having no full and true information about placements of friendly and enemy squads. By a variety of causes friendly is taken as an enemy and is being shot: lack of radio communication when squad loses the orientation on place and goes where he’s not supposed to be etc.

Fire “on my position”

When enemy’s squad is in close engagement with friendly forces, in extreme cases friendlies are forced to call fire mission on their location. Meanwhile artillery or aviation or any other vehicle fires a barrage or fires to kill enemy troops who are in danger-close positions to friendlies, often on a range, which is very close to striking effects of used hardware, which can lead to friendly casualties.

 

Forbidden:

 

2.1 Killing a friendly bot with an intention to take his equipment, ammunition or to make room in vehicle.

2.2 Killing of the same-sided players

2.3 Intended killing of the same-sided players

2.0.1 Repeated unjustified reports about team-kills (when suffered one is who to blame).

 

Allowed:

Killing a same-squaded/same-sided bot if Squad leader or Side Commander allowed

Killing a friendly player as a result of Side Commander’s or Squad Leader’s (in case both player and SL are in one squad) order are allowed and is not followed by punishment.

Note:

Persons allowing to kill another same-sided player take personal responsibility on their actions and must use the principle of extreme need and justify their orders.

If the accused in TK has apologized and the suffered has accepted the apologize, denied access to servers is lifted.

Penalty:

 

AR 2.1 – Denied access on project’s servers on term – up to 4 game days, if repeated – up to 21 game days.

AR 2.2 – Denied access on project’s servers on term – up to 16 game days, if repeated – up to 48 game days.

AR 2.3 – Denied access on project’s servers on term – up to 96 game days.

AR 2.0.1 – Denied access on project’s servers on term – up to 8 game days.

 

Rules Section #3.

Side/Squad Commanding

After administrator turns on missions and makes re-assign, Side Commander must engage HQ-squad, write in chat “Blue/Red/Green SC” and control engagement of slots and assign free vehicle.

Rules of Side Commander:

Assign slots between squads (punishment: In case Squad doesn’t want to give up their slots voluntarily, squad might receive denied access till the end of mission).

Choose mission parameters (only attacking side)

End mission (admit defeat)

Forbidden:

 

3.1 – To disobey to commander of your group/squad/side, to ignore his orders

3.2 – To disobey to commander of your group/squad/side, causing loss of mission, wasting tactical plan, objectives and target set on briefing.

Note:

Both Speaker and Listener take responsibility for hints in chat.

Detour of water obstacles around the edge of map (where water obstacles end) or where the water end just before the end of map is counted as unfair game and is taken for “Using bags of games and its add-ons”, which is the violation of 4.1 project rules.

Penalty:

 

AR 3.1 - Denied access on project’s servers on term – up to 4 game days, if repeated – up to 12 game days.

AR 3.2 - Denied access on project’s servers on term – up to 16 game days, if repeated – up to 48 game days.

 

 

Rules section #4

Unfair play, the non-game communication.

 

Forbidden:

 

4.1 Using of game bugs and its add-ons - error of code and graphical glitches (for example, disappearing textures), giving an advantage over other players

4.2 Using cheats and other software, that provide an advantage over other players.

4.3 Using non-game means of communication (such as text messages in chat TS, Skype or Steam Overlay).

4.4 Watch on-line broadcasts.

4.5 Tips in chat of on-line broadcasts.

 

Allowed:

 

• Inform your squad leader or side commander by Push (Poke Client) in Team Speak (TS) in the event of communication problems or death due to a bug games.

• Watch ally on-line broadcast during the placement on slots and briefing.

 • Watch on-line broadcast gaming opponent after death.

 

Note:

• For tips in a chat responsibility carries and prompter and person, who use a prompt.

• Detour water crossing over the edge of the card (where water barrier ends), or else when the river ends right before the border of the card - it's unfair game and is equivalent to "Using the bugs of the game and its add-ons", that is a violation of paragraph 4.1 of the rules of the project.

 

Penalty:

 

AR 4.1 - restrict access to the project's servers on period - up to 16 gaming days, with recidivism (repetition) - up to 48 gaming days.

AR 4.2, 4.3, 4.4- restrict access to the project's servers for an indefinite period.

AR 4.5 - restrict access to the project's servers period from 3 to 112 gaming days, with recidivism (repetition) - for an indefinite period.

 

 

Rules section #5

Insults, use of foul language, flood.

 

Forbidden:

 

5.1 Public insult player(s) of the project, using any means of communication (game forums, game chat, channels in TS).

5.2 Intentional affront to the administration of its operations and activities in games organization (as a collegial organ and its individual members), non-constructive (unproven, unreasoned, undermines the reputation of the administration of the project) statements in its address (the project's team as a whole and its individual members), as well as any statements aimed at discrediting the project, that doesn't carry in itself the constructive criticism and proposals for improving the game-play by using any means of communication (gaming forums, game chat channels TS).

5.3 Using the foul or abusive language in any chat channels.

5.4 Flooding in the game chat during the placement on slots.

5.5 Flooding in the game’s global chat channel at a briefing.

5.6 Intentionally set markers in the global channel during the briefing.

5.7 Intentional flood by markers on the mission's map, unrelated with briefing and preventing the normal understanding of the task by players.

 

Note:

 

• «Insult» ,also, means the constant negative remarks against the participants of the project (in the well-known sense - "troll, scoff"). Responsibility for violation of this paragraph is individual and do not transferred to the group of players/squad to which an violator classing himself .

• Allowed veiled conventional expressions (Noob, tomato etc).

• After death, you get into "Channel 200" (RT), where you are allowed to express whatever you think (within reason, in first 5 minutes after death, the intensity of emotions, nerves, emotions, etc.).

• Flood in the game’s chat – there are any messages, unrelated to the current game. Comments, questions and other statements, relating to the current game (mission) by the commander of the side and squads are allowed.

• The general gaming channel intended for administrator's messages, comments and representatives of the sides / squads / teams. Using the general chat by other players is forbidden.

• False evidence at the tribunal considered as an insult to the administration.

 

Penalty:

 

AR 5.1, 5.2 - restrict access to the project's servers for an indefinite period, but not less than 4 gaming days.

AR 5.3, 5.4, 5.5 - restrict access to the project's servers on period - 1 gaming days, with recidivism (repetition) – up to 3 gaming days.

 

AR 5.6, 5.7 - - restrict access to the project's servers on period - up to 4 gaming days, with recidivism (repetition) – up to 12 gaming days.

 

 

Rules section #6

Aerial ramming, sabotage of the games.

 

Forbidden:

 

6.1 Intentionally ramming air vehicle or intentionally dumping air vehicle on the places of enemy's accumulation.

6.2 Intentionally damage allied vehicle, delay the nomination of Allied units, unmask the allied forces (shooting for no reason, playing music - a violation here will be considered by not the execution of the order to stop it).

 

Allowed:

 

Intentionally unmask the allied forces (shoot without reason, play the music) only by order of the side commander.

 

Penalty:

 

AR 6.1 - restrict access to the project's servers on period from 4 to 9 gaming days, with recidivism (repetition) – up to 24 gaming days.

AR 6.2 - restrict access to the project's servers on period – up to 4 gaming days, with recidivism (repetition) – up to 12 gaming days.

 

Rules section #7

Attacking enemy spawn and Test start

 

Forbidden:

 

7.1 attack or bombard place re-spawn (start location) or the opposite side of the zone defense in the 10 minutes after the start of the mission or before the time specified by mapmaker

7.2 You CAN NOT shoot from handguns, throw grenades, use any vehicles to drive during the place you spawned of a test run of the mission (after 21:00).

 

Allowed:

 

• Attack or bombard the enemy spawn or nearest places, IF its agreed or allowed by mapmaker or its allowed in the mission conditions.

• On the test run mission(test start): Shoot from handgun, drive vehicles, throw grenades if its allowed by game administrator or mapmaker.

 

Penalty:

 

AR 7.1 Limited access to the servers of the project for period - up to 9 days, if repeated - up from 9 to 18 game days.

AR 7.2 Access will be limited to the servers for a period – up to 1 day, if repeated -up from 1 day to 3 days.

 

 

Rules #0

Other rules of the project

 

Forbidden:

Requirements for game nick (official site, in game, in teamspeak):

should not offend other members of the project

must not contain any bad language

must not contain any symbols as for replacement or for beauty your nickname (exceptions are possible)

It must be readable

Must be same in game and in teamspeak

Forbidden to use the tag (of registered gaming team) if you not member of this team

Penalty:

 

AR 0.1 - blocking access to the WOG server before you eliminate discrepancy in you nickname.

AR 0.2 – access will be limited up to 12 days.

 

 

 

Decision-making:

Game administrator himself can decide to restrict access for a period up to 4 days. (Exception: AR 0.1, AR 0.2).

Group of game administrators (minimum 3 game administrators) may decide to restrict access for a period up to 12 days.

Super Administrator alone can decide to restrict access for a period up to 20 days.

The group of Super Administrators can decide with a term limit access for any period (permanent ban - taken by majority votes by a vote of all Super Administrators)

AR 5.2 is considered only by Super Administrator. Any Super Administrator can only temporary restrict access until the end of the proceedings.

 

Thx a lot to McLarey, PalePalp, Morgan.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this  

  • Recently Browsing   0 members

    No registered users viewing this page.

×

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.