• ZSU Gaming
  • Discord
  • Patreon
  • Steam
  • Home
  • Matches

  • EsC Season 8 – Series 1 (second)

Battle Ground ch

Players:

  • Aluka
  • Faker
October 24, 2019 12:00 pm
10 : 10

Kukang be

Players:

  • GaRpY
  • Bowman
  • Tournament: Esports Championship Series Season 8
  • Tournament Stage: Series 1

Videos

Screenshots

Copyright © 2021 ZSU Gaming

Top Background Image Bottom Background Image

Search

General Gameplay
1.1. Players must not create Squads with names (or use in-game names) that contain language that is offensive to the average person.
1.2. Players must be actively playing and contributing to the team’s efforts in the game.
1.3. Players must not use the Vote Kick system maliciously, excessively or without a valid reason. Initiating player must be a direct witness to an event to initiate a vote
1.4. Players are to utilize their own radios clearly.
1.4.1. Players must not spam voice or text chat with the intent to disrupt and/or annoy other players.
1.4.2.Players are allowed to take an enemy radio. Transmitting across the enemy radio is not acceptable.
1.5. Players must not grief or impede the gameplay of their team or teammates. (This Includes Team Killing, Shooting Friendlies or damaging friendly buildings/vehicles.)
1.5.1. Players will not kill another teammate that has killed them previously, or another teammate. (Revenge Team Killing/ Intentional Team Killing.)
1.6. Enemy Main Operating Base camping is allowed (Everon), however an admin may ask any player to pull back to normal objectives at any time, should they deem it unproductive. Failure to reasonably comply will result in admin action.
1.6.1 Enemy Main Operating Base camping is not allowed (Arland and other maps). A buffer zone of One objective is to be maintained, Meaning you can cap the objective that leads to their base, but not progress further in
1.7. Admins may make directives to players at any time. Non-compliance with an admin directive may result in removal from the server.
1.8. Using enemy equipment is acceptable, But may lead to friendlies mistaking you for an enemy.
1.9. A player that utilises the arsenal will bring the appropriate amount of supplies for the engagement. E.G. A player engaging in backline harassment of the enemy may bring in additional supplies, medical, ammunition etc. These supplies shouldn’t be excessive (150GLs, 20 Sniper magazines, >150 supply) Use common sense, an admin may direct the player to adjust their loadout should it cost too much supply
1.10. Radios must be placed in a position that is reasonably accessible by foot (able to be climbed up to, etc.) and interactable with. If the radio is not interactable the player placing is to make an attempt to destroy the radio and is not allowed to spawn on it.

Vehicles
2.1. Players must not abuse vehicles or the role of the vehicle – Players must not do the following;
2.1.1. Single crew high supply cost vehicles that require two crew to effectively use. This specifically includes the BTR-70, BRDM and LAV-25 (or any future armoured vehicle like these.)
2.1.2. Use helicopters to intentionally ram/kamikaze.
2.1.3. Use our servers to practice flying helicopters.
2.1.4. Use a vehicle to disrupt a friendly vehicle or player in any way. (This includes Ramming.)
2.2. A person that spawns a vehicle is the owner of the vehicle. They can appoint a driver if they do not wish to do so themselves.

Bases and Construction
3.1.The player will not perform The act of “digging down” or deconstructing a base, With the exceptions of;
3.1.1. Arsenals can be deconstructed to provide supplies/ensure spawns at frontline bases.
3.1.2. A base is being rebuilt, restructured or reinforced and it is required to remove a structure.
3.1.3. Additional buildings have been constructed and not required. I.E. Three Arsenals.
3.1.4. The base belongs to the enemy.

Fire Support Assets
4.1. Mortar operators should use a spotter/forward observer on any strike area, randomly firing mortars and killing friendlies will be dealt with as Intentional Team Killing. Any person who calls in a mortar strike on friendlies may be dealt with as committing Intentional Team Killing and potentially the mortar operator.
4.2. Mortar and rocket helicopter strikes are to be called in on Platoon radio with enough time for friendlies to react and call a ceasefire before the strike starts. Failure to communicate and TKing may result in admin action. This is not required when a helicopter has been called in on a specific enemy target by a friendly.
4.3. Mortars are not to be fired at or from within a Main Operating Base.
4.4. Rocket helicopter strikes are not to be conducted on the enemy Main Operating Base.

Common server rules

The ZSU Gaming Squad Servers fall under the Squad Code of Conduct – which is a rule list for all licensed servers. This may be found here: https://joinsquad.com/code-of-conduct/

Applies to all ZSU Gaming Public and Private Servers

1.1.    Players must play the game as intended.

1.2.    Players must not intentionally teamkill.

1.3.     Players must not hack or alter the game.

1.4.    Players must not intentionally glitch or exploit the game to gain an advantage. (i.e: Placing an emplacement in a river, rock or unreachable area so as to guarantee its safety)

1.5.    Players must play with respect and act with teamwork and communication in mind.

1.6.    Our server is based in Australia and is primarily an English-speaking server. Players must not engage in squad leading and/or leadership positions if they are unable to speak English.

1.7.    Players must not pretend to be an admin of our servers, pretend to be a community representative of ZSU Gaming, or impersonate another person entirely.

1.8.    Players must not make abusive comments towards other players or admins

1.9.    Players must not participate in any form of discrimination and/or abusive comments made against or towards fellow players.

1.10.    Players must not partake in metagaming or stream sniping – that is a player’s use or revealing of knowledge concerning the state of the game to influence either their or others’ actions when said persons would have no relevant knowledge or awareness under the circumstances.

1.11.    Players threatening the integrity of the server or players may be removed permanently at any time – there is a zero-tolerance policy to DDoS threats or other malicious actions.

squad server rules

This applies to all ZSU Gaming Squad Servers

2.1.    Players must not abuse vehicles or the role of the vehicle – ie. dumping vehicles with no intention to reuse them, and/or using a vehicle as a personal transport. This includes using a vehicle to ram other vehicles or using a vehicle to disrupt a friendly vehicle or player in any way.

2.2.    Players must not create Squads with names (or use in-game names) that contain language that is offensive to the average person. In-game names must contain more than 2 characters.

2.3.    This server is not a training ground for competitive clans.

2.4.    For any vehicles that require crewmen to operate the gunner position, you must have 2 crewmen within the vehicle. The sole exceptions to this rule are the MTLB APC and Bulldog APC.

2.5.    Players must not shoot emplacements or vehicles out of base protection zone – the only exception to this is if you are being camped at main by the enemy and need to do so to leave.

2.6.    Leaders of Squads must play using the Squad Leader, Lead Crewman or Lead Pilot Kit.

2.7.    Players must not create a squad or take the Commander role if they do not intend to lead.

2.8.    Players must join a Squad.

2.9.     Players must be actively playing and contributing to the team’s efforts in the game.

2.10.    Players must not use the unarmed player kit.

2.11.    Players must not manipulate the Map or Commander Vote system. ie. creating a squad, placing a vote, and then disbanding afterwards.

2.12.    Players must not spam voice or text chat with the intent to disrupt and/or annoy other players.

2.13.    Players must not grief or impede the gameplay of their team or teammates.

2.14.    Post-seeding, players should not rush caps past the mid-cap as the first game after seeding is always the most fragile and can lead to continual stomping after the first game.

2.15.    Main camping is allowed, however an admin may ask any squad to pull back to objectives at any time, should they deem it unproductive. Failure to reasonably comply will result in admin action.

2.16.    Admins may make directives to players at any time. Non-compliance with an admin directive may result in removal from the server.

ADDITIONAL SEEDING RULES – WHILST BELOW 40 PLAYERS

3.13.    Players must not advance on, camp or attack HABs in any way.

3.14.    Players must not place or use offensive emplacements.

3.15.    Players must fight over the centre cap/s – Cap and Hold – go no further.

3.16.    Attackers must attack the center cap/s, defenders must defend the center cap/s. Players are to contain fighting to the centre cap/s.

3.17.    No HAB is to be placed within 150m of the closest centre cap/s. (The inner ring of a Radio creation marker is 150m from its centre point)

3.18.    Only one Radio per team is allowed. Insurgents may have 2 HABs, but only one Radio.

Make sure you follow all of these instructions well in advance of mission times, which are 2030 on Tuesdays and Thursdays, 1930 on Sundays, Sydney time (Image for assistance: https://imgur.com/a/cpQpv6v)

Download (subscribe to) the following Steam mod collection first: https://steamcommunity.com/sharedfiles/filedetails/?id=2092744812  

  1. Download ArmA3Sync from http://www.armaholic.com/page.php?id=22199 (the download link is located near the bottom of the page). Install and Open ArmA3Sync once downloaded, if prompted to find your ARMA 3 directory, point it to your arma3_x64.exe file (Generally found here: Program Files (x86)\Steam\steamapps\common\Arma 3).
  2. In the ArmA3Sync program, enter the ‘Addon Options’ tab and click the blue plus symbol on the far-right side, and navigate back to your ARMA 3 directory (as in step 1) unless you specifically store your mods elsewhere.
  3. Enter the ‘Repositories’ tab of ArmA3Sync and click the blue plus symbol, then in the ‘Public auto-config url’ section, paste: ftp://repo.zsu.gg/mission/.a3s/autoconfig then click the “Import” button – click the ‘Ok’ button once all the boxes have been filled out for you.
  4. In the ‘Repositories’ tab select the ‘Notify’ checkbox for the ‘ZSU ARMA3 Mission Repo’ then click the ‘connect to repository’ button (bottom-most button) to enter the repo.
  5. Tick the ‘Auto-Discover’ box then click the green tick on the far left so that ArmA3Sync automatically finds the Steam Workshop mods that you downloaded in step 1. Once it has finished checking for addons, tick the ‘@ZSU-Missions-Repo’ box, then open the ‘Settings’ menu and set ‘Max Connections’ to 10, then click the download button (black play button). All the mods under the ‘@Common’ folder will be the mods you downloaded in step 1, the mods under ‘@ZSU-Missions-Repo’ are the mods you will download through ArmA3Sync.
  6. In the meantime, download and install TeamSpeak3 from https://www.teamspeak.com/en/downloads/. Once TS3 is installed and the modset has been downloaded, navigate to Arma 3\@ZSU-Missions-Repo\@ZSU_M-Core\plugins and run the plugin installer as an admin to install Task Force Radio (TFAR). If you have a previous version of TFAR already installed, uninstall it before installing this version. Once the plugin is installed, Open Teamspeak, & head to options (Alt + P) and set up a push-to-talk button under the ‘Hotkey’ section. To use push-to-talk in ARMA you must run TS3 in admin mode. To do this right click the TS3 executable, click properties, compatibility, and tick ‘Run this program as an administrator’. Our Teamspeak server address is: arma.zsu.gg
  7. Once the repository download is finished in Arma3sync, enter the ‘Addons’ tab and click the ‘Modsets’ button (blue plus button). Tick the ‘ZSU ARMA 3 Mission Repo’ repo, click OK, and a folder with all the mods synchronized with the repository will appear on the Addon Groups panel on the right. Tick the ‘ZSU ARMA 3 Mission Repo’ box and click start game to launch ARMA 3 with our modset. Do not put any info in the Join Server area. When playing our ops, you must launch through ARMA 3 Sync.

Make sure you follow all of these instructions and book an induction well in advance of mission times which are 2030 on Tuesdays, and 1930 on Thursdays & Sundays Sydney time. (Image for assistance: https://imgur.com/a/cpQpv6v)

0. Download (subscribe to) the following Steam mod collection first: https://steamcommunity.com/sharedfiles/filedetails/?id=2092744812

  1. Download ArmA3Sync from https://zsu.gg/content_static/uploads/2021/11/arma3sync-installer-1-7-106.exe – Install and Open ArmA3Sync once downloaded, if prompted to find your ARMA 3 directory, point it to your arma3_x64.exe file (Generally found here: Program Files (x86)\Steam\steamapps\common\Arma 3).
  2. In the ArmA3Sync program, enter the ‘Addon Options’ tab and click the blue plus symbol on the far-right side, and navigate back to your ARMA 3 directory (as in Step 1) unless you specifically store your mods elsewhere.
  3. Enter the ‘Repositories’ tab of ArmA3Sync and click the blue plus symbol, then in the ‘Public auto-config url’ section, paste: ftp://repo.zsu.gg/mission/.a3s/autoconfig then click the “Import” button – click the ‘Ok’ button once all the boxes have been filled out for you.
  4. In the ‘Repositories’ tab select the ‘Notify’ checkbox for the ‘ZSU ARMA3 Mission Repo’ then click the ‘Connect to repository’ button (bottom-most button) to enter the repo.
  5. Tick the ‘Auto-Discover’ box then click the green tick on the far left so that ArmA3Sync automatically finds the Steam Workshop mods that you downloaded in step 1. Once it has finished checking for addons, tick the ‘@ZSU-Missions-Repo’ box, then open the ‘Settings’ menu and set ‘Max Connections’ to 10, then click the download button (black play button). All the mods under the ‘@Common’ folder will be the mods you downloaded in step 1, the mods under ‘@ZSU-Missions-Repo’ are the mods you will download through ArmA3Sync.
  6. In the meantime, download and install TeamSpeak3 from https://www.teamspeak.com/en/downloads/. Once TS3 is installed and the modset has been downloaded, navigate to Arma 3\@ZSU-Missions-Repo\@ZSU_M-Core\plugins and run the plugin installer as an admin to install Task Force Radio (TFAR). If you have a previous version of TFAR already installed, uninstall it before installing this version. Once the plugin is installed, Open Teamspeak, & head to options (Alt + P) and set up a push-to-talk button under the ‘Hotkey’ section. To use push-to-talk in ARMA you must run TS3 in admin mode. To do this right click the TS3 executable, click properties, compatibility, and tick ‘Run this program as an administrator’. Our Teamspeak server address is: arma.zsu.gg
  7. Once the repository download is finished in Arma3sync, enter the ‘Addons’ tab and click the ‘Modsets’ button (blue plus button). Tick the ‘ZSU ARMA 3 Mission Repo’ repo, click OK, and a folder with all the mods synchronized with the repository will appear on the Addon Groups panel on the right. Tick the ‘ZSU ARMA 3 Mission Repo’ box and click start game to launch ARMA 3 with our modset. Do not put any info in the Join Server area. When playing our ops, you must launch through ARMA 3 Sync.

You’re good to go! If you haven’t already, contact one of our ARMA Instructors in #arma-general of our Discord. We’ll get an induction organised for you and make sure you’re set for your first mission.

YEET!