HGG is proud to announce the fruit of our hard labor: a brand new server providing a fun, relaxed game play style.
Here in #HGG we aim to put the fun back in PR and other games in general. We believe in the empowerment of the player base and making the players have control and admins that only serves as guides and not dictators.
Our aim with this server is to provide a no bullshit, no heavy restriction and a fun server to play in. We have chosen to give the players a free reign of control with regards to map votes and other aspect of gameplay.
We believe on giving the player Rights and trusting the player base to make the right and logical decisions on matters such as map votes and general gameplay mechanics. The rules that we are about to employ in our servers are designed in a way to balance the fun and playability of the gameplay in the server.
General Rules
1.1 The Admins decisions about certain matters in the server are final.
1.1.1. All bans, kick, warnings and announcements are final.
1.2 Glitching, hacking and ghosting are ban-able offenses. We will investigate every claims of cheating via all means available immediately.
1.2.1. Griefing is a ban-able offense.
1.2.2. Everything will be reported in the admin section forums of PR.
1.3 Intentional Team Killing is not allowed and will not be tolerated.
1.3.1. 5 intentional TK with punish will result in a kick and a temporary ban.
1.3.1.1. In events wherein friendly units are mixed in with enemy combatants and accidental team kills happened, The perpetrator will only receive one warning. Failure to adhere to that warning will result in a kick. We call this the ?Trail Mix? rule.
1.4 Claims must be asset category specific.
1.4.1. Whoever stakes the first claim shall have the right to use the asset category or specific asset according to claim.
1.4.2. Only assets that require certain kits for operation can be claimable.(pilot, crewman)
1.4.2.1. Assets such as humvees, technicals, rocket techie, spg, logistics trucks, trans trucks and lights transport boats are not claimable assets since the asset requires no special kit to operate.
1.4.2.1.1. All of this will come in a first come first serve basis.
1.5 Mumble dj's are allowed.
1.5.1. However, the operator must cease playing music in certain situations such as fire fights, briefings and other events that may distract other players from focusing in the game.
1.5.2. The operator must also cease playing music once asked by anyone in the immediate surrounding area covered by local speech.
1.5.2.1. It can be done via team chat or mumble voice and must be asked in a nice manner.
1.5.3 Failure to do so for the operator will result in a kick.
1.6 All chat is allowed but is discouraged.
1.6.1. We allow trash talking in all chat but it must be done in a way that it is not distracting to the other players.
1.6.1.1. Admins will monitor all chat and would have the freedom to announce ?CUTTING ALL CHAT COMMS? if the chat has been excessive and falls under the categories of:
1.6.1.1.1. The ?Annoying chat rule?
1.6.1.1.1.1. This is when the chatter gets annoying and is not entertaining anymore to anyone.
1.6.1.1.2 The ?Not Funny Rule?.
1.6.1.1.2.1. This is when the direction of the chat is leading to situations where it is no longer funny, constructive or is nowhere near the initial topic of the trash talk.
1.6.1.1.2.2. This includes spouting memes in all chat.
1.6.1.1.3 The ?Personal rule?.
1.6.1.1.3.1. Trash talking involves insults but excessive insults are generally frowned upon.
1.7. Map votes is a right.
Gameplay Rules
2.1 No locked squads until certain conditions are met:
2.1.1. Asset squads requires at least 6 people to be locked
2.1.2. Infantry can lock at 6 but is generally advised to keep open to give other players some chance to join squads.
2.1.2.1. A squad could lock squad below the limit only if they meet certain conditions
2.1.2.1.1. They are securing a slot for a friend(s), clan mate(s) that is on the other team or trying to join the server.
2.1.2.1.1.1. A time limit of 10 minutes since the formation of the squad will be given before they will be forced to open up and let other people join in.
2.1.2.2 There is no unassigned non-afk player that has no squad.
2.2 Claims must be asset category specific
2.2.1. Whoever claims that asset first has the sole right to use that asset.
2.2.1.1. In cases wherein the squad that claims the asset is not in base and hasn't been using the asset, Any squad can use that said asset provided that they are given explicit permission to do so by the Squad leader of the asset claiming squad.
2.2.2. In most cases, we won't require the squad trying to claim the asset to use the specific model designations. Especially in occasions wherein a layer of the map has two or more different variants that performs the same category. There are certain exceptions provided.
2.2.2.1. Squad names such as CAS, Tanks and APC's are allowed if the available assets models for the same category can be used simultaneously by one squad being (2 crewmen/vehicle)
2.2.2.1.1. Tanks are not included in this.
2.2.2.1.1.1. However, a 2nd tank squad can be created but an explicit permission must be granted by the squad leader of the 1st tank squad.
2.2.2.2. CAS squads will have the rights to use both Fixed wing and Rotary assets granted that they meet certain conditions.
2.2.2.2.1. The amount of Pilots and spotters needed to operate ALL of the available CAS assets(fixed wing, rotary) can be done by 1 squad of no less than 6 pilots.
2.2.2.2.2. CAS classification will include the following rotary aircrafts models apart from the widely accepted, Z10, Havoc Mi-28, Cobra, Apache)
2.2.2.2.2.1. Zhi-9(atgm and Rocketpod variants), CAS huey, Mi-24V(20-30mm cannon variant with ATGM)
2.2.2.3. Transport squad will have control over light duty, medium duty and heavy duty transports.
2.2.2.3.1. Mi-24p (non-atgm variant w/ 6 passenger capacity.) is classified as a transport chopper.
2.2.2.3.2. In cases wherein a layer would only spawn 2-3 trans assets, the squad lock rule does not apply and the squad leader can lock squad whenever he feels like.
2.3 Kits such as sniper, hat, AA and other specialized and limited assets are not claimable.
2.3.1. We also don't tolerate stealing limited kits off squads.
2.3.1.1. It is defined by joining the squad, getting the kit and leaving immediately without the explicit permission of the squad leader of the squad where the kit was taken from.
2.3.1.1.1. Violators will be warned and be given a grace period of 5 minutes depending on circumstances to return the kit before being kicked from the server.
2.4 No C4 heli drops are not allowed in insurgency.
2.4.1. It is a waste of time since it is harder to kill caches now.
2.5 Roadkills are legal both with road and air vehicles.
2.5.1. This is covered by the ?Stupidity clause? which states that ?If you're too stupid to get hit or killed by something you can hear or see coming from a mile away, then you deserve that death.?
BASE, FOB and CAP rules
3.1 No mortars or FOB within DoD.
3.1.1. Entirely dependent on BaseRape rules for INS
3.2 There will be no asset rushing for the enemy first flag.
3.2.1. Infantry can rush without the help any asset.
3.2.1.1. The only exception will be applied towards air transport asset.
3.2.1.1.1. It will not be allowed to loiter and provide support to the ground rushing troops.
3.2.1.1.2. Light armored vehicles such as Humvee's, Land rovers, G-wagon, MTLB(heavy mg variant), buggy and VN3 are allowed to rush
3.2.1.1.2.1. Vehicles such as Stryker, MTLB(30mm variant), LAV-25 and vehicles with heavier armor and or armaments greater than 20mm cannot participate in rush.
3.3 Base rape is a big no-no, except on last flag (and docks repair station in muttrah), and nothing closer to 2 grids of main.
Additional Server Rules
4.1 Clans and groups are allowed to recruit players in our server but must ask for permission from the group or server admin.
4.1.1. The group has to setup an agreement with us if you want to recruit via our server.
4.2 Hostilities towards server admins will not be tolerated especially if it is not justifiable.
4.2.1. WE will kick and permanently ban anyone who acts hostile towards our server admins. We are running this server out of our pockets and putting time in the game to keep everything running. Our goal is for everyone to enjoy the game.
4.2.1.1. We understand that you may have complaints towards an admin. This must be directed via our forums or teamspeak. We prefer to answer via TS so that we can resolve the situation as quickly as possible.
4.3 Abusing the !r function is a kickable offense.
#HGG's Ghetto! (North America)
Player feedback for all Project Reality: Battlefield 2 servers.
Return to “PR:BF2 Server Feedback”
Jump to
- Announcements
- ↳ Announcements & Highlights
- ↳ Development Blogs
- ↳ Changelogs
- ↳ Events
- PR:BF2 Mod Forums
- ↳ PR:BF2 General Discussion
- ↳ PR:BF2 Suggestions
- ↳ PR:BF2 Feedback
- ↳ Maps
- ↳ Vehicles
- ↳ Infantry
- ↳ Coop & Singleplayer
- ↳ PR:BF2 Bugs
- ↳ PR:BF2 Tales from the Front
- ↳ Tactics & Strategies
- ↳ Map Strategies
- ↳ Infantry Tactics
- ↳ Squad Leader Tactics
- ↳ Commander Tactics
- ↳ Armor Tactics
- ↳ Aircraft Tactics
- ↳ PR:BF2 Clans
- ↳ Clan Wars
- ↳ Clan Recruitment
- ↳ PR:BF2 Community Factions
- ↳ Mapping
- ↳ Objects
- ↳ Coding
- ↳ Modelling&Animations
- ↳ Texturing
- ↳ Chilean Forces 1978
- ↳ Indonesian Forces
- ↳ Faction Archives
- ↳ African Resistance Fighters
- ↳ Australian Forces
- ↳ Dutch Forces
- ↳ Finnish Defense Forces
- ↳ New Zealand Def. Force
- ↳ Norwegian Forces
- ↳ Polish Forces
- ↳ Czech Forces
- ↳ Brazilian/FARC Forces
- ↳ PR:WWII General Discussion
- ↳ PR:WWII Suggestions
- ↳ PR:Falklands General Discussion
- ↳ PR:F Suggestions
- ↳ PR:Vietnam General Discussion
- ↳ PR:V Suggestions
- ↳ PR:BF2 Community Modding
- ↳ Modding Tutorials
- ↳ Community Maps
- ↳ Community Tasks
- PR Server Forums
- ↳ PR:BF2 Server Feedback
- Project Reality Support
- ↳ PR:BF2 Support
- ↳ General Technical Support
- ↳ Hardware
- ↳ Software
- ↳ OverClocking & Networking
- ↳ PR Dev Blogs
- ↳ Official PR Tournament News
- ↳ Tournament Website
- ↳ PR Dev Journal Archives
- ↳ 2009
- ↳ 2008
- ↳ 2007
