|
|
Battlefield 2142 Battle Week Rules - Update Version 1.25
=================================================
1. Registration
a) All Squads/Clans MUST be registered with Ecliptical Realms (ER): http://www.eclipticalrealms.com/ in order to participate in Battlefield 2142 events.
b) Club Captains must have all participating members registered with ER and affiliated with their Club including the Captains approving themselves.
=================================================
2. Setup and Coordination of Matches
a) During match setup, when maps, hosts, number of matches, gameplay rules, and competing sides are chosen, players on each team should be announced to help enforce that all players in the match are signed up at Ecliptical Realms and are active on a club.
b) Match Setup and Coordination must be done in:
Battle Room
Ecliptical Realms Forum
c) Squad/Clan and Player membership should be verified prior to each battle event.
d) Each Squad/Clan must play a minimum quota of one (1) map per match round. One match consists of two (2) rounds. Within these two (2) rounds, each side must play one (1) round as PAC and one (1) round as EU. No best of 3 type battles are acceptable.
e) Squads/Clans must agree on maps, numbers of battles, gameplay rules, and players before battle starts and host launches game. This agreement should be made in the Battle Room and saved by members of both clans to be shown in cases of dispute. Please be very clear on all the fine points when negotiating a match:
Does a no vehicle rule include the stationery rail gun and AA?
Are all movements based on the game mechanics acceptable? You get the idea.
f) All Unlocks earned in ranked servers can be used. In the interests of fair play Unlock Mods are acceptable.
g) Players per game can range from 1 verses 1 to 16 versus 16. No games hosting uneven sides will be permitted/authorized or reported unless the uneven side is caused by player drop(s) after the first round begins.
h) Mixed Clan battles are acceptable although members from the same Clan must not be on opposing sides.
i) Commanders must not be used. Their final results are insufficient for reporting scores.
j) Each map result will be reported by the host as an individual game played.
k) Host is responsible for taking screenshot of scores and registering results for both teams (sides). All players are encouraged to take their own screenshot of the results of the battle.
l) Host will report results as soon as possible and at least within 24 hours after the match has been completed. Contact a moderator if you have difficulty submitting results. Results of games are to be reported at: http://www.eclipticalrealms.com/
m) Host will include a link in submitted match notes to a screenshot of the match. This will allow moderators and players to view the results. BF2142 totals do not always tally due to the nature of the scoring system and it''''''''''''''''s important moderators can check the scores in a timely manner without sending out multiple PMs.
Images can be uploaded to a site such as http://photobucket.com - http://www.filefront.com/ - http://www.tinypic.com
n) The use of exploits, glitches or cheats is strictly forbidden. Failure to abide by this rule will result in match forfeits, deletions and member bans. The Terms of Use (TOU) for this website dictate cheating and unfair play to be a violation of your membership agreement. The TOU can be found here:
http://www.eclipticalrealms.com/legal.asp
Exploits, glitches, and hacks include, amongst others not listed, - Squad Leader Beacon surfing, wall hacks, aimbots, unlimited resource hacks, no fog of war, squad hijacking, map display hacks. Keep your gameplay within the bounds of what the developers aimed for and you won''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''t go wrong. If you aren''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''t sure that something you do in game is forbidden then ask a BF2142 moderator for clarification. Don''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''t find out the hard way.
Player/Clan Disconnects During Game Event
If a Player/Clan disconnects from the game after it has officially started, it will be the Player/Clan’s responsibility to reconnect to the game as fast as possible. Even though all points are lost when disconnects occur, Players/Clans returning will contribute to their team score. If the Player/Clan does not return their score will still be recorded when game results are submitted, with all Zeros (0s).
In the event a Player or Players are unable to join the required second round, the match can be continued in one of two ways.
1. One team can field less Player or Players.
2. Subbing for a different Player or Players. However, this is only permitted if both clans negotiate its use before any matches begins. Both clans must provide the names of substitute players who will step in if needed.
If Clans do not negotiate a Subbing rule before the match begins then option 1. stands.
Fielding less players, or agreeing to subbing provides Clans flexibility to ensure the match is completed in a timely and fair manner.
Clan Forfeits
A Clan Forfeit is submitted in the event all members of one team no longer wish to continue out their match quota of (2) rounds after the first round has begun. Forfeit scores are applied as follows.
Forfeit Team
1. The forfeit team is listed with a loss.
2. The forfeit team is listed as Match Team #2.
3. 10 Deaths are applied to each individual player.
4. All other fields reported as 0
Forfeit Victim
The forfeit victim is not listed in the match submission at all. A forfeit score is a punishment for the Forfeit Team. The general concensus amongst active clans is a win should be earned and this rule reflects that.
Unless the Host Game Crashes, the game will continue to the end. A third party host crash will require the battle to be replayed. A team host crash will be considered a forfeit unless the opposing team agrees to replay. In the interests of fair play a replay is the recommended course of action.
=================================================
3. Host Setup and Configuration
Hosting will require a good connection to ensure stability. Please take this into account when selecting a host for your club. To ensure stability the battle recorder must not be used. Using the battle recorder can cause network drain and create lag. Host crashes caused by instability or use of the battle recorder will result in a host forfeit.
Host Server Settings
Dedicated Server Settings
1. Gametype: Conquest Mode
2. Server Name: CW# - (club tag vs club tag)
3. Password: As per agreement
4. Internet: ON
5. UseGlobalRank: ON
6. AllowFreeCam: OFF
7. AllowExternalViews: ON
8. AllowNoseCam: ON
9. HitIndicator: ON
10. StartDelay: 30
11. SpawnTime: 10
12. TicketRatio: 20 Per Player
Please note that scores you set are a percentage of the base figure. A 16 man map has a base of 100 tickets and a 32 man map has a base of 200 tickets.
A 16 man map with base tickets set at 100 would give the following: 4vs4 = 80, 6vs6 = 120, etc.
A 32 man map with base tickets set at 200 would give the following: 10vs10 = 100, 12vs12 = 120, etc.
Take care you set the correct percentage for the map size and number of players.
Dedicated servers allows for any number for the Ticket Ratio but ingame servers only allow multiples of 10. 10 per player is a little low so 20 will be used. This may be changed in future based on feedback.
13. RoundsPerMap: 2 for third hosting all battles and 1 for clan server as the next round is played on the other team''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''s host.
14. TimeLimit: 0
15. SoldierFriendlyFire: 100
16. VehicleFriendlyFire: 100
17. SoldierSplashFriendlyFire: 100
18. VehicleSplashFriendlyFire: 100
19. FriendlyFireWithMines: ON
20. TkPunishEnabled: OFF
21. TkPunishByDefault: ON
22. VotingEnabled: ON
23. VoteTime: 60
24. MinPlayersForVoting: 1
25. AutoBalanceTeam: OFF
26. PunkBuster: ON
Remaining settings as per default/agreement.
Client Server Settings
1. Gametype: Conquest Mode
2. Server Name: CW# - (club tag vs club tag)
3. Password: As per agreement
4. Auto Balance: OFF
5. Friendly Fire: ON
6. Spawn Time: 10s
7. Max Players: As per battle
8. Time Limit: 0s
9. TicketRatio: 20 Per Player
Please note that scores you set are a percentage of the base figure. A 16 man map has a base of 100 tickets and a 32 man map has a base of 200 tickets.
A 16 man map with base tickets set at 100 would give the following: 4vs4 = 80, 6vs6 = 120, etc.
A 32 man map with base tickets set at 200 would give the following: 10vs10 = 100, 12vs12 = 120, etc.
Take care you set the correct percentage for the map size and number of players.
10. Rounds Per Map: 1 (fair hosting rule)
=================================================
Battle Etiquette and Strategy
Unlike Tournaments, Battle events do not force Clans or Players to accept challenges or meet a match quota beyond the initial 2 rounds. Putting Clans/Players under undue pressure to battle, especially when the odds are stacked heavily against them, inevitably causes friction and hostility.
However, before making a challenge or declining a battle, players should be reminded that the statistics used in this event are weighted to ensure that a loss to a higher ranking player can be beneficial based on the participation and average rank played awards. In addition, higher ranking players consistantly playing against much lower ranking players can see a detrimental effect on their rating due to the average rank played award.
If Players/Clans are not accepting battle challenges attempt to change your negotiating strategy to make the battle more appealing. Increasing the battle player count or replacing players to make the playing field more even will make the battle more inviting.
The more players there are in the Battle Room at any one time the better the opportunity for reaching an agreement regardless of the range of ability.
Play fair, be friendly, and have fun. |
|
 |
Browsing as a Guest.
Logon to access more features
Your IP: 13.59.134.65
|
 |
|
|
|
|
