|
|
| Line 1: |
Line 1: |
| TermOS is a lightweight operating system for terminals, used primarily for the Research Department's network.<br>
| | Read the Rules |
| Terminals act as interfaces to networked servers and devices. Once connected to a server, all commands are sent from your terminal to the server, where they are actually run.
| |
|
| |
|
| Servers you can connect to include the Research Department's Mainframe and the Centcom Communications Array.
| | Admitting that you didn't read the rules when questioned by an admin about something you did won't get you out of trouble. |
|
| |
|
| Every device on the network is connected to through a data terminal directly below it. These transmit data through the station's power lines.
| |
|
| |
|
| Devices have a net_id, which is their address on the network (an 8 digit string); and a type, which describes their function.
| | No racial or homophobic slurs. |
| ::P: [02002776]-TYPE: PNET_MAINFRAME ''This is the Research Mainframe at address 02002776''
| |
|
| |
|
| To operate any networked device you will have to ping, then connect to it.
| | It doesn't matter who you are or how you talk to your friends. Racially and homophobic loaded words are not allowed. |
| | Don't call people names, or use them in some ironic remark. Don't put them in your character name. It will get you warned or banned. |
|
| |
|
| ==Connecting==
| | No creepiness; no sexual jokes. |
| ;help:The most '''important command'''. Displays all available commands and their usage. | |
| ;term_ping:Pings the network and displays a list of all connected devices and their net_id. (Devices which are disconnected will not display. None will display if YOU are disconnected.)
| |
| ;connect ''net_id'':net_ids are 8 digits. For example, ''connect 02002ceb'' will have the terminal connect to the device. More commands will be available once connected and logged into a device.
| |
| ;term_login:Logs you into the terminal. Your ID must be inside the terminal to log in. With your ID in your active hand, click the '''-----''' below the screen to insert your ID.
| |
| ;diconnect:This will disconnect your terminal from the server you are currently connected to. <del>no shit</del>
| |
| ;restart:Reboots your terminal. It disconnects from any device you were connected or logged into.<br> This can be handy if the device is locked up or prevents normal use of disconnect. Overuse of restart is analogous to rebooting your computer every time you open the wrong web page, and is hence discouraged.
| |
|
| |
|
| | This includes rape jokes, or roleplaying sex, sexual harassment/assault, or rape. Basically, if it involves your genitals it doesn't belong here. |
|
| |
|
| | Gameplay rules. |
|
| |
|
| ==The Network==
| | Don't talk with other players outside of the game. |
|
| |
|
| [[File:Outpost_Computers.png|right|frame|Every networked device in the Research Sector.]]
| | Communications and eavesdropping on other players' conversations are an important part of the game. |
| <br><br>
| | If you are playing with friends, talk to them in the game chat. |
| ===DWAINE===
| | Don't use skype, ventrilo or IMs to coordinate or ask for their help. |
| <br>
| |
| DWAINE is the operating system of Research Mainframes. Scientists use it to run their research programs. Research Directors program guardbuddies on DWAINE.
| |
|
| |
|
| DWAINE is a networked OS. The Mainframe runs the OS and programs, and acts as a bridge between terminals and devices.<br>
| |
| Devices - data banks, printers, robuddy docks, radios - are connected to the Mainframe through the network.<br>
| |
| Finally, terminals act like a keyboard and monitor, they display program interfaces and transmit commands to the Mainframe.
| |
|
| |
|
| Log into a terminal by inserting your ID card and typing ''term_login''. When you login at a terminal your home directory is created on the Mainframe's storage. This folder is only accessible to you and superusers. It will generally be preserved between logins, provided you only login to one terminal at a time.
| | Don't use multiple accounts. |
|
| |
|
| There are two access levels on DWAINE: ''regular users'' only have write access to their home folder, and read access to data banks. They can however directly send commands to peripherals.<br>
| | When you die in a round, don't reconnect using a different account. You'll have to hope that someone clones you or turns you into a borg. |
| ''Super users'' status requires logging in with a head id; they can read and write to any folder on the system, including other users' private homes, and write/delete files on data-banks.
| |
|
| |
|
| | If you have siblings or friends playing on different computers in the same house/network use adminhelp to let us know and not be accidentally banned as a multikeyer. |
| | Even in these instances, you can't play a round with two different accounts on the same computer. |
|
| |
|
| ===Files===
| | Don't grief. |
| DWAINE runs on the Mainframe in the central part of the research wing. OS files and user homes are stored on a removable electronic board.<br>
| |
|
| |
|
| Program files are stored on magnetic tapes plugged into one of several data-banks.
| | Don't start fights to have an excuse for killing people. |
| Available data-banks are listed in the directory /mnt.
| | Don't upload laws that allow the AI to murder unless you are a traitor. |
| Important banks are:
| | Don't cause workplace accidents (fires, explosions, harmful gas leaks) to injure or kill other players. |
| *Control: currently holds copies of the guardbuddy control files and scripts. It is located in the RD's office. It takes the mountpoint ''/mnt/control''.
| |
| *Artlab: is the databank in Artifact Research. By default, it contains artifact research software. It takes the mountpoint ''/mnt/artlab''
| |
|
| |
|
| Databanks can be accessed in the same way as any other folder in the operating system, with the caveat that any file I/O will have a minor delay that could interfere with scripting. It is a good idea to double check any file transfers to them, in case the tape has been write-protected or removed.
| | When acting in self defense, try not to escalate fights. Incapacitating people or calling security is better than murdering them. |
|
| |
|
| ===Peripherals===
| | Don't roleplay a psychopath to have an excuse for killing or harming people. |
| To interface with peripherals the Mainframe uses a series of device drivers and mountpoints. All drivers are on the Mainframe by default.
| |
|
| |
|
| Peripherals include databanks, printers, guardbuddies and their radio. Many of these feature some manner of interface with the file system in the form of a mountpoint in the directory /mnt. Mountpoints are like folders, their contents can be listed, and files can be copied to them
| | Don't explode bombs or release harmful chemicals on the escape shuttle just because the round is about to end. |
| | You can do this once the shuttle has left and the round has finished |
|
| |
|
| For a list of currently connected peripherals, scan the contents of /mnt ''ls /mnt'.<br>
| | Don't carry grudges across rounds. |
| Peripheral can contain files, receive commands, or both.
| |
|
| |
|
| ===Commands===
| | Don't take revenge for something that happened in a previous round. Every round is separate, or we wouldn't hear the end of players settling their scores from previous games. |
| The in-system help file is currently a work in progress, but may be accessed by the command ''help''.<br>
| |
|
| |
|
| '''File operations''': | | Don't metagame. |
|
| |
|
| *'''ls''': and an optional argument specifying the filepath. If no filepath is supplied, it will list the contents of the current working directory.
| | Don't use your knowledge of game mechanics to your advantage. |
| *'''cd''' ''"filepath"'' changes the current working directory. If the filepath is not prefixed with a forward slash, it will be taken as relative to the current directory. For example, "cd /" would set the working directory to root, and then a subsequent "cd mnt/artlab" would have the same effective result as "cd /mnt/artlab"
| | For example, you know this game has traitors. When you see a chef breaking into chemistry, do not automatically call him a traitor because he's somewhere he doesn't belong. |
| *'''rm''' [-r/i/f] ''"filepath"'' removes a target file or directory. The user must have appropriate access to the target file. There are three possible command switches, which may be combined (e.g. -r, -rf, and -if would all be valid). ''r'', recursive, is necessary for the deletion of directories. ''i'' instructs the system to confirm before deletion with a simple yes/no dialog, and ''f'' suppresses response messages (And overrides ''i'').
| |
| *'''cp''' ''"filepath to copy" "destination filepath"'' will make a copy of the file at the first filepath and place it in the destination. If the destination is a directory, the copy will try to maintain the name of the original.
| |
| *'''mv''' ''"filepath to move" "destination filepath"'' functions in much the same way as cp, with the exception that the original file will be removed following the copy operation.
| |
| *'''chmod''' ''"new permission value" "target filepath"'' will change the access permission of a target file. The permission value takes the form of three octal digits, going (from left to right) owner access, group access, and other access. Each can be thought of as three-bit binary values, bit 1 (the least significant) controlling modify access, bit 2 controlling write access, and bit 3 controlling read access. For example, the value "777" would be 111 111 111 in binary, and thus would be all access.
| |
|
| |
|
| '''Input/Output''' | | When the round is Nuke, don't enter the syndicate shuttle unless you know for certain (through a pinpointer or the radio) that the Syndicates have the Auth Disk and are arming the nuke. |
| *'''cat''' ''"filepath" [additional filepaths...]'' will print the contents of the document(s) at the specified filepath(s)
| | A last showdown in the shuttle is fine, invading it in any other case is not. |
| *'''echo''' ''[text...]'' will print provided text to the current output stream. By default, this is the user's terminal. This may also be '''piped''' into a record file by use of ''^''. For example: ''"echo Hello, World! ^ ./file"'' will create a file named "file" in your current directory (Assuming you have write access) containing the the text "Hello, World" "|n" may be used to establish newlines.
| |
|
| |
|
| '''System Utilities'''
| | Reply when an admin questions you. |
| *'''su''' is used to assume superuser status. After executing su, insert an authorized (station heads) ID card and follow on-screen instructions.
| | From time to time an admin is going to ask about some actions you performed in the game. |
| *'''who''' will list the usernames and network IDs of other current users on the system.
| | Explain what you did, and try to keep a civil tone. Sarcasm is not well received. |
| *'''talk''' ''"username or network ID"'' ''"message"'' will send a message to another user on the system.
| |
| *'''mesg''' ''[y/n]'' Will allow/disallow receiving messages from other users, or, if invoked without arguments, will show the current acceptance status.
| |
|
| |
|
| *'''logout''' ''or'' '''logoff''' will do exactly what you would expect.
| | Don't impersonate admins. |
| | Just don't. |
|
| |
|
|
| |
|
| ==Printing Files==
| | Punishments |
| Any valid document copied to the mountpoint of a printer will be printed. The printer mountpoints are, in /mnt, and are generally prefixed with "lp-".
| |
| ''cp filename /mnt/lp-artlab'', will order the printer in Artifacts Lab to print the contents of filename.
| |
|
| |
|
| ==GuardBuddies==
| | Warning |
|
| |
|
| Using the DWAINE terminals, you can assign [[Robots|Guardbuddies]] to various jobs. To start playing with your buddies, follow these instructions. Italicized words are commands you input into the computer:
| | Simply being told to quit what you're doing ingame, either by direct PM or a "voice in your head". You'll probably get punished harder if you ignore a warning. |
|
| |
|
| *Insert your ID card into the terminal<br>
| | Muting |
| *''term_login''<br>
| |
| *''su''<br>
| |
| *''term_login''<br>
| |
| *Eject your ID card<br>
| |
| *''cd /mnt/control''<br>
| |
| *''prman list''
| |
|
| |
|
| You are now in the folder with the GuardBuddy controls, and you have big boss access so they actually listen to you. The list you see before you will show your little minions with their network IDs and their equipped weapon.
| | Muting stops you from talking on ALL channels. |
|
| |
|
| ===Assign a buddy to guard===
| | Prison |
| *''guard_script (network ID) (name without spaces)''<br>
| |
| The computer should respond ''Transmitting wake command''. The buddy should be active, with a small face on its viewscreen. When it gets close enough to see whomever they are guarding, they will point at that person and announce they are under guard. If the guard target does not have access to the Guardbuddy bay, you might need to drag it out to meet its ward. Don't always think a guard is a good thing, though...many flavors of Guardbuddies are capable of friendly fire, and that can leave you vulnerable to antagonists - perhaps even the devious RD who assigned the buddy in the first place!
| |
|
| |
|
| ===Assign a buddy to patrol===
| | Your character will be sent to the Punishment Dimension, where an admin (should) contact you shortly to ask questions. This is just a holding area and not a punishment in itself - if you can satisfy the admin that you weren't being shit, you'll be returned to the station. |
| *''patrol_script (network ID)''<br>
| |
| The computer should respond ''Transmitting wake command''. The Guardbuddy will wake up and behave much like a [[Securitron]], roaming the halls and arresting people doing bad things. This is a good thing to fall back on if you don't have something better for the buddy to do, but don't want it idle.
| |
|
| |
|
| ===Assigning a buddy to purge===
| | If you ever get sent here and questioning doesn't occur after a few minutes, adminhelp it. |
| *''prman upload purge (network ID)''<br>
| |
| *''prman wake (network ID)''<br>
| |
| This one doesn't have a fancy control script with it because you really, really should not be uploading this command unless you are a traitor or everything has completely gone to hell. When under these orders, the Guardbuddies figure 'if it ain't a Head, it's dead.' They will roam station and arrest anyone not showing a Head ID, causing mass havoc. Laser blasts from one of the lasers or Energy guns around the station will also stun a buddy and make it a sitting duck to repeated blasts.
| |
|
| |
|
| ===Recall the buddies===
| | Death and/or Humiliation |
| *''prman recall (network ID)'' OR<br>
| |
| *''prman recall all''<br>
| |
| This will order the buddies back to their charging bays and cancel all standing orders. This is useful if a traitor got into your controls and corrupted the buddies.
| |
| Be aware that the mainframe radio has a limited range, and may not be able to recall guardbuddies too far away from the Research Sector.
| |
|
| |
|
| ==Radio==
| | Usually reserved for something annoying but not quite bannable, such as incessantly whining. If you're not reduced to a pile of mushy gibs or struck dead on the spot you can expect to be made fat, stupid, a lizard, or being the subject of an announcement marking you for the crew to beat down. In these cases, nagging adminhelp your fate will only make things worse. |
| If connected, the radio interface module (Used primarily by the Guardbuddy software to recall them) will appear at ''/mnt/radio''. This can be used to transmit packets simply by writing a record file to it, each line being interpreted as a separate key in the radio packet. For example, "echo command=dostuff|naddress_1=020000FF ^ /mnt/radio/test" would cause the radio to transmit a packet on the default frequency with two entries, "command" equal to "dostuff" and a target address equal to 020000FF. It should be noted that all packets sent in this method must have the address_1 value specified to be transmitted.
| |
| <br>
| |
| <br>
| |
| If you wish to send a signal on a frequency other than the radio's default (the Guardbuddy communication frequency), include a line in your file specifying the value of "_freq" such as "_freq=1149" to transmit over the PDA communication frequency 114.9.
| |
|
| |
|
| ==Troubleshooting==
| | Job Ban |
| When a terminal become unable to connect to the network some elements may be damaged.<br>
| |
| As the network is wired, a severed cable is the most frequent problem, and requires to track the missing section in the cables between the devices you are communicating with.
| |
|
| |
|
| [[File:Terminal_Blowout.png|thumb|Data Terminal|right]]
| | It will prevent you from selecting certain jobs. |
| Every device is connected to the wires through a data terminal. Data terminals are directly under the device, hidden by the floor tile. Network cables run between terminals to connect devices.<br>
| | These are placed when you use a job to harm other people without being a traitor. Or take a high responsibility job without doing the minimum effort to help the crew; like a captain that forgets to carry the Nuke Authentication Disk, or an AI that will ignore someone's pleas for help. |
| When a data terminal is destroyed, if the device is still functioning, it will be unable to connecto to the network.<br>
| |
|
| |
|
| Terminal themselves are easy to [[Constructions#Computers|build]] and [[Constructions##Computers_2|disassemble]].<br>
| | If you don't like certain jobs so much that you don't even want the risk of being randomly selected for them, you can request a job ban on them. Requested job bans are not punitive measures, so don't worry about them becoming a black mark against you. |
| TermOS can be easily installed from a disk in Tech Storage.
| |
| <br>
| |
| <br>
| |
| This is a list of the most common problems:
| |
|
| |
|
| *Blinking terminal screen
| | Server Ban |
| *: The glass is cracked. Take it off with screwdriver, then crowbar. Replace the glass.
| |
|
| |
|
| *Terminal unable to ping
| | Makes you unable to log onto the server until the ban expires. Pretty self-explanatory. |
| *: Wires might be severed at some point. Search for the damaged cable section and replace it.
| |
| *: A data terminal might have been destroyed by an explosion. Dismantle your terminal and move it onto another data terminal. Or ask the electricians to scan one and make you a replacement.
| |
|
| |
|
| *Programs stop responding. But the terminal is able to ping other devices
| | Permabans will never expire until successfully appealed HERE. |
| *: The mainframe may be damaged. Use the restore kit in the Research Director's office. It comes with instructions
| |
|
| |
|
| *Data Banks cannot be accessed and do not appear in /mnt.
| |
| *: Banks are directly connected to the Mainframe, the cable between them may be damaged. Look for the missing section. Or a missing terminal port.
| |
|
| |
|
| ==Tapping the Wire==
| | Things to Know |
|
| |
|
| Communications between terminals and devices run on the wire; commands are sent as plain-text messages that can be eavesdropped with the proper equipment. If you want to understand how to hack the Mainframe, you should spend a round or two reading network traffic.<br>
| | Warnings Aren't Required |
| The Mainframe on the station is not unique. Another mainframe is at an high-tech location away from the station.
| |
| This is ideal to practice on, if you don't want an angry scientists to blow you up for breaking their work.
| |
|
| |
|
| ==Scripting==
| | Don't complain that you didn't get a warning before being hit with punishment. If you're being sufficiently shit you may earn a straight ban. |
| It is possible to automate function with the use of script files. These are text files with a special prefix that marks them as executable.
| |
|
| |
|
| A sample script to display a few words on screen.
| | Different Admins have Different Styles |
| #!
| |
| echo Hello World.
| |
|
| |
|
| To create this script you must enter the following text.
| | Some admins enforce some rules more harshly than others. |
| | You should never break any of the rules, but if you do don't complain that you were on the receiving end of a stricter admin's wrath. |
|
| |
|
| echo #!|necho Hello World ^./myscript
| | Punishments are Case by Case |
|
| |
|
| "#!" is at the start of every script, to tell the system the file is executable.<br>
| | How much someone else got punished for the same offense doesn't matter to your own punishment. Unless there's a flagrant difference between the two (example: Jimmy Poo got 30 minutes for hitting someone with an extinguisher, and you got a permaban.) |
| "|n" breaks lines in the script, one line for every command.<br>
| |
| "^" marks the path to the file where the script is to be saved (in this case a file named myscript in the current folder).<br>
| |
|
| |
|
| <br>
| | Complaining about an admin. |
| The tape in /mnt/control has some scripts which you can study to understand how more complex scripts can be layed out.<br>
| |
| To read existing scripts, type ''cat filename'' to have the script printed on screen.
| |
| <br>
| |
|
| |
|
| ==Tech Support==
| | If you think you were punished without merit (or if you think someone else's treatment was bullshit) then go to the Unban Appeals section for requesting a review of your ban, or the Admin Complaints section for calling out bad admin behavior. |
|
| |
|
| our Help Line is currently unavailable as conversion to automated Buddy Troubleshooters is in progress.<br>
| | When arguing your case, try to be reasonable and if you did break a rule, don't try to weasel out of it by saying dumb things like "I didn't mean "harsh word against minorities" that way", or by denying everything. Admins have logs and they will call you out on your actions if necessary. |
| If you are interested in financially sponsoring the Thinktronic. LTD.robuddy basketball team, please contact Stephen H. Toczylowski.
| |
|
| |
|
| ==Bridge Comm. Console==
| |
| There is one communication console on station. It is on the Bridge, and it is used to connect to Centcom's communication array to download often flawed intel on potential traitors or revolutions, or other messages from Centcom.
| |
|
| |
|
| Instructions are available on a nearby slip of paper.
| | Hilarity Clause |
|
| |
| *Initially two commands will be available.
| |
| *: list: This prints a list of all the Centcom messages available to download and their messages IDs
| |
| *: download: Download (message ID)
| |
|
| |
|
| When a file is downloaded it can be printed with the file_print command. Simply examine the paper to read the message.
| | If you make a transgression against the rules but do so in a manner which is incredibly entertaining or funny, youmight avoid punishment for your actions. |
| | |
| | Bear in mind that "funny" is entirely relative and it is purely up to the admins to decide if you were funny enough or not - also bear in mind that we've seen many things a lot of times before. If you're going to shoot for this rule, be original. Copycatting someone else's shtick won't end well for you. |
| | |
| | Sploded Clause |
| | |
| | If you havebeen a consistently terrible player for a long time, the admins can ban you on your history alone, and do not need any further excuse or cause. |
| | This rule generally requires several admins to be in agreement that you are utter shit before taking any action, you have to get on a lot of people's nerves. |
| | |
| | Named after Sploded, aka Dr. Von Overdose, a terminally shitty player who would constantly grief and fuck things up for other players while adminhelping anything that happened to him. This is not something to be proud of! |
| | |
| | Lord Doom Clause |
| | |
| | The rules do not apply to Lord Doom. This works both ways. |
| | |
| | He can do anything he wants to you, but on the other hand you can also do anything you want to him with no fear of consequences. This only applies to the person with the BYOND key Lord Doom and never anyone else. Especially not you. Don't try it. |
Read the Rules
Admitting that you didn't read the rules when questioned by an admin about something you did won't get you out of trouble.
No racial or homophobic slurs.
It doesn't matter who you are or how you talk to your friends. Racially and homophobic loaded words are not allowed.
Don't call people names, or use them in some ironic remark. Don't put them in your character name. It will get you warned or banned.
No creepiness; no sexual jokes.
This includes rape jokes, or roleplaying sex, sexual harassment/assault, or rape. Basically, if it involves your genitals it doesn't belong here.
Gameplay rules.
Don't talk with other players outside of the game.
Communications and eavesdropping on other players' conversations are an important part of the game.
If you are playing with friends, talk to them in the game chat.
Don't use skype, ventrilo or IMs to coordinate or ask for their help.
Don't use multiple accounts.
When you die in a round, don't reconnect using a different account. You'll have to hope that someone clones you or turns you into a borg.
If you have siblings or friends playing on different computers in the same house/network use adminhelp to let us know and not be accidentally banned as a multikeyer.
Even in these instances, you can't play a round with two different accounts on the same computer.
Don't grief.
Don't start fights to have an excuse for killing people.
Don't upload laws that allow the AI to murder unless you are a traitor.
Don't cause workplace accidents (fires, explosions, harmful gas leaks) to injure or kill other players.
When acting in self defense, try not to escalate fights. Incapacitating people or calling security is better than murdering them.
Don't roleplay a psychopath to have an excuse for killing or harming people.
Don't explode bombs or release harmful chemicals on the escape shuttle just because the round is about to end.
You can do this once the shuttle has left and the round has finished
Don't carry grudges across rounds.
Don't take revenge for something that happened in a previous round. Every round is separate, or we wouldn't hear the end of players settling their scores from previous games.
Don't metagame.
Don't use your knowledge of game mechanics to your advantage.
For example, you know this game has traitors. When you see a chef breaking into chemistry, do not automatically call him a traitor because he's somewhere he doesn't belong.
When the round is Nuke, don't enter the syndicate shuttle unless you know for certain (through a pinpointer or the radio) that the Syndicates have the Auth Disk and are arming the nuke.
A last showdown in the shuttle is fine, invading it in any other case is not.
Reply when an admin questions you.
From time to time an admin is going to ask about some actions you performed in the game.
Explain what you did, and try to keep a civil tone. Sarcasm is not well received.
Don't impersonate admins.
Just don't.
Punishments
Warning
Simply being told to quit what you're doing ingame, either by direct PM or a "voice in your head". You'll probably get punished harder if you ignore a warning.
Muting
Muting stops you from talking on ALL channels.
Prison
Your character will be sent to the Punishment Dimension, where an admin (should) contact you shortly to ask questions. This is just a holding area and not a punishment in itself - if you can satisfy the admin that you weren't being shit, you'll be returned to the station.
If you ever get sent here and questioning doesn't occur after a few minutes, adminhelp it.
Death and/or Humiliation
Usually reserved for something annoying but not quite bannable, such as incessantly whining. If you're not reduced to a pile of mushy gibs or struck dead on the spot you can expect to be made fat, stupid, a lizard, or being the subject of an announcement marking you for the crew to beat down. In these cases, nagging adminhelp your fate will only make things worse.
Job Ban
It will prevent you from selecting certain jobs.
These are placed when you use a job to harm other people without being a traitor. Or take a high responsibility job without doing the minimum effort to help the crew; like a captain that forgets to carry the Nuke Authentication Disk, or an AI that will ignore someone's pleas for help.
If you don't like certain jobs so much that you don't even want the risk of being randomly selected for them, you can request a job ban on them. Requested job bans are not punitive measures, so don't worry about them becoming a black mark against you.
Server Ban
Makes you unable to log onto the server until the ban expires. Pretty self-explanatory.
Permabans will never expire until successfully appealed HERE.
Things to Know
Warnings Aren't Required
Don't complain that you didn't get a warning before being hit with punishment. If you're being sufficiently shit you may earn a straight ban.
Different Admins have Different Styles
Some admins enforce some rules more harshly than others.
You should never break any of the rules, but if you do don't complain that you were on the receiving end of a stricter admin's wrath.
Punishments are Case by Case
How much someone else got punished for the same offense doesn't matter to your own punishment. Unless there's a flagrant difference between the two (example: Jimmy Poo got 30 minutes for hitting someone with an extinguisher, and you got a permaban.)
Complaining about an admin.
If you think you were punished without merit (or if you think someone else's treatment was bullshit) then go to the Unban Appeals section for requesting a review of your ban, or the Admin Complaints section for calling out bad admin behavior.
When arguing your case, try to be reasonable and if you did break a rule, don't try to weasel out of it by saying dumb things like "I didn't mean "harsh word against minorities" that way", or by denying everything. Admins have logs and they will call you out on your actions if necessary.
Hilarity Clause
If you make a transgression against the rules but do so in a manner which is incredibly entertaining or funny, youmight avoid punishment for your actions.
Bear in mind that "funny" is entirely relative and it is purely up to the admins to decide if you were funny enough or not - also bear in mind that we've seen many things a lot of times before. If you're going to shoot for this rule, be original. Copycatting someone else's shtick won't end well for you.
Sploded Clause
If you havebeen a consistently terrible player for a long time, the admins can ban you on your history alone, and do not need any further excuse or cause.
This rule generally requires several admins to be in agreement that you are utter shit before taking any action, you have to get on a lot of people's nerves.
Named after Sploded, aka Dr. Von Overdose, a terminally shitty player who would constantly grief and fuck things up for other players while adminhelping anything that happened to him. This is not something to be proud of!
Lord Doom Clause
The rules do not apply to Lord Doom. This works both ways.
He can do anything he wants to you, but on the other hand you can also do anything you want to him with no fear of consequences. This only applies to the person with the BYOND key Lord Doom and never anyone else. Especially not you. Don't try it.