Jump to content

Coltable

Member
  • Posts

    1,321
  • Joined

  • Last visited

  • Days Won

    33

Everything posted by Coltable

  1. Okay i mean if thats true... thats kinda fucked lmao @stitch @Jackwebb1112
  2. Denied. The SCP-RP SMT has decided against adding this suggestion for performance reasons, the benefit to the server, or another unstated reason.
  3. Denied. The SCP-RP SMT has decided against adding this suggestion for performance reasons, the benefit to the server, or another unstated reason.
  4. Completed! This suggestion is now in the server
  5. Completed! This suggestion is now in the server
  6. Denied. The SCP-RP SMT has decided against adding this suggestion for performance reasons, the benefit to the server, or another unstated reason.
  7. Its a consequence to prevent players from abusing the "OH IM CRAZY IM GONNA STAND BEHIDE CI AND KILL THEM HA HA CRAZY" That sort of "Roleplay" as you've stated is totally fine but whats not okay is players who decide to abuse it and THOSE players are the ones who get on the KOS list.
  8. We either remove the ability for dclass to attack CI, or we keep the list, if you decide to attack the one branch whos trying to help you on the server then its on "you" the player to deal with the consequences of your decision be that being placed on a list or what ever it be, you made that happen nobody else. If you dont want to be placed on a kos list for the safety of CI personnel then don't kill them, easy fix.
  9. Denied. The SCP-RP SMT has decided against adding this suggestion for performance reasons, the benefit to the server, or another unstated reason.
  10. Denied. The SCP-RP SMT has decided against adding this suggestion for performance reasons, the benefit to the server, or another unstated reason.
  11. Due to how much rework would need to take place in adding a system such as "tank classes" myself and site-admin currently dont see it be hugely beneficial compared to the workload and setup. We may take another look at this suggestion in the future however.
  12. We're examining this bug! If we find a fix for this bug, or we find that it is unfixable with reasonable attempts, this post will be updated with an appropriate response.
  13. We're examining this bug! If we find a fix for this bug, or we find that it is unfixable with reasonable attempts, this post will be updated with an appropriate response.
  14. We're examining this bug! If we find a fix for this bug, or we find that it is unfixable with reasonable attempts, this post will be updated with an appropriate response.
  15. We're examining this bug! If we find a fix for this bug, or we find that it is unfixable with reasonable attempts, this post will be updated with an appropriate response.
  16. We're examining this bug! If we find a fix for this bug, or we find that it is unfixable with reasonable attempts, this post will be updated with an appropriate response.
  17. We're examining this bug! If we find a fix for this bug, or we find that it is unfixable with reasonable attempts, this post will be updated with an appropriate response.
×
×
  • Create New...