Copy and Paste the following into the post's "BODY", answer ALL questions, and Submit the post.

============ COPY Start ============

1) Do you agree to all Rules and Regulations of the H4G Community?

2) What brought you to our Community?

3) Why do you want to join the [H4G] Community/Team/Clan?

4) Voice communication is mandatory. Do you have a Microphone and TeamSpeak?

5) What other games have you played?

6) Have you ever played on a Competition Team? If so, how long?

7) Do you know the difference between your GUN and your Weapon?

8) How old are you?

9) What else should we know?

10) Were you referred by a member (who)?

11) Do you feel you are compatible with the H4G Community?

12) Hacking, glitching, and cheating are forbidden. When was the last time you've done any of these?

13) Will you abstain from cheating, glitching or hacking?

14) What is your In-Game (Origin/Steam) name?

============ COPY End ============

After your message is posted, join us on TeamSpeak and in game so we can get to know you better. Core Admins review members' applications on the 1st of each month. A Core Admin will notify you of the decision to allow/not allow you to continue to wear tags. You are *permitted* to wear "[H4G]" tags

Revocation Your Membership can be terminated (only by a Core Admin) under (but not limited to) these cases:

Has been active for over 1 year in the community (but 1+ year members are not automatically offered)

Is chosen by INVITATION only, and Voted in by existing Core Admins

Has complete & authoritative administration rights of the Game servers, Website, and Voice servers

Has the power/authority to terminate your membership without consulting others first. (If necessary, your membership status will be discussed and voted upon at the next Core Meeting.) You may be banned and/or asked to leave the community in rare cases.

Committees:

Complaints Committee: Core Admins who resolve and arbitrate disputes about other players and admins

MapList Committee: Assigned to propose and make changes regarding Maps/Settings of game servers

You MUST include a proper REASON and YOUR NAME so we can determine why and by whom it was done.

Example: @kick PlayerName Racist comments (Eel)

For Perm Bans (by Core Admins mostly): Create a thread in the "Banlist" forum with the Date/Time, Player Name, and Reason for Ban/Suspicion.

What to Warn/Kick/Kill/Ban for:

1. NO Racist/Derogatory Chat or Names

Tolerance Level: Absolutely No tolerance.

Definition: Nigga, jew, chink, riceburner, fag, wetback, cunt etc. You know what we mean (eg Aussie kangaroo fucker is not a racial comment, it’s a joke,) Includes “fag” and any racial comment. Also includes in-game names that use these words. Not included is clan tags.

3. Be a Team Player (Don't Team-Kill or Destroy Assets, Spawn Camping or Stealing Assets or Hot Seating)

Tolerance Level: No Tolerance

Definition: Using C4 to blow up own teams assets (eg, placing C4 on the chopper or tank spawn point). This action will drive people crazy, and they will leave our servers. Spawn camping the main is sometimes a server killer, if a spawn camper is driving other players to quit then yell @kill Playername No spawncamping please Kick/ban offense. No stealing of other teams assets from main bases. You must see this happen to be acted upon. No Hotseating, where a player jumps into the gunner seat and back to the pilot seat.

Definition: This only applies when the game has less than ten players in it. Then it will be a 6 v 4 match, hard on the team of 4. Team Balancing plug-in takes care of most of this.

Exception: If its 14 v 14 and some guy changes to play with his mate, and temp. makes it 13 v 15, the game will sort it out when the next player joins or auto-balance will take care of it.

Process:

1st offense:

@fmove PlayerName (Type in Chat: No team swapping when it makes it unfair)

2nd offense:

@fmove PlayerName (Type in Chat: No team swapping when it makes it unfair)

3rd offense+:

@kick PlayerName No team swapping to make it unfair. (YourName)

5. Clan tags for Members ONLY

Tolerance Level: Medium-High

Definition: A new guy you haven’t met, can’t find him on the website, but more importantly here: He’s NOT on TS (A requirement to wear tags)

Background: New Members MUST be on Teamspeak, it’s a condition of wearing tags. That said, the object here is to Get Him Registered and on TeamSpeak, not necessarily make so much trouble for him so he removes his tags and never plays here again.We want new players, so encourage TeamSpeak use, and as a last resort, if he won’t do the right thing, ask politely that he remove the tags.

Process:

1st offense:

@yell PlayerName To wear our tags you must be on TeamSpeak. Register at our website and come talk to us.

2nd offense:

@yell PlayerName We asked you to come on TeamSpeak. Please come talk to us about your tags.

This is a detailed list of In-Game Admin commands that can be used. Note: Some commands require higher permissions than you might currently have.

Command Response Scopes (default)

!

Responses will be displayed to everyone in the server. Everyone will see "Phogue has been kicked for team killing".

@

Responses will only be displayed to the account holder that issued the command. The command issuer will see "Phogue has been kicked for team killing" but no one else will.

#

Responses will be displayed to all players that hold an account ("display to admins only"). Only account holders will see "Phogue has been kicked for team killing".

All error messages are privately sent to the command issuer

Commands (default)

Kicking / Banning

@kick [playername] [optional: reason]

Kicks a player from your server

The reason will appear in the response and is used to display to the player on the games menu

Requirements: Minimum of kick privileges

@tban [playername] [time in minutes] [optional: reason]

Temporarily bans a player from your server for a set time in minutes

The reason will appear in the response and is used to display to the player on the games menu

By default procon will not allow users with only temporary ban privileges to ban for longer than an hour

Requirements: Minimum of temporary ban privileges

@ban [playername] [optional: reason]

Permanently bans a player from your server

The reason will appear in the response and is used to display to the player on the games menu

Requirements: Permanent ban privileges

Killing

@kill [playername] [optional: reason]

Kills a player

The reason will appear in the response and message sent to the player

Requirements: Minimum of kill privileges

@nuke [optional: team]

Kills every player in the server, or if a team is specified will kill every player on that team

Has a 10 seconds countdown that can be canceled with the @cancel command

Requirements: Minimum of kill privileges

Communication

@say [text]

Says [text] for everyone to see from the Server

Requirements: Must hold an account with procon

@psay [playername] [text]

Says [text] to a specific player from the Server

Requirements: Must hold an account with procon

@yell [text]

Yells [text] for everyone to see in the middle of their screen

Requirements: Must hold an account with procon

@pyell [playername] [text]

Yells [text] to a specific player in the middle of their screen

Requirements: Must hold an account with procon

Map controls

@restart [optional: timer]

Restarts the current map

If specified will display a countdown timer than can be canceled with the @cancel command

Requirements: Must have "Use Map Functions" privileges

@nextlevel [optional: timer]

Forwards to the next level

If specified will display a countdown timer than can be canceled with the @cancel command

Requirements: Must have "Use Map Functions" privileges

Player control

@move [playername]

Moves a player to another team. Swaps them in Rush, Conquest, Squad Rush and will cycle through the 4 teams in Squad Deathmatch

Queues the player and will move them when the next die

Requirements: Must be able to move players between teams and squads privileges

@move [playername] [squad]

Moves a player into a squad on their same team

Queues the player and will move them when the next die

Requirements: Must be able to move players between teams and squads privileges

@move [playername] [team]

Moves a player onto another team in no squad

Queues the player and will move them when the next die

Requirements: Must be able to move players between teams and squads privileges

@move [playername] [team] [squad]

Moves a player onto another team and into a specific squad

Queues the player and will move them when the next die

Requirements: Must be able to move players between teams and squads privileges

@fmove

fmove functions exactly like all of the @move commands except forces the move immediately by killing the player

Requirements: Must be able to move players between teams and squads privileges

Countdowns

@cancel

Cancels all countdowns initiated by the account holder

You cannot cancel other account holders countdowns

Requirements: Must hold an account with procon

Custom Configs (basic in game command addons)

@exec

Displays a list of configs available in the /Configs/CInGameAdmin/*.cfg directory

This command replaces the "@exec -l" command of 1.6 and prior versions of the in game admin

Requirements: Must hold an account with procon (the configs validate privileges themselves)

@exec [configname]

Executes a config in the /Configs/CInGameAdmin/*.cfg directory

The config author is responsible for insuring the executing account holder has sufficient privileges

No pre-made configs are provided with procon, but you can visit the forums to download configs to extend the in game admin

You can make/edit/copy/whatever any more configs, essentially allowing you to make your own basic in game commands =)

Requirements: Must hold an account with procon (the configs validate privileges themselves)

If procon needs confirmation of your intentions it will ask "Did you mean [command]?", you can then answer !yes which will execute your confirmed command.

Argument Matching

Procon will match your command against a dictionary of possible arguments, then order the possibilities by those containing subsets of what you said.

Possibilities: "Phogue", "1349", "Sunder", "Zangen", "Sinex"

"Sangen" will match "Zangen" because only one letter is different and no possibilities have a subset of "Sangen"

"sin" will match "Sinex" because even though it is lexicographically closer to "1349", Sinex contains a subset of "sin"

Additional Information

This plugin is compatible with Basic In-Game Info's @help command

In game admin will use BF3, Vanilla bfbc2 data if available, then use punkbuster data if available.

The in game admin uses a combination of a spell checker with an auto-completer. As of 1.5 the spell checker will favour names/maps/etc that have a subset of what you typed exactly. Play around with it and let me know your horror stories with this feature on the forums =)

No one will see you issuing the commands (even you) if you prefix it with a '/'