Introduction: Why is CSS Content Necessary for DarkRP?
Counter-Strike: Source (CSS) content is essential for many Garry's Mod servers, especially DarkRP, because it includes various textures, models, and assets that are not part of the base Garry's Mod game. Without these files, you may experience missing textures (often seen as pink and black checkerboards) or "ERROR" models, which can significantly affect your gameplay experience.

Legal Notice:
Downloading CSS content from third-party sites like GMOD Content is technically only legal if you own a licensed copy of Counter-Strike: Source. If you do not own the game, consider purchasing it on Steam, which will automatically provide you with all the necessary content in a legal and straightforward manner.

Step-by-Step Guide to Installing CSS Content

Method 1: Downloading CSS Content from a Third-Party Site

1. Download the CSS Content:
   • Go to the GMOD Content Website
   • Click on the CSS (Counter-Strike: Source) Content download link.
   • Save the ZIP file to your computer.
2. Extract the CSS Content Files:
   • Once the download is complete, locate the downloaded ZIP file on your computer.
   • Right-click on the ZIP file and choose Extract All or use your preferred extraction tool (such as WinRAR or 7-Zip).
   • Extract the files to a new folder named "cstrike.".
   • You can leave it named css-content-gmodcontent just ensure inside of that it contains a folder named materials
3. Locate Your Garry's Mod Addons Folder:
   • Open the Steam client and go to your library.
   • Right-click on Garry's Mod and select Properties.
   • Click on the Installed Files tab and select Browse Local Files.
   • Navigate to the Garry mod folder, then open the addons folder.
4. Install the CSS content:
   • Open the CSS Content folder you extracted earlier.
   • Copy the entire folder (usually named cstrike or css-content-gmodcontent).
   • Paste the folder into the addons folder of your Garry's Mod directory.
   • Ensure inside of the folder it contains
     • materials
     • models
     • particles
     • sound
     • May also contain a txt file saying downloaded-from-gmodcontent.com
5. Verify Installation:
   • Launch Garry's Mod.
   • Join a server or create a local game.
   • Look for any missing textures or "ERROR" models. If none are visible, the installation is successful.

Method 2: Purchasing Counter-Strike: Source on Steam

1. Purchase and install Counter-Strike: Source from Steam.
2. Launch Garry's Mod.
3. Go to Games at the bottom and make sure CSS is checked.
4. This method ensures you have all the necessary files without needing to download anything manually.

Troubleshooting and Verification

How to Verify if CSS Content is Working Correctly:

• Join JustifiedRP to check if some models are still errors that are css
• Ensure there are no pink/black textures or "ERROR" models.
• Check if specific textures like wall decals, player models, and props (like dumpsters, crates, and signs) are displaying correctly.

Common Issues and Solutions:

• Textures Still Missing:
  Double-check that the cstrike folder is inside the correct addons directory. Ensure no extra folders are nested incorrectly (e.g., addons/cstrike).
• Content Not Appearing After Installation:
  Restart Garry's Mod after installing the content. You may also need to verify the integrity of Garry's Mod files via Steam.
• Conflicts with Other Addons:
  Some addons may override CSS content. Disable all other addons and re-enable them one by one to identify any conflicts.

Keeping the CSS Content Updated:

• Periodically check for updates on GMOD Content or the Steam store to ensure your CSS content is up-to-date.
• Re-download and replace outdated files to maintain compatibility with server updates.

Uninstalling CSS Content

1. Navigate to your Garry's Mod addons folder.
2. Delete the cstrike folder to remove the CSS content.
3. Restart Garry's Mod to apply changes.

CSS Content and Other Addons

• CSS content generally does not conflict with other addons unless they specifically overwrite the same textures or models. Always check server requirements for any specific mods or content packs needed.

Glossary of Terms

• CSS: Counter-Strike: Source, a game required for certain textures and models in Garry's Mod.
• Addon: Additional content that can be added to Garry's Mod, like mods, models, and textures.
• Texture: The 2D images applied to 3D models to give them detail.
• Model: A 3D object in the game, like a character or prop.
• "ERROR" Models: Placeholder models that appear when Garry's Mod cannot find the correct model file.
• Pink and Black Checkers: The default missing texture indicator in Garry's Mod.

Additional Resources

• Purchase Counter-Strike Source
• GMOD Content Website

---

---

---

---

---

---

Title

---

• You are responsible for keeping updated on our rules upon joining our server.
• Please read the rules thoroughly and completely.
• If there are any problems regarding these rules, please make a thread in the Suggestions tab.

---

General Rules
Communication Rules
Prop Rules
Entity Rules
Basing Rules
Rule Specific Rules
Government Rules

---

Definitions

• RDM (Random Death Match): Killing players without a valid in-game reason is strictly prohibited. All combat must have a legitimate purpose for roleplay.
• RDA (Random Arrest): Law enforcement characters must have a valid reason to arrest other players. Arbitrary arrests are not allowed.
• NLR (New Life Rule): After your character dies, you must forget all information related to that life. Do not seek revenge or return to the scene of your death for at least 10 minutes.
• FailRP (Failed Roleplaying): Players must act consistently with their chosen role and the game's setting. Unrealistic or out-of-character behaviour that breaks immersion is not permitted.
• FearRP: Players must react realistically to threatening situations. For example, if someone points a gun at you, you should comply or seek cover rather than attacking or ignoring the threat.
• Metagaming: Using out-of-character knowledge to gain an in-game advantage is forbidden. This includes sharing information your character wouldn't realistically know, such as keypad codes or base layouts.

---

---

1. Roleplay Integrity
   1. There is no random death match (RDM) or random arrest (RDA).
   2. Adhere to the New Life Rule (NLR): Forget previous life details after death.
   3. Avoid FailRP: Always act according to your chosen role.
2. Respectful Conduct
   1. Treat all players with respect, regardless of their role or status.
   2. No discrimination, harassment, or excessive profanity
   3. Resolve conflicts maturely; seek staff assistance if needed.
3. Server Loyalty
   1. No advertising on other servers or communities
   2. Please report bugs and exploits to staff instead of abusing them.
   3. Provide constructive feedback to improve the server.
4. Fair Play
   1. No cheating, hacking, or using exploits
   2. We prohibit AFK farming or occupying job slots while inactive.
   3. Do not encourage or bait others into breaking rules.
5. Immersive Gameplay
   1. Use realistic and appropriate roleplay names (minimum 3 English characters).
   2. Maintain character during interactions; avoid breaking immersion.
   3. Participate in and respect ongoing roleplay scenarios.
6. Economic Integrity
   1. No scamming other players
   2. You cannot exchange in-game currency and items for real-world value.
   3. Avoid excessive wealth hoarding that disrupts the server economy.
7. Job Responsibilities
   1. Fulfill the responsibilities of your chosen job.
   2. There should be no instances of false demotions or abuse of job-specific powers.
   3. Respect the hierarchy and chain of command within factions.
8. Environmental Respect
   1. Once you've finished using props and entities, clean them up.
   2. Avoid unnecessary prop spam or entity creation.
   3. Respect designated building areas and others' properties.

---

---

1. Discrimination can occur due to factors such as but not limited to race, ethnicity, nationality, religion, gender, sexual orientation, age, or disability. The use of objectionable language, derogatory terms, or slurs directed at protected groups
   Endorsing or promoting discriminatory ideologies
   Harassment or abuse based on personal characteristics
   1. Enforcement:
      Violations will result in immediate action, which could include warnings or permanent suspensions.
      We will consider context, but intent does not excuse harmful behavior.
      The staff is responsible for the final interpretation and enforcement of this rule.
   2. Conduct during gameplay:
      Refrain from engaging in contentious religious or political discussions.
      Concentrate on positive community interactions and gameplay.
   3. Reporting:
      Staff members encourage players to report incidents. They may either use the specified reporting system or contact a staff member directly.
      False reports submitted in bad faith may result in penalties.
   4. Community Responsibility:
      We anticipate that players will contribute to a welcoming environment.
      When you observe discriminatory behavior, speak out.
      Assist your fellow participants, who may be victims of harassment.
2. We will not accept any form of sexual harassment or misbehaviour. This includes unsolicited sexual approaches, obscene language, jokes, and other behaviour that creates a threatening or hostile atmosphere.
   1. Avoid jokes or comments about rape, incest, or other sensitive topics.
   2. Report any incidences of sexual harassment to the management team right away. Making allegations public might jeopardise the inquiry process.
3. Justified uses English as its primary language for advertisements. You can use any language in other contexts, as long as it follows all other communication standards.
4. We strictly prohibit the use of spam in OOCs, ads, @chat, local chat, and voice chat.
5. Advertising of any kind is strictly prohibited within our community. This includes promoting other platforms, products, or services without permission.
6. Voice Chat Etiquette
   1. To reduce background noise, use push-to-talk whenever possible.
   2. Keep your voice at a suitable volume.
   3. You should not use voice changers and soundboards without specific consent.
7. Roleplay Communication
   1. When using in-character (IC) chat and voice, keep your character consistent.
   2. As per the server rules, use /advert for significant roleplay announcements.
8. Staff Respect
   1. Respect staff choices and communicate courteously with them. If you disagree with a judgement, appeal through the appropriate means.
9. Personal information protection:
   Do not share personal information about yourself or others through any public communication channels on the server. This includes, but is not limited to:
   1. • Full names
      • Addresses
      • Phone numbers
      • Email addresses
      • Social security numbers
      • IP addresses
      • Financial information
      • social media accounts
      • Details about a school or workplace
   2. Any violation of this policy will result in immediate disciplinary action, up to and including permanent removal from the server. It is important to prioritise the safety and privacy of all individuals in our community.
   3. If you believe someone is sharing personal information in violation of this policy, please report it to a moderator or administrator immediately.
   4. We take the protection of personal information seriously and appreciate your cooperation in maintaining a safe and respectful environment for all users.
   5. Doxxing is strictly prohibited.
      We have a zero-tolerance policy for doxxing. Doxxing is the act of revealing or threatening to reveal private or sensitive information about an individual without their consent. We strictly prohibit this, and we will face immediate and severe consequences.
   6. Protecting yourself:
      Be cautious about the information you share, even in private messages.
      Do not click on unknown links or download files from untrusted sources.
      Use strong, unique passwords for your accounts. Regularly update your passwords and enable two-factor authentication for added security.

---

---

1. No Prop Spamming: Avoid rapidly spawning multiple props or an excessive number of props that could cause server instability or lag.
2. No Prop Blocking: You cannot use props to block or obstruct critical areas like spawn points, entrances, exits, or NPCs. All entrances and pathways must remain accessible to all players.
3. We strictly prohibit using props to climb walls or structures, access otherwise inaccessible areas, or surf.
4. No Prop Killing: Do not use props to intentionally harm or kill other players. This includes launching props at high speeds or dropping them from heights.
5. No Prop Minging: Do not use props to disrupt, antagonise, or annoy other players' roleplay experiences. This includes placing props in front of cameras, using props with inappropriate textures or models, or repeatedly using props that create disruptive sounds.
6. No Floating Bases or Structures: All props used in building must have realistic support and cannot float without visible support. We do not allow structures that defy the laws of gravity or appear unrealistic.
7. Limit Prop Size: Avoid spawning excessively large props, which can cause lag or obstruction. Use props that are appropriately sized for their intended purpose.
8. Clear Unused Props: Remove any props that you have spawned but are no longer using to keep the server clean and reduce lag.
9. No Prop Usage in Combat: During active combat or raids, do not use props as weapons, shields, or barricades. Props should not provide an unfair advantage in combat.
10. Admin Discretion: All prop usage is subject to administrative discretion. Admins may remove or ask players to remove any props deemed harmful, inappropriate, or causing lag.

---

---

1. No Entity Spamming: Do not spawn multiple entities rapidly or create an excessive number of entities that may cause server lag or instability.
2. No entity blocking: entities must not be placed to block or obstruct key areas, such as spawn points, entrances, exits, or NPCs. Keep all pathways and important locations accessible.
3. No Dangerous Entities Near Spawn: Do not place explosive or dangerous entities, such as C4, mines, or gas canisters, near spawn points, public areas, or other players' bases.
4. No Entity Abuse: Do not use entities to gain unfair advantages, such as hiding printers in walls, glitching entities into inaccessible areas, or exploiting bugs to duplicate entities.
5. No Interference with Other Players' Entities: Do not steal, destroy, or tamper with entities owned by other players unless your role (e.g., thief, raider) explicitly allows it, and only in the context of roleplay.
6. Remove Unused Entities: Clear up any entities you have spawned that are no longer in use to help maintain server performance and prevent clutter.
7. Limit Use of Dangerous Entities: Keep the use of explosive or otherwise dangerous entities reasonable. Do not place multiple explosive items in one area, as it can create unnecessary risks or cause lag.
8. Entity Placement in Bases: Entities such as printers or other valuable items must be placed in a way that makes them reasonably accessible during raids. Do not hide entities in walls, ceilings, or use glitchy spots to prevent other players from finding them.
9. Staff Discretion: All entity usage is subject to staff discretion. Staff members may remove or ask players to remove any entities deemed harmful, inappropriate, or causing lag.

---

---

1. Design Rules
   1. (Disallowed) Crouch bases: bases that require players to crouch or crawl through entryways or paths to progress or raid. This includes any part of a base where crouching is mandatory to pass or reach valuables.
   2. (Disallowed) Jump Bases: bases that require players to jump or perform any jumping actions to enter or navigate. This includes designs where jumping is necessary to pass over obstacles, reach certain areas, or progress further into the base.
   3. (Disallowed) Timed bases arebases designed to intentionally delay raiders by requiring excessive time to navigate, even without keypad doors or obstacles. This includes any base layout that forces raiders to spend an unreasonable amount of time walking, moving through excessively long corridors, or performing repetitive actions solely to waste time or create an unfair advantage.
      1. A base must take less than 15 seconds to navigate, excluding keypads.
   4. (Disallowed) Movement Restriction Bases: Bases that force players to perform specific, non-standard movements (e.g., crouching, jumping, sliding, or dodging) to enter or raid. Any base requiring unconventional movement that restricts raiders' ability to proceed normally falls under this category.
   5. (Disallowed) Unfair Visibility Bases: Bases designed in a way that prevents either the raider or defender from clearly seeing each other during combat. This includes any use of props, textures, lighting, or designs that create unfair visibility, such as one-way windows, hidden shooting spots, tinted or obstructed viewports, and any setups that obscure one party's view while leaving the other party fully visible. Both the raider and defender must have an equal opportunity to see and engage each other during raids.
   6. (Disallowed) Maze Bases: bases with overly complex or confusing layouts, featuring more than six 90-degree turns or intricate pathways designed to delay or confuse raiders. This includes any layout that forces raiders to navigate a maze-like structure to reach valuables.
   7. (Disallowed) Blackout bases: bases using dark textures, props, or lighting setups that make it extremely difficult or impossible for raiders to see. This includes any base design that intentionally reduces visibility for raiders, such as completely blacked-out corridors or rooms.
   8. (Disallowed) Invisible bases: bases that use invisible props or textures to obstruct or deceive raiders. This includes walls, barriers, or pathways that are made invisible, making it unclear where raiders can or cannot go.
   9. (Disallowed) Water bases: bases that include water elements or segments to create an advantage against raiders. This includes designs where water is used to slow raider movement, impair vision, or hide entities.
   10. (Disallowed) Pixel-Perfect Bases: Bases that require raiders to perform precise and exact movements, such as specific jumps or squeezing through tight spaces. Any design demanding a high level of accuracy to navigate or proceed is considered a pixel-perfect base.
   11. (Disallowed) Trap bases: bases designed to trap or kill players without providing a fair chance to escape or engage in combat. This includes pits, hidden traps, or areas with one-way entry that leads to automatic death or damage.
   12. (Disallowed) Kill box bases: bases where raiders are funnelled into a confined space where they can be easily killed without a fair chance to fight back. Typically, these bases have only one way in and out, limiting the raider's ability to maneuver.
   13. (Disallowed) Angled Shooting Blinds: Bases that use angled props or designs to give defenders an unfair advantage in shooting while limiting the visibility or aim of raiders. This includes setups where defenders can see and shoot raiders without being seen themselves.
   14. (Disallowed) No-Collided Props in Bases: bases that use props set to "no-collide" to create unfair advantages. This includes using props that raiders can walk through but cannot see through or props that block movement or vision without appearing solid.
   15. (Disallowed) Invisible Shooting Spots: bases with shooting windows or positions that are invisible or very hard to spot, making it difficult for raiders to see where shots are coming from. This includes using invisible or translucent props in shooting areas.
   16. (Disallowed) Fall Damage Bases: Bases designed in a way that forces raiders to take fall damage while attempting to enter or navigate the base. Any design that intentionally incorporates vertical drops or jumps that cause harm is considered a fall damage base.
   17. (Disallowed) Prop Climbing Bases: Bases that require raiders to stack or use props to climb over barriers or reach certain areas. This includes any base where accessing valuables necessitates climbing via props or unconventional means.
   18. (Disallowed) One-Way Viewing Windows: Bases with windows or openings that allow defenders to see and shoot raiders without being visible themselves. This includes designs that use props or positioning to create one-way visibility.
   19. (Disallowed) Randomized Pathway Bases: bases that have multiple paths, with only one leading to the valuables, forcing raiders to guess or use trial and error. This includes setups with false doors, misleading signs, or complex branching paths.
   20. (Disallowed) False/Decoy Room Bases: bases with rooms that appear to contain valuables or objectives but are actually empty or serve no purpose other than to mislead raiders. This includes fake vaults or rooms with decoy entities.
   21. (Disallowed) floating bases: bases that float in mid-air or are supported by props that defy gravity. Any base without realistic structural support that seems to hover or float is considered a floating base.
   22. (Disallowed) Blocked Viewport Bases: Bases that use props to block viewports or create artificial obstructions, like fog, to impair raiders' visibility. This includes designs that intentionally block lines of sight to create an advantage.
   23. (Disallowed) Overlapping Prop Bases: Bases using overlapping or stacked props to make walls or surfaces impenetrable or extremely difficult to shoot through. This includes exploiting prop placement to create unfair defences.
   24. (Disallowed) Fake Keypad or Button Bases: Bases that include fake keypads, buttons, or switches meant to mislead or confuse raiders. This includes setups where raiders are tricked into interacting with decoys that serve no functional purpose.
   25. (Disallowed) Drop-Box Bases: Bases that force players to drop down into confined or hard-to-escape areas, limiting their mobility or creating a one-way path. This includes designs with drops that leave raiders vulnerable.
   26. (Disallowed) Slide Bases: Bases that force players to slide down slopes or ramps, restricting movement or forcing them into disadvantageous positions. This includes any use of physics to funnel raiders into specific areas.
   27. (Disallowed) Dark Room Bases: Bases with rooms intentionally kept in darkness or low visibility, preventing raiders from seeing properly or navigating effectively. This includes any area where lighting is manipulated to impair vision.
   28. (Disallowed) One-Way Prop Bases: bases that use props, allowing defenders to see or shoot through them, but raiders cannot see or shoot back. This includes props that are transparent on one side but opaque on the other.
   29. (Disallowed) Peekaboo Bases: Bases where defenders can quickly hide and reappear to shoot at raiders without giving them a fair chance to retaliate. This includes designs with rapid cover elements or hiding spots.
   30. (Disallowed) Render Distance Exploit Bases: Bases that take advantage of map render distances, making it hard or impossible for raiders to see defenders from specific positions or ranges.
   31. (Disallowed) Head Glitch Bases: Bases where only a small part of the defender's head is visible, giving them an unfair advantage by making it extremely hard for raiders to hit. This includes props positioned to cover most of the defender's body.
   32. (Disallowed) Prop Tunnel Bases: Bases with narrow tunnels or tight spaces designed to limit raider movement severely. This includes setups where raiders are forced into narrow passages, making them easy targets.
   33. (Disallowed) Hide and Shoot Bases: Bases designed so that defenders can hide entirely while still having the ability to shoot raiders. This includes designs that allow defenders to shoot from positions raiders cannot see or access.
   34. (Disallowed) Zigzag Bases: Bases with excessive zigzag pathways designed to slow raiders down or confuse them. This includes paths with constant direction changes that create unnecessary delays.
   35. (Disallowed) Rapid Door Close Bases: Bases with fading doors that close too quickly, preventing fair access for raiders. This includes any door setup where the raider has minimal time to proceed.
   36. (Disallowed) Double Door Bases: Bases that use multiple layers of closely spaced doors to make raiding unnecessarily challenging. This includes doors that serve no purpose other than to delay raiders.
   37. (Disallowed) Prop Block Bases: Bases that use props to intentionally block access to certain areas or routes, making them difficult or impossible to raid. This includes props placed in a way that hinders movement or progress.
   38. (Disallowed) Elevated Platform Bases: Bases that require raiders to climb elevated platforms or props, giving defenders a height advantage or making raiders easy targets.
   39. (Disallowed) Toggle-Only Access Bases: Bases that rely exclusively on toggle buttons or other mechanisms raiders cannot reasonably counter. This includes bases where raiders have no choice but to guess or trial-and-error to proceed.
   40. (Disallowed) Wall Bang Bases: Bases that use thin props or materials to allow defenders to shoot through walls or barriers without exposing themselves. This includes props that appear solid but allow shots to pass through.
   41. (Disallowed) Deceptive Entryway Bases: bases with multiple fake entrances or misleading signs designed to confuse raiders about the correct entry point. This includes any design that misleads raiders about how to access the base.
   42. (Disallowed) Timed Trap Bases: Bases that have timed traps or mechanisms meant to close off pathways, cause damage, or trap raiders without giving them a fair chance to proceed.
   43. (Disallowed) Obstruction Prop Bases: bases that use props to create artificial obstacles, such as debris or fake barriers, that block raiders' vision or movement unfairly.
   44. (Disallowed) Backdoor bases: bases with hidden or unintended entry points that are difficult or impossible for raiders to find. This includes exploiting map features or unintended access points.
   45. (Disallowed) Forced Drop Bases: bases that force raiders to drop into confined spaces without a way to escape or defend themselves effectively. This includes designs that trap raiders upon entry.
   46. (Disallowed) Window Peek Bases: Bases with windows designed for defenders to peek and shoot without being visible or targetable by raiders. This includes designs that use narrow slits or hidden viewports.
   47. (Disallowed) Juke Door Bases: Bases that include false doors or paths solely to waste time or mislead raiders. This includes designs where doors lead to dead ends or irrelevant areas.
   48. (Disallowed) Forced Damage Bases: Bases designed in a way that forces raiders to take damage without any reasonable means of avoiding it. This includes traps, fall damage zones, or environmental hazards intentionally placed in the base's path.
   49. (Disallowed) No-Retreat Bases: bases that prevent raiders from retreating or leaving once they enter. This includes designs with one-way paths that trap raiders inside.
2. Location Rules
   1. Bases must not block or restrict access to any unique NPCs or entities that are important for gameplay or specific jobs.
   2. Bases should not prevent players from traveling freely around the map, including designs that force a player into entrapment.
   3. A base location is only allowed to occupy one part of the map, which is defined as one building or one rooftop area.
   4. Building in or above restricted zones, such as the fountain area or on sidewalks, is not permitted.
   5. To claim ownership of a base location, you must own all doors that encompass the building. If there are no doors, it is first-come, first-served; a "Building" sign is recommended to indicate the area is claimed.
   6. Jobs with specific door ownership (like government jobs, bank jobs, or sewer dwellers) must be based in their designated areas as specified in their job descriptions.
   7. Only one base is allowed per party or group.
   8. Using props or entities in tunnels or other narrow pathways is not allowed.
3. Entryway Rules
   1. A base can have a maximum of four keypad-controlled doors in the entry path, and each door must open once for entry and exit.
   2. Keypad doors must have a minimum hold time of five seconds with no initial delay.
   3. There must be a reasonable space between keypad doors, and the distance should not exceed the size of specific props, ensuring raiders have a fair chance.
   4. Using keyboards, buttons, or lights to confuse or mislead raiders is not allowed.
   5. Maze(zig-zag)-like base designs with more than six 90-degree turns are prohibited.
   6. Base designs should not require raiders to crouch, crawl, or otherwise exit the standing state to enter.
   7. Blacked-out, heavily texturized, or invisible base designs that hinder a raider's ability to navigate are not allowed.
   8. Bases that use water segments to gain an advantage against raiders are prohibited.
   9. Designs that require raiders to slide, drop, or perform pixel-perfect movements are not allowed.
   10. Keeping doors locked in the open/closed state to obstruct raiders is not permitted.
4. Shooting Window Rules
   1. Bases must allow both parties (defenders and raiders) to see and shoot at each other during a raid; using props that obstruct visibility or create unfair advantages is not allowed.
   2. Tinted shooting blinds or any method that obscures a raider's aim is prohibited.
   3. Props used for shooting blinds must meet minimum size requirements, and all buttons used for shooting blinds must be bound to a single key and set to toggle mode.
   4. Bases should not use angled shooting blinds or exploit no-collided props.
   5. Buttons used for opening shooting blinds or fading doors should be bound to a single key and configured to toggle mode.
5. Keypad Rules
   1. All keypads must be placed in visible and accessible locations and within a reasonable distance from their corresponding prop.
   2. Keypads should have a minimum hold time of five seconds with no initial delay to ensure fair raiding opportunities.
   3. You may only have a maximum of 4 Keypad Doors
6. Fading Door & Button Rules
   1. Fading doors must be linked to a button and may not be controlled by a key bind.
   2. Fading doors must not be stacked closely together in a way that makes it difficult or impossible for raiders to breach.
   3. Fading doors may not be used as a hidden way out of your base or into the base.
7. Sign Rules
   1. Only three types of signs are allowed: KOS/AOS Signs (indicating kill/arrest on sight zones), Building Signs (indicating that the base is still under construction), and RP Build Signs (indicating that the base is for roleplay purposes only and contains no raidables).
   2. Signs must be easily visible, placed at the front entrance of the base, and be of a sufficient size (e.g., size 40 or above).
   3. KOS/AOS and other signs must be specific in their wording and not use vague or banned phrases (e.g., "Once KOS Always KOS" or "KOS If Annoying").
   4. Signs must not blend into the background and should be clearly readable to avoid confusion.
   5. If using an RP Build sign, the base must not contain any raidable entities, and the players must adhere to the specific rules for RP builds.
   6. You cannot stack different types of signs on the same base; only one type of sign is allowed.

---

---

Raiding Rules

1. Raids must be declared clearly in the chat or using the integrated G menu before commencing. Failure to announce a raid is considered RDM.
2. You may raid the same base only once every 20 minutes
3. You must leave the base immediately after completing the raid. Remaining inside a raided base for longer than necessary is considered camping.
4. Only jobs designated for raiding (e.g., thieves, gangsters) are allowed to conduct raids.
5. During a raid, do not use exploits, glitches, or prop abuse to gain entry or an advantage.
6. You must not raid bases with "RP Build" signs, as they are designated for roleplay purposes only.
7. You cannot raid the same base multiple times in a row with different groups or teams; alternating raids with different groups is considered raiding abuse.
8. Raiders are allowed to use explosives, such as grenades or breaching charges, but their use is limited to a maximum of 8 rounds per raid.
   1. This restriction pertains to the entire team that is conducting the raid on the base.
9. Raiders must ensure that the use of explosives does not cause excessive damage to the environment or disrupt gameplay for other players outside the raided base.

Defending Rules

1. Defenders must stay within their base or immediate vicinity while defending from a raid. Chasing raiders beyond reasonable distance is not allowed.
2. Defenders may not rebuild, modify, or add new props to their base during an active raid. All defences must remain static.
3. Defenders may only shoot raiders once they have entered the base or its immediate surroundings. Shooting raiders outside this area is considered RDM.
4. Defenders may not use any third-party tools, exploits, or cheats to gain an unfair advantage during defence.
5. Defenders must adhere to visibility rules, ensuring both raiders and defenders can see each other clearly during a raid.
6. Defenders are not allowed to use any explosives, including grenades, C4, or any other explosive devices, during a raid. This restriction is in place to ensure that raiders have a fair chance to breach and engage in combat without being overwhelmed by explosives.

New Life Rule (NLR)

1. The New Life Rule (NLR) applies whenever you die. You must wait 5 minutes before returning to the location of your death.
2. During the NLR cooldown, you must forget all information about your previous life, including who killed you, what happened, or any actions taken by others.
3. NLR applies to all deaths, whether during raids, combat, or accidents. Breaking NLR by returning early or acting on knowledge from a past life is prohibited.
4. Raiding or attacking the same location immediately after dying and respawning is not allowed; you must wait for the NLR cooldown.

Countering Rules

1. You may only counter actions (like raids or muggings) if your role or job specifically allows it (e.g., police, vigilante, security jobs).
2. Countering must be announced in the chat to avoid confusion and accidental RDM.
3. Countering must be limited to actions in your immediate vicinity. You cannot travel across the map to counter an action unless it involves your base or an allied base.
4. Using countering as an excuse for random killing or engaging in combat without a legitimate reason is disallowed.

Warning Rules

1. All warnings must be issued using the integrated G menu to ensure clear communication.
2. You must give at least three verbal or text warnings before taking any lethal action against a player. All warnings should be reasonable and allow the player time to comply.
3. Warnings cannot be used in spawn areas, public spaces, or near NPCs unless there is a legitimate roleplay reason.
4. You cannot use warnings as a reason to kill players repeatedly or without justification. Abuse of warnings for random killing or harassment is prohibited.
5. Players must be given a reasonable amount of time to respond to a warning. Immediate action following a warning is considered RDM.

Mugging Rules

1. All mugging must be initiated using the integrated G menu. You must declare your intent to mug someone clearly.
2. The maximum amount you can demand during a mugging is £50,000. Any demands exceeding this limit are disallowed.
3. Players being mugged must be given at least 10 seconds to comply with your demands. Killing a player before this time frame is considered RDM (Random Death Match).
4. You may not mug the same player within a 15-minute time frame. Doing so is considered harassment.

Hitmen Rules

1. Hitmen must follow the rules of engagement and not kill anyone other than the assigned target. Killing others without reason is considered RDM.
2. A hitman cannot accept multiple hits on the same person consecutively.
3. Hitmen are not allowed to accept hits on players currently in spawn or designated safe zones.
4. Hitmen must use reasonable tactics to approach targets. Using props, glitches, or exploits to gain an advantage is not allowed.
5. Hitmen may not collaborate with other players or use other players to achieve a hit. Hits must be completed solo.

Kidnapping Rules

1. All kidnappings must be initiated using the integrated G menu, with clear communication of your intent to kidnap.
2. Kidnapping must involve a clear demand or ransom, not exceeding £50,000. (Government = £100,000)
3. You may not kidnap the same player within 30 minutes.
4. Kidnapping must not be conducted in high-traffic public areas, such as spawn points or in front of NPCs.
5. The maximum duration for holding a kidnapped player is 5 minutes. Holding players longer is disallowed.
6. You must provide the kidnapped player with an opportunity to comply with your demands; immediate harm or killing is disallowed without giving them a chance.
7. Releasing the kidnapped player is mandatory once the kidnapping is over; you may not kill this player as a way to let them go.

---

---

Government Rules

1. All government roles must adhere strictly to their job descriptions and avoid actions that do not fit their role (e.g., random killing, random arrests, non-roleplay behavior).
2. Corruption, including accepting bribes or collaborating with criminals, is strictly prohibited.
3. Government officials may only use authorized and government-issued weapons, tools, and equipment.
4. Basing is restricted to designated government areas (e.g., police department, bank).
5. Public safety and security must always take precedence over personal interests or gains.
6. All official actions, including arrests, raids, and law enforcement, must be justified
7. Effective coordination is required during emergencies (e.g., bank raids, kidnappings, major threats) to ensure a unified response.
8. All government employees must adhere to server rules at all times and respect staff authority.

Police Department Regulations

1. Officers must protect citizens, enforce laws, and maintain order without engaging in Random Death Match (RDM) or conducting False Arrests.
2. The use of non-lethal force (e.g., batons, tasers) is prioritized; lethal force is reserved only for situations where it is justified (e.g., self-defense, armed threats).
3. Arrests require valid reasons (such as visible crimes or KOS warrants) and must be conducted using the integrated warrant system.
4. Property raids require a valid search warrant approved by the Mayor and should be executed professionally.

Mayoral Responsibilities

1. The Mayor must act in the city's best interest, creating laws that are fair and promote public safety.
2. Direct participation in combat or raids is prohibited; the mayor should remain in designated safe areas, such as the Police Department.
3. All laws must be reasonable, not conflict with server rules, and respect player rights.
4. The Mayor cannot create laws that personally benefit themselves or unfairly target specific players or groups.
5. Kill on Sight (KOS) or Arrest on Sight (AOS) orders must be justified, fair, and communicated clearly to the police force and citizens.
6. The mayor is responsible for approving police raids and warrants and must have valid reasons for doing so.

Bank Manager Duties

1. The Bank Manager is responsible for overseeing bank security and the protection of assets.
2. The bank manager must collaborate with the police to establish defences for the bank.
3. Any hired security personnel must fully comply with server rules and the Bank Manager's directives.

Disallowed Laws

• Blanket bans on all weapons, including self-defence tools like pistols.
• Laws that only allow certain players or groups to carry weapons.
• Laws that directly benefit the Mayor or their friends.
• Laws that unfairly target specific players or groups.
• Laws that allow KOS or AOS without valid reasons or broad categories.
• Laws that make all crimes punishable by death without due process.
• Excessively high taxes or fines that unfairly burden players.
• Fines or taxes that are arbitrary or lack clear justification.
• Laws targeting specific groups or roles unfairly.
• Laws that promote discrimination based on player choices.
• Laws that conflict with existing server rules or are too vague to be enforced fairly.
• Laws that contradict the server's core gameplay mechanics or established player freedoms.
• Laws that punish legal roleplay actions.
• Laws that ban basic player interactions like trading, communication, or forming groups.
• Bit miners cannot be illegal

---

Username: iyda

Your In-Game Name: iyda

Link to your Public Steam Profile: http://steamcommunity.com/profiles/76561197960330446

Your Age: 20

Your Discord Tag: iyda

Is your discord name the same as your In-Game Name? Yes

What is your time zone? GMT

Have you ever been warned or banned on any Justified server? ewfefwewfewf

How much playtime do you have on the server? 3months 20d 12 minutes 10seconds

Have you read up on our rules fully? No

Include any other information about yourself that you'd like the community and the management team to know about you. efwewfwefwefewf

Do you have a microphone and use it on a consistent basis? Yes

Do you have any prior experience staffing on other Garry's Mod servers within the past 2 years? ewfewfwefwefewf

Have you previously staffed on Justified? No

Why do you want to be a part of the Justified Staff Team? ewfewfwefewf

Why should you be accepted onto the Justified Staff Team? fewewfewf

What qualities do you possess that would make you an effective staff member? wefwef

Have you ever had to handle a difficult situation as a staff member on another server? If so, how did you handle it? efwweffewwef

How would you handle a situation where a player is repeatedly breaking the rules despite multiple warnings and kicks? ewffew

A player approaches you with an issue they are having with another player on the server. How would you handle this situation? efwwefwef

How would you deal with a player who is constantly harassing or disrespecting other players on the server? ewfwef

Have you ever had to enforce disciplinary action against a friend or someone you know personally? If so, how did you handle the situation? ewfewfewf

What is your opinion on the use of admin powers for personal gain or advantage? efw

Have you ever been accused of abusing admin powers on any other server? If so, how did you handle the situation? wefefwwefewf

What steps would you take if a player accuses you or another staff member of abusing admin powers? ewfewfewf

Do you have any experience with server administration or programming? If so, please describe. ewfewf

How do you handle stress and pressure in a fast-paced and potentially chaotic environment like a Garry's Mod server? ewfewf

How much time are you willing to commit to staffing on the Justified server? efewfwef

What is your opinion on the role of staff members in maintaining a healthy and enjoyable server community? ewfwefw

Can you describe your experience working with other people in a team-oriented environment? wefewfefw

What are some of the biggest challenges you foresee in being a staff member on the Justified server, and how do you plan to overcome them? ewfwef

You receive a report from a player who claims that another player is using cheats. What steps would you take to investigate the report? fefwewfwef

A player approaches you and claims that another player is harassing them. What steps would you take to address the situation? wefew

A player is causing trouble and breaking server rules, but they have a history of being a valuable member of the community. How would you handle the situation? ewfewf

You receive a report that a player is exploiting a glitch to gain an unfair advantage. How would you investigate the report and address the situation? wefwef

Two players are having an argument in chat and it's starting to become heated. What steps would you take to diffuse the situation? ewfewf

You notice a player repeatedly breaking minor server rules (e.g. prop blocking), but they stop when you approach them. How would you handle the situation? wefwefwef

You receive a report that a player is using racial slurs in chat. How would you handle the situation? efwewfewf

A player approaches you and asks for an item or a favor that they are not entitled to as part of their job or role. How would you handle the situation? efwewf

You notice that a staff member is not enforcing the rules consistently. How would you address the situation? eefwefw

A group of players is causing trouble and disrupting the gameplay experience for others. How would you handle the situation? fwef