Forum

I post news because I have permission to do that :-)

The best idea way to ban is ban for MAC adress.

Lazy and low losers won't check Google for sure
Ban by name = another account
Ban by IP = sometimes router restart is enough

Hi people.

Rules creed for Winter League is completed. To read the Rules Creed click the news title.

More informations about Winter League coming soon. Probably tommorow


Part 1.General League informations:

- League system is table system, open season, without play-offs.
- Number of season weeks is rigid depending on the number of teams signed in.
- Only one league round per season. Every clan must play one match with all of the opponents.
- Two maps per one match. Both teams must select their map.
- Once selected map by exampled team cannot be selected again anymore by this team in the season.
- Open season is preceded by two Pre-Season matches for every team. Pre-Season is to determine what teams show up and who do not. If a team misses a Pre-Season match without prior notice they get removed from the League unless they have a valid excuse for not showing up.
- PreSeason period is one week.
- This tournament has an open season- Every season week there is one match. Every team has one week to play their match. Every week must be ended before incoming monday.


PART 2- Team Management

- The roster minimum is 5 players. This means a team needs to have a minimum of 5 players on their roster in order to be eligible to play.
- The team captain is responsible for his roster. If anyone in a team is caught cheating, using bugs or smurfing, the team will be punished also.
- There is no maximum amount of players on a roster.

PART 3- Server Requirements

- The latest version of the CVAR scripts should be running on the server
- Team captains of the teams should be online during the match in case there is a dispute or server crashes.
- The server should be running in Tournament Mode.
- In some of the cases league admins will have to monitor matches. This means that if a league admin has to spectate a match, he should be given access to the server as an administrator.
- Server has to be located in Europe, unless both teams do not agree
- A neutral located server always has priority over other servers, unless the opponent is located outside of Europe. If no compromise about the server can be made, both teams play their map on their server. If teams still can not compromise, admins will make the final decision.
- A team does not have the right to dispute about bad servers anymore if they still played the match. They can only protest against it during the setup round, any round played after that counts. If in the middle of the match server side issues appear, the other team has to request a discard in the start of the round, and addresses the issues.

PART 4- Server Settings
Configuration Tab:

- Game Password: Your Choice (must be posted in match comms)
-  Minimum Player Honor Level: 1
-  Maximum Player Honor Level: 100
-  Delayed Start Options: Disabled
-  Maximum Players: As high as your server allows
-  Maximum Admins: 3
-  Auto-Balance Options: Never Auto Balance Teams
-  Game Play Mode: Force Live Fire Weapons

Rules Tab:
-  Enable Multiplayer cheats: Off
-  Show Death Messages: On
-  Rounds Per Match: 12
-  Round Time Limit: Map Dependent
-  Spectator Rules: Players only first person view
-  Scoreboard Display Rules: Scoreboard always available
-  Friendly Fire Roe Limit: x
-  Kick Player for Early Roe: Off
-  Roe Violations Options: Ignore Violations
-  Idle Player Kick Minutes: Disabled
-  Idle Player Kick Rounds: Disables
-  HUD Options for Enhanced Difficulty: All Unchecked

Tournament Tab:
-  Match Name:
-  League Name:
-  Tournament Name: League Name
-  Home ?Team?: Defending team
-  Away ?Team?: Attacking team
-  Require Team Passwords: On
-  ?Home? Team Password: Team Choice (post in Match Comms if this is for opposing team)
-  ?Away? Team Password: Team Choice (post in Match Comms if this is for opposing team)
-  Requested Pause length: 180 seconds
-  Swap Sides Every: 6 rounds
-  Swap Delay: 180
-  Mission Planning time: 4 minutes
-  Captain Request Delay: 30 Seconds
-  Delay Between Rounds: 10 seconds
-  Tie Breaking Rules: Allow Ties
-  Use Endex Rule: Off
-  Open All Weapons Slots: Off
-  Allow Team Captains: On
-  Random Side Starts: Off

PART 5- Match details (score reporting, dispute, resheduling)

Preparation for the Match

In the days/hours leading up to a match both teams are required to familiarize themselves with the General League Rules and League Specific Rules. The team providing the server is to also ensure that it complies with the Server Requirements and that it is setup properly as per the Server Settings rule. When the teams enter the server they will join their side using the team password. One player from each team will choose the Team Captain spot.

Setup (Mission Planning) Round

The Mission Planning round must begin no later than 10 minutes after the scheduled match time. As long as there is at least 1 player present from both teams this can happen. The short handed team(s) then has the length of the planning round to get the rest of their players on the server. If one team has no members on the server at the 10 minute mark then the team that is on the server will take a screenshot of the F1 screen showing their presence then leave the server and file a no-show dispute. If both teams have all members on the server and assigned to the proper team before the 10 minute mark then the team captains should select ready to begin the planning round early.

During the Mission Planning round the teams are to verify the following:

?   All opposing players are on the opponent's roster and are eligible for the match.
?   The server is set to the proper map and the proper number of rounds is set.
?   Captains, via the Tournament Panel, need check if all the server settings are all right
?   All players should move around the server to check for lag or warping issues. If the server is extremely laggy for multiple players on a team then each should open their console, type stat net, and take a screenshot. Discuss multiple player lag issues with your opponent. If the opponent is also experiencing the problem, quickly move to a different server. If no other server is available or both teams are still having issues on the second server, then reschedule the match to be played on a later date.

Teams failing to perform the checks above forfeit their right to dispute over them once the match goes live

Once the Mission Planning round ends the match must go "Live", even if all players from a team are not yet present. However teams are always encouraged to show some sportsmanship and wait if it is really needed. Teams beginning the match with less than the max number of players may subsequently bring them in during discarded rounds. The exception to this rule is if a team does not have the required minimum amount of players present, which is 3. In this scenario the match ends and the team in question will report a forfeit loss.

In Between Live Rounds

If a team asks for a discard before the next round starts. Both teams need to discard that round.

Live Rounds

Additional Server Setting Checks
During the first live round of the match there are some server settings that need to be checked.

?   Round Time
?   Spectator View is set to 1st Person

The settings above cannot be checked during the Mission Planning round under TM. Teams noticing any of these settings to be wrong should immediately notify their opponent. The round will then stop, the setting will be fixed, and the match will start over. These settings can only get brought up for repair during the 1st Live Round of the match. If they are noticed later, they cannot be changed and neither team can dispute over them.

Match Play Potential Issues

Tournament Mode Issues
Tournament Mode does not properly score rounds played on SF Sandstorm and MOUT McKenna due to TWL's 2 of 3 objective rule. Teams must manually keep score and report the end of each round in global comms on those maps.

Server Crashes
In the event of a server crash, the last round will be replayed with the number of players that were alive in the round when the crash took place. The replay round will begin and immediately all players that were dead before the server crash will suicide. The remaining players will have the full time limit to complete the round.

Stopping Live Play
Live Round play is not to be stopped unless agreed to by both teams. There are 3 known exceptions to this rule.

The first two exceptions are situations where a player fails to spawn or has a Critical Error causing game crash at the beginning of the round. If the team with the member having one of these problems reports the condition to the opponent via captain's chat or global chat within the first 20 seconds of the round, the opponent is required to discard the round. Failure to abide by this rule will result in a round forfeit on the part of the team refusing to honor the discard request. In the case that this problem occurs, the team that requested a discard round should dispute the match after it is finished, notify their opponent that they are leaving to file a dispute for refusing to honor their discard request. The round or rounds in which the opposing team did not discard while they should have given one will be won rounds for the team with the crashed player. The opponent can, at their discretion, attempt to verify the validity of the discard request "after" granting it by checking to see if the player didn't spawn or has crashed. Having a player a few feet above the ground usually indicates that he did not spawn. Signs that someone has crashed would be the character idle at spawn or walking into walls. Obviously, if the crashed player has left the server no signs can be found. If the opponent feels that the request was invalid, they may leave the match and dispute. However, if the dispute is overturned they will forfeit the remaining match rounds.

The final exception applies to no objective spawning on maps with a moveable objective. When a team discovers the objective is not in its location, they are to notify the opponent via captain's chat or global chat and the round must be discarded. The same procedures from the paragraph above apply for teams refusing to discard or for teams improperly making the discard request.


PART 6- Anti-Cheat (AC client, cvars, demo recording)

In this league we have no dedicated AC Client running. However teams are obligated to run the latest CVAR checks.
In case of a dispute, all team members should have a demorec of the match available. They should be handed in if the admin team asks for it. Failure to do so will lead to a forfeit win or replay, depending on the severeness of the situation.

PART 7- Cheating/Smurfing

Cheating and smurfing are strictly forbidden. Using known exploits will result in a loss of the round in which the exploit was used.
- Known bugs: Jumping on the wooden plank below west to get on the ledge
Jumping on the wall at dusk near middle building in order to flank embassy
Alpha bugspot not allowed to prone there?

PART 8- Penalties for rules infractions

- Cheating will result in a removal of the player from the game, losing the match 12-0, losing all matches in which the cheating player has played with 12-0 and in case the team obviously knew about this the team will also be removed from the tournament.
- Smurfing will result in losing the match with 12-0 and removing the players smurfing from the tournament.
- Exploiting known bugs in the game will have penalties
- First exploit: Round loss
- Second exploit: Match loss 12-0
- Third exploit: Ban from the league for that player, match loss 12-0

PART 9- Admin structure

At this moment there are five admins in the team.
The admin team consists of:
-   SNLSTB.Bart^
-   [Majestic]tidididi
-   [PTWars]B!6
-   =IGC=Smoke
-   Mortiferus.David-mad

PART 10- General Statement

-   All rules are to be viewed as 'General Guidelines'. Certain situations may require an admin override a posted rule if it is felt to be in the best interest of the community or teams involved.

The rule set can be modified.

I didn't say you are crying

To end this and be honest, my name is missing on that sound violation list : /

Strange. We will cry.

I remember seeing 260+.

I remember seeing 2500.

I think that. What happened to him? Did Alechko closed him in his basement, or something?

Yes Spanky, I noticed the site admin rights, thanks.

Wow, you have sent me very interesting stuff. Thanks very much. It's really great the Crusade helps.

***line removed***

What was that Jonnys "backup plan"? Going linux-only (he mentioned this to me in one of PMs)?

I must tell you I'm starting to view this anti-cheat effort as personally attractive to me. I have zero experience with strictly game-related code, but I feel comfortable in low-level stuff in general (when I was younger :-D I've coded my own kernel with memory protection, processes, threads and all that, and I knew x86 instruction set by heart, so that I could code in binary :-D).

One of the things I was already planning, is to re-write the Assist in C or C++. That will also help with anti-cheat things as we will have more control over the Assist process than with Realbasic.

I'm currently taking care of some pending issues related to my house, kids, etc. (that's why I haven't done any real work yet, only posting BS on forum ;-D), but as soon I finish most urgent stuff, I hope to finally get some time for real work on Assist.

Thanks for those PMs again.

LOL