Staff Guide

Core conduct and banning policies for Zee Hood staff.

1. Banning Policy

In-game bans must follow strict formatting to ensure logs are clear and consistent.

/tempban [user] 999d [reason]/zeehoodd

IMPORTANT: You MUST include our vanity /zeehoodd in every ban message or you will receive a strike.

2. Abuse Rules

Abuse of power is strictly prohibited and results in immediate demotion.

Combat Restriction: Using commands like /restore, /bring, or /god during or after fights is prohibited.
Zero Advantage: Commands must not provide any combat advantage. If attacked, you cannot use commands.
Unbiased Moderation: Treat all players equally. Friends do not receive special treatment.

Staff Code of Conduct

Maintaining the integrity of Zee Hood is the top priority for all personnel.

Exclusive Representation: Staff are strictly prohibited from promoting, repping, or working for competing projects/games.
Professionalism: Always maintain a respectful and professional tone when interacting with players, even if they are being toxic.
Internal Privacy: Never leak staff-only information, upcoming maps, or moderation discussions to the public.
Active Presence: You must remain active both in-game and in the Discord server to maintain your position.
Chain of Command: Respect the hierarchy. If you have a dispute with another staff member, take it to Management privately.

3. False Banning Policy

1 False Ban (No Clips) 1 Strike

2 False Bans (With Clips) 1 Strike

Total Strikes 2 = Termination

Host Events / Tryouts

Standard protocol for managing in-game events and professional tryouts.

Requirements to Host

Before you are eligible to lead a tryout or event, you must meet these criteria:

Live Audio: You must have a working Microphone to communicate rules clearly.
Hardware: Hosting requires a PC (No mobile/console hosting).
Expertise: You must possess **Basic Knowledge on Cheats** to effectively review clips.

Hosting Phase: Rules Pitch

Once players are lined up at School, you must read these rules clearly in the Stage Chat:

• Weapons: DB, TAC, REV, KNIFE Only
• Requirement: 5 Overall Wins = Wall
• Range: Winner Picks Range
• Strict: NO Auto-Clicker, NO Macro, NO Lay, NO Headless
• Quality: Must clip ALL 5 kills to join Wall
• Final Step: PC check required at the end

Region Filtering: If EU tryout, ban all NA. If NA tryout, ban all EU. Non-regioned players join the closer server.

Stage 1: Standard Tryouts

Fair Picking: Pick players strictly from the Top to Bottom of the panel. Random picking is prohibited.
Point Tracking: When a player wins a 1v1, update their points in the panel (Type Area).
Wall Selection: Once a player reaches 5 points, Jail them on the opposite side of the school. They are now a "Wall".
Verification: Stop at 5 Walls. Require all 5 players to create a ticket and send their 5 clips immediately.
S-Lock: Run /slock and kick everyone who is not a Wall once clips are verified.

Stage 2: Semi-Finals

Line the 5 Walls up. Pick from Left to Right.

Format: The first two players on the left 1v1.
Rotation: The loser goes to the end of the line (Right). The line carries on.
Selection: Continue until 2 finalists reach 5 points each.
Clips: Both finalists MUST send all 5 clips of their semi-final kills into their ticket.
Cleanup: Kick the other players once finalists are confirmed.

Stage 3: The Finals

Rules: DB, TAC, REV, KNIFE. Range cycles every 1v1 (Close → Mid → Far).

Finalists 1v1 to a score of 5 points.
Winner sends all 5 clips into the ticket.
Final Step: Check clips, log the win, and send the player for a mandatory **PC Check**.

Ticket Guide

Professional handling of exploiter reports and appeals.

Exploiter Reports

Always maintain professional language. Follow this workflow for every report:

Ask for a clear clip and the username.
Verify cheating is visible. If the name isn't in the clip, ask for separate proof of identity.
Double-check usernames. Wrong IDs lead to strikes.

Renaming Guide

Use these status tags to organize the ticket channel:

/rename done /rename needs higher up /rename waiting for clips

Appeal Management

If a player provides solid evidence:

Ping a Higher-Up.
Wait for confirmation on the evidence.
Execute /unban only after the all-clear.

Ban Bot System

Discord-integrated moderation tutorial and procedure.

1. How it Works

The Ban Bot can be operated in two ways for maximum flexibility:

Via DMs

Message the bot directly with your command. Perfect for private handling of cases.

Via Server

Use commands in the designated staff channels. Keeps the team synchronized.

2. Command & Evidence Tutorial

Professional bans REQUIRE evidence. Follow this precise workflow:

Initiate: Type /ban [user] [reason] in the chat.
Attachment: When the bot prompts, upload your clip or image directly. The bot will automatically host the evidence.
Sync: Once confirmed, the bot pushes the ban to the global database and the Roblox game servers instantly.

3. Realistic Ban Embed Mockup

This is exactly how a processed ban will appear in the staff logs:

Phase 1: Confirmation Request

Zee Hood Ban Bot BOT

⚠️ Confirm Permanent Ban

Target User

Exploiter123 (ID: 15928374)

Reason

Flying / Silent Aim - /zeehoodd

Phase 2: Success Notification

Zee Hood Ban Bot BOT

✅ User Successfully Banned

Status

Confirmed & Synced to Roblox Servers

Database ID

#ZH-8923-BAN

BAN BOT RULE: Never ban without attaching a clip. Incomplete logs result in immediate strikes.

Content Creator Requirements

Metrics and guidelines for joining the Zee Hood program.

TikTok

Followers: 1,500+

Avg Views: 2,000

Avg Likes: 150

1-4 Zee Hood videos (Recent)
Post 2x per week
/zeehoodd in caption

YouTube

Subscribers: 500+

Avg Views: 1,500

Avg Likes: 50

2-4 Zee Hood videos (Recent)
Post 1-2x per week
/zeehoodd in description

TikTok Live / Streaming

Streamers must maintain these metrics:

Avg 50+ viewers.
Stream at least 2x a week.
Maintain 2-3 recent Zee Hood related clips.

Blacklisted members are permanently ineligible for the program.

PC Check Rules

Strict anti-cheat policies for different roles.

Personnel Policy

Staff Members

Absolutely NO cheats allowed on computer. Zero tolerance.

Stars / Star Legends

No exploits allowed. If found, must factory reset or be removed.

Crew Owners

Exploits allowed for other games, but immediate blacklist if used in Zee Hood.

Ocean Scan – Staff Procedure

Follow this multi-stage protocol for every manual PC scan:

1. Generate the Pin

Go to Dashboard → Pins and click "Create Pin".
Select the correct game (Roblox).
Name the pin clearly: DiscordName – Tryout Winner or DiscordName – Normal Check.

2. Deployment

Copy the generated URL and send it to the player.
Direct them to join the designated voice channel and start screensharing their full screen.

3. Live Monitoring

Ensure they open the link themselves. Confirm full screen is visible at all times.
Watch for suspicious behavior (tab switching, deleting files, stopping share).
NEVER request passwords, 2FA codes, or personal account access.

4. Wait for Results

The scan will process and return results to the dashboard.
Do not conclude the check until results are fully visible.

5. Review & Conclude

Automated scans may false flag — manually review all detections.
Cross-check flagged items with known cheat categories.
If clear, close the check. If confirmed, apply punishment and document the outcome.

Star Challenge Protocol

Official rules for Star matches and logging.

Challenge Setup

Region Lock: Only NA vs NA and EU vs EU. No cross-region.
Setup: Create ticket, add both players. Star sets ping.
Observation: Join private server, enable Aimview on both.

Round Cycles

Each round alternates range. First to 5 kills wins.

Close

Mid

Far

Victory & Results

Winner must send clips of ALL KILLLS. Log winners in the official Discord channel. Ping Management if a Star loses for rolling.

Quota & Promotions

Performance metrics and career path.

Weekly Quota

80

Total weekly bans required

Checks: Sunday, 3PM EST

Strike System

Strikes reset weekly on Sundays after quota checks. 3 strikes result in permanent termination.

Command Reference

Quick lookup for staff controls.

Adonis Commands

/restore [user] Full heal/ammo (Do not abuse)

/bring [user] Teleport user to you

/tempban [u] [t] [r] Standard ban (include vanity!)

/unban [user] Lift restriction (HQ clear only)

Keybinds

B Open Staff Panel

!hideemoji Toggle emoji visibility

!showemoji Enable emoji visibility