Jump to content

Rookieblue

Retired Staff
  • Posts

    2,231
  • Joined

  • Last visited

  • Days Won

    32

Everything posted by Rookieblue

  1. Moved to correct location. Not knowing a rule is not a valid defense to breaking it. The MOTD literally pops up every time you log into the server, and it's your responsibility to be aware of any rules that apply to a job you're playing on.
  2. Denied To utilize the generators, tesla gates, or other objects you must succeed in a roll supervised by a staff member. Pushing these buttons outside of these instances constitutes FailRP. Additionally, only CI and Foundation personnel are authorize to press those buttons, which would've been explained to you had you complied with the roll requirements. This warning is being upheld.
  3. Denied Based on the testimony provided I am upholding this warning. As SCP 106 it is impossible to accidentally no-clip into the area where GENSEC personnel are stationed. To accidentally go into that area you need to be in the D-Block Hallway, which is also a restricted area where 106 can not enter. SCP 106, 173, and 343 are moderated more strictly than other SCPs due to their SWEPs being more likely to be used to minge. Based on these factors, I am denying this appeal.
  4. Denied Based on the testimony and lack of evidence provided refuting the validity of the warning I am denying this appeal. Staff members have the responsibility to handle incidents that occur in game based on their observations, server logs, and video evidence. A staff member observations, whether recorded or not, is sufficient evidence to back a warning being issued unless other evidence contradicts these observations, or proves them false.
  5. Where in D-Block where you when you teleported in?
  6. Enough. Further arguing will result in this report being locked and forum warnings being issued.
  7. @NetworkParadox You need to include your steam ID on the appeal so we can locate the warning.
  8. Accepted Thank you for the report. All misconduct with the exception of the mass racism had already been addressed by in game staff. This player has now received a warning and permanent ban from our server for mass racism.
  9. Accepted Thank you for the report, after reviewing the evidence provided and in game logs I've made the following decision. 1) Going into Lower D-Block as LCPL As previously stated in a prior player report, it is NOT against the MOTD, nor the current GENSEC SOP for GENSEC personnel to simply enter lower D-Block. As such no action will be taken on this allegation. 2) Broke NLR Multiple Times This player broke NLR on three occasions per server logs, and will receive a warning this misconduct. 3) Not Listening to CoC No evidence was provided to support this allegation, so no action is being taken. 4) Said GENSEC is his minge job Confirmed via video and server logs. Based on his statements I have removed his GENSEC whitelists and blacklisted him from GENSEC Trainee.
  10. Though we do appreciate the apology.
  11. Warnings should remain permanent. They are a record of past misconduct on the various servers. Warnings do not affect players what so ever unless you accumulate a lot of them. We have staff members across the community that have gathered a decent amount of warnings, but if they're old and haven't been issued recently, they aren't considered an issue. PoliceRP was the only server that had a system where old warnings could be removed from someone's record, and that has since been shut down. Additionally, as October stated, it also helps staff members track patterns of misconduct for certain offenses. For example: Player minges on SCP 066 and breaks out SCPs. They're warned for their misconduct and kicked off the job. A week later they hop on SCP 173 and exploit the SWEP, and are again warned for their misconduct. Another week later they minge on SCP 106 and are warned. Me, as a SMT member who reviews all warnings and bans issued on SCP daily, will see that this player has a pattern of misconduct on SCPs, using them to breach other SCPs or abuse SWEPs. I will take that into consideration and decide whether to blacklist the player from the SCPs he's had misconduct on to prevent further issues.
  12. Noted! We have reviewed this issue with our servers and we will be working hard to fix it ASAP! Please allow up to a week for any bug fixes to occur as we go on a first come first serve basis. Thank you!
  13. If you have the authority to blacklist, but don't have access, this is more of a bug report.
  14. Denied Racism and homophobic slurs are not tolerated on this server, nor this community. The ban will remain in place.
  15. Denied While player poaching is unacceptable in this community, there isn't enough evidence connecting the offending discord account with the reported Steam ID.
  16. How did you connect this person's discord profile with their steam ID?
  17. Accepted After reviewing the evidence and testimony provided I do not believe anything had occurred that rose to the level of a warning for staff disrespect. Simply asking for a higher ranking moderator is not disrespectful in and of itself, nor is a player disagreeing with a staff member inherently disrespectful. However, it is expected that players not engage in arguments with staff members after they've rendered a decision, rather if they disagree with a decision they should make a staff report on the forums, or otherwise request clarification about a rule. On the topic of RP stuff, the only thing mandated by the MOTD are SCP adverts informing players of the status of an ongoing breach attempt. It is NOT required to engage in specific /me actions during roll offs per the MOTD. However, if a branch's SOP does include this requirement, it would then be required. Even though it's not required, it is good form and sportsmanship to engage in /me acts as it increases RP involvement, as well as informs the breaching SCP of what is going on. To have your warn removed, go to the "Bans" Section at the top of the forums, navigate to your profile, find the warning for this appeal, and for the reason on the appeal, link this post.
  18. Denied The appellate clearly and admittedly engaged in disrespectful behavior targeting a branch.
  19. I believe I was the one that issued this blacklist. I blacklisted this individual from SCP 106 after he was warned for using the SCP 106 SWEP to glitch into the staff room. Given the distance of the staff room from the playable map, this was a flagrant violation of the rule: You can only teleport through doors and walls, not open space (DO NOT GO THROUGH WALLS TO PLACES OUTSIDE THE FOUNDATION, INCLUDING STAFF ROOMS. BE REASONABLE WITH HOW FAR YOU GO IN THE WALLS). Additionally, this is not the first offense of this type for the individual, as he was also warned for abusing SCP 173's SWEP 4 days prior. Based on the facts provided and the continued misconduct on SCPs that have easily abused SWEPs I made the decision to blacklist him from SCPs 106, 173. and 343, the three SCPs that have SWEPs capable of being exploited and abused in the manner Auryz has a history of doing. As these SCPs are commonly abused, there is a very small tolerance, in most cases, a single free pass, where exploiting a SWEP from one of these SCPs will not result in a blacklist unless it was a significant event. Two, however, shows that Auryz did not learn from the second chance he was given previously.
  20. Could always call staff to handle D-Class spawning props, or take screenshots and file a player report if staff are unavailable.
  21. This warning and ban was put in place regarding this player report: Based on the evidence provided, confirmed via server logs, as well as the fact this constituted mass racism, I issued a permanent ban consistent with the guidelines in place in the staff handbook.
×
×
  • Create New...