Page 1 of 1

Ban Request section rules (READ BEFORE POSTING)

Posted: Fri Apr 18, 2014 6:04 pm
by Hibbles
---JUST TO REITERATE---

The Anon3 amendment is STILL in effect.

Please read below for details.

Anyone disregarding that will receive a warning. Repeat offenders will be given section bans.

This is in order to streamline appeals/requests and to not make them a shit fest that people don't want to touch. ~ PAS

---Ban Request Details:---

Use this template when posting a ban request:


Your byond account:
Your character name:
Their character name:
Their byond account(optional, but useful if you can provide it):
Server and time:
Logs and/or screenshots:
Description of what happened:
Why they should be banned:


Ban Request section rules:

1. Global Forum rules apply
2. If you are not an admin or directly involved with the ban request(You are the one being ban requested, you saw what happened, you were his victim, etc.) then do not post in the ban request
3. Use the template. Failure to use the template for a ban request will result in the ban request being disregarded until the post is fixed with template included.
4. No image macros, reaction images, memes or videos anywhere in FNR. Any media posted should be screenshots or other evidence directly related to the thread.
5. Try to keep your ban request calm, concise and properly formatted. No one wants to read a wall of text, or an angry rage post.
6. If a thread goes for a month with no activity it will be resolved. If you don't want your thread to go unresolved because of a lack of response then notify admins for a response.

Re: Ban Request section rules (READ BEFORE POSTING)

Posted: Sat Aug 09, 2014 2:31 am
by MrStonedOne
Given that some people have decided that the steno rules are free to be ignored; I've decided to up the ante so the speak.

Repetitive ignoring of steno rules will lead to your FNR posting privileges being revoked until further notice

Re: Ban Request section rules (READ BEFORE POSTING)

Posted: Fri Jan 09, 2015 1:31 am
by Timbrewolf
THE AN0N3 AMENDMENT IS IN EFFECT

Adding to/adjusting the definitions so that players can post in a thread regarding something they weren't involved in, IF IT IS TO BRING UP/POINT TO/HIGHLIGHT a rule, precedent, or piece of evidence that was missed that is relevant to the situation.

This does NOT include:
"This happened to me once and I didn't get banned for it" or the reverse "This happened to me once and I got banned for it."
"My opinion is…" or "I feel like…"

This WOULD cover:
"Rule 3 says…"
"These admins have always allowed…"
"Actually in the logs it says…"

This would allow players who are invested in the rules, have the experience, and can conduct themselves well to advocate in threads.

Re: Ban Request section rules (READ BEFORE POSTING)

Posted: Fri Dec 04, 2015 1:51 pm
by peoplearestrange
Bump to reiterate anon3 amendment being still in effect.

Re: Ban Request section rules (READ BEFORE POSTING)

Posted: Tue Feb 28, 2017 1:31 am
by MrStonedOne
New rules regarding the use of public logs in ban appeals, ban requests (if ever re-opened) and admin complaints:
  • The content of line must not be modified in any way.
    • This does not apply to adding context (as long as its clear that its added and not part of the original log)
    • Likewise, you are allowed to add formatting or emphasis as long as it does not appear deceptive
  • Any omissions of in between lines must be clearly marked in-line to the logs along with a brief description giving a rough amount of the lines removed, what they contained, and why they were removed
    • -snip-(500 lines of the clown slipping the hos in the other room removed for being irrelevant)
  • You must link to the log file you got the logs from to make it easier to validate the context
  • Air on the side of good faith, Its better to include too many context lines then not enough lines context lines
  • Expect onlookers to assume bad faith. If you omit details that are later deemed to be important people will assume you did it intentionally. This means doing due diligence when reviewing the logs for related or relevant bits.