
THE RULEBOOK
This is the complete, current rulebook, the same one every Husk acknowledges in Discord before applying. You should know exactly what you're signing up for before you spend a minute writing an application.
Hardcore RP. Not a deathmatch, not a PVE stroll. Story first, with the dial turned hard toward the dark side.
๐ซ Zero tolerance. Racism, sexism, hate speech, or toxicity anywhere (Discord, in-game, voice). Not "ironic," not "just my character." Instant removal.
โ๏ธ PVP serves the story. Earned violence, not shooting people because they're there. Want pure combat? That's what scheduled & on-demand events are for: hot zones, raids, contested drops.
๐๏ธ Reputation follows you. We talk to other servers and staff. Changing your tag doesn't reset it. Ban evasion and alt accounts are an instant ban. One person, one identity.
๐ No exploits. Duping, glitching, or abusing any bug for gear, access, or advantage is an instant ban. Find a bug? Report it in a ticket. Don't farm it.
๐ฆด The bar is high. Aggression ceiling is high and bad things happen to good characters, by design. Aggression without intent is just noise.
Play hard. Play honest. Stay in the story.
Discord is part of the world. Keep it clean and useful.
๐ข No mass pings. Never @everyone/@here or staff roles. Pings come from staff only.
๐๏ธ Need staff? Open a ticket for complaints or rule-breaks. Skins handle general questions. Don't DM the Marrow.
๐๏ธ Use the right channels. Staff will move or delete posts that drift.
๐ค No meta. Ever. What happens on Husk stays on Husk: no exposing kills/raids/deaths, no leaking bases or stashes, no tipping your group to things your character doesn't know, no out-of-game chatter that bleeds into in-game knowledge. This rule has the most teeth. Breaking it has consequences.
๐ฅ No stream sniping. Watching a player's live stream to track them, their base, or their group in-game is meta. Same crime, same consequences.
๐ซ No advertising other servers (links or name-drops) without staff approval. Open a ticket to ask.
๐๏ธ Staff are present. Just be someone who doesn't need watching.
The Discord is part of the world. Treat it that way.
People die out here. We just make sure it means something.
๐ฅ Reporting a bad kill: open a ticket in Discord. A clip is required. No clip, no review.
๐ฉป Before you shoot, ask: Does this kill need to happen? Could you walk away? Could you talk first, even with a gun raised? If you can't justify it, it wasn't RP, it was aiming.
โข "Hands up" then instantly shooting is not a hold-up. It's treated as a bad kill.
๐ No combat logging. Never log out during or right after a fight, hold-up, raid, or capture. Give it a few minutes once the area is clear. Disconnecting to dodge danger is a bad kill in reverse and earns a ban.
โข A pattern of empty kills earns a ban. No three-strikes. We watch the shape of how you play.
๐ซ Your ticket: one Shell owns it; serious calls escalate to the other Shells, then the Marrow. Verdicts stay private.
๐ฉท Staff are unpaid volunteers. Give it 24h before nudging.
The system holds because we hold it. Don't undercut it.
Raiding is the loud, ugly end of a long story, not a loot shortcut.
๐ข Raid bans are set each season and updated in announcements. Read them before you swing.
This applies to any base with a flag: a faction, a duo, or a solo white-flag. If it has a flag, the rules below apply.
There are two ways into a base, and they play by different rules:
๐ฅ Blowing in (explosives) means YOU MUST DECLARE FIRST:
1. Declare it. /raid declare and name your target. Don't know who owns it? Just name the base or its location: a faction, a player, or "the base at [place]" all work. Give your RP reason (proof optional). Recorded privately, you get a code. The defender is not told.
2. Arm an explosive at their base. An IED, claymore, land mine, or plastic explosive officially starts the raid.
3. Defenders get fair warning. The instant it starts, the defending base is alerted that someone is raiding them. No names, no numbers.
โ ๏ธ Blowing into a base without declaring first is a punishable offense. No exceptions, no "I had a reason."
๐ชค Sneaking in (no explosives) needs NO declaration:
โข If a base's own bad design leaves a legit gap you can physically walk, climb, or crouch through, take it. No declaration required. But glitching, clipping through walls or textures, or exploiting build/terrain bugs is NOT "bad design." It's an exploit, and it's a ban.
โข Code-rolling is allowed and also needs no declaration, but you must have a valid RP reason. Don't roll digits because you're bored.
โข Either way, be ready for the questions. Staff may ask, so have your reason straight.
โข You can dismantle your way back out without declaring, as long as you're not trashing the place.
๐ซ NO BOOSTING. EVER. No getting in or over walls off players, gear, OR vehicles. No stacking, climbing, or using anything as a ladder. Applies to every raid, declared or not.
While raiding, also do NOT:
โข Build anything to get in or around: structures, storage, vehicles, dropped items
โข Do excessive damage to walls/vehicles, or dismantle player structures unless needed to progress
โข Dismantle improvised shelters (tarps, leantos) at all
๐ช Loot etiquette: no popcorning. Take what you want, stow or neatly pile the rest. Don't spray gear across the lawn.
๐ข Codes: change one only while defending, and it returns to the original owner afterward. No griefing or hostage-holding.
Raid like it costs something. Because it does.
The bot is part of the world. Treat it like story, not a toy.
โณ Earn your link. Be on the server 15 minutes before you link your gamertag (use your displayed in-game gamertag).
๐ฏ Don't kill Quest NPCs. It breaks quest lines for everyone. No exceptions, no "I didn't know." You may end up in a cell.
๐๏ธ Don't abuse the tools. No spamming tapes, notes, boards, or quest submissions, and no exploiting for rewards.
๐ซ Watch what you leave behind. Notes, tapes, and posts are held to the same standard as Discord and in-game. Crossing the Ethos line gets it removed and may end your run.
๐ Read the manual. The Discovery manual channel in Discord covers linking, POIs, boards, quests, broadcasts, and tapes.
The world is listening. Don't shout into it for the sake of it.
Two kinds of wheels now: personal vehicles and taxis.
๐ Personal: Trucks & Humvees ONLY. The only vehicles you can keep as personal. Limit 2 per base/faction (solo players with a base get an allowance too). They can be parked in or at your base. Going over the limit or hoarding is handled by admins, with proof of the violation.
๐ Taxis (everything else): the vehicles scattered around the map. Use them, but:
โข You're the driver. Nobody's coming to pick you up.
โข Random spawns, no set time or place (don't pattern it). They last as long as they last.
โข Gear left in a taxi is gone when it despawns or dies. Don't use the trunk as long-term storage. Stay near it if you want it to stick around.
โข Use at your own risk. Taxis are a privilege, not a right. Staff will not entertain complaints about lost taxis or the gear left in them.
โ ๏ธ Cars aren't free KOS. The KOS rules still apply. But approach, follow, or ambush a car wrong and things can go sideways fast; the driver doesn't owe you patience.
Drive like you'll lose it. Because you will.
(You only declare when you're blowing in with explosives. Sneaking in or code-rolling needs no declaration, just a valid RP reason.)
Why declare?
A declaration ties your explosive raid to a real reason, a real person, and a timestamp. It keeps raids story-driven instead of "free gear runs." And it's what protects YOU if you're ever accused of raiding for nothing.
๐ Why staff genuinely cannot see your declaration
This isn't "trust us." It's how it's built:
โข There is no raid-archive channel. Nothing is posted anywhere: not public, not staff-only, not hidden. There is literally no list to open.
โข Your declaration is sealed in the bot's database. The only way to open one is to look it up by its exact code.
โข Only YOU have your code. It's DM'd privately to you and nowhere else. Staff don't have it. The owner doesn't have it.
โข So unless you personally hand over your code, it stays sealed. No one can browse, search, or stumble onto it.
๐ซ How the code works if your raid is disputed
A defender complains you raided them for no reason. Here's exactly what happens:
1. A Shell opens a review.
2. To clear your name, you give the reviewing staff your code.
3. The staffer looks it up with your code, the only way a declaration is ever opened. Up comes your reason, proof, and timestamp.
4. Checks out? You're cleared. Your declaration is your alibi.
5. Can't produce a valid code? Then there's no proof you declared, so the raid is treated as undeclared and illegitimate. That's on you.
And even that lookup is logged: who opened what, when. The one time your declaration is ever seen, it's on the record.
๐ Your target never knows
Declaring tips off no one. No ping, no DM. The defender has zero idea until you actually start the raid in-game. Your surprise is 100% intact.
Read it all? Good. That puts you ahead of most applicants.
Apply on Discord โ