🛠️ Developer & Content Creator Rules

[Z I Z O U]

Two roles, two different toolkits, one standard. Developer and Content Creator are staff roles without a ban button — you are trusted with things the rest of the team cannot touch, so the bar is higher, not lower. The shared team rules are in Staff Rules; this thread is what applies to your specific job.

Developer

• Production is not a playground. Test on a staging copy first. Never restart, edit or debug a live plugin or the database while players are on the server.
  
• Nothing ships unreviewed. Changes go through the repository and are reviewed before deploy — no "quick fix" pasted straight onto the server.
  
• Write it down. Every change gets a short note: what it does, what it touches, how to roll it back. The next developer is not a mind reader.
  
• Access is not a licence. You will see player data, IPs and logs while working. Look at what the task needs, nothing else, and never share it.
  
• Never share credentials. No FTP, panel, database or bot token goes to a friend, a "helper" or anyone outside the team. Use 2FA where it exists.
  
• Do not promise fixes. "It will be done this week" is a promise you do not own — say what you are looking at and when you will know more.
  

Content Creator

• You are the brand on camera. The same conduct rules as everybody else apply in your videos, streams and comments — including when you are in other communities.
  
• No leaks. Unreleased features, events, staff discussions and private member data stay off the timeline until they are public.
  
• Spoilers stay out of public channels. Upcoming events are announced when management announces them, not when you find out.
  
• Official assets only. Use the current logo, the current server address and the current links — an outdated link on a video with 50k views costs us players.
  
• Say what is sponsored. A paid promotion or a gifted product is disclosed. Our credibility is worth more than one deal.
  
• Escalate, do not moderate. Harassment, cheating accusations and drama in your comments or chat are reported to the moderators — you do not answer them with a ban.
  

Both roles

• Activity is judged by output, not hours: shipped changes, published content, and being reachable when the team needs an answer.
  
• Going away? Log it like everybody else — Staff Inactivity. During a leave the tools stay off until you request return.
  
• Stepping down? Staff Withdrawal, with a handover of whatever you own.
  
• Questions about priorities come from management, not from whoever pings you loudest.
  

Applying
Both roles are applied for through the Server Application — pick Developer or Content Creator inside the form and only that role's questions appear. A linked CS 1.6 account is required, and your hours on the server are shown on the form.

See also: Staff Rules · Staff Inactivity Policy · Admin Server Rules

— UNCAP Management