Warning Appeal - Fringbean

[[GL] Fryingpan36]

Your In-game Name: Fringbean/Change

Your SteamID: STEAM_0:1:485639549

The admin's name in-game: CoolCaz

What warning did you receive: Power Gaming

When did you receive this warning: 10/17/2021

Please give a description of the situation that led to the warning: Flagging onto D-class.

Why do you think this warn was false: "Switching between combat jobs on a branch after dying to avoid NLR timers" is the reason for the warning although logs say different (NLR was waited)

Evidence the warning is false: https://medal.tv/clips/68486905/d1337x3L6rel?invite=cr-MSxOcEgsMTU2NTIzNjEs (its just logs) 

[Some Weeb]

+support

Skill issue. 

[Flixy]

+Support

[J0LT]

-/+ until full thing is heard

NLR does not just mean the timer. the rule was implemented so that if people died on CI/MTF during a CI raid, they wouldnt go on dclass on target the apposing branch

[Sprink]

-Support

Just because you waited your NLR doesn't mean you didn't still hop onto d-class to kill Security and MTF after you died in the raid.

This has been stated as a no no at multiple CI, MTF, and Command Meetings.

[Georgie_]

2 minutes ago, Sprink said:

-Support

Just because you waited your NLR doesn't mean you didn't still hop onto d-class to kill Security and MTF after you died in the raid.

This has been stated as a no no at multiple CI, MTF, and Command Meetings.

yee

-Support

[Coolcaz11]

Not gonna give a + or - support since, well, you know lol

The reason why I issued the warn was because he did hop onto the D-Class job after being killed during a CI raid, and even though his voiced intention was that he 'just wanted to go to HCZ as D-Class' he did still hop onto another job after dying in a raid while the raid was still going on, and fought foundation personnel. As it says in the motd, "Switching to different branches or SCPs to target opposing branches after being killed/during a raid." 

Again, what his true intentions were I do not know, but when I was taking the sit, it was clear that he did hop onto D-Class after dying in a CI Raid, and attacked Foundation personnel, while the CI raid was still going on. If the CI raid was over, and then he did it I wouldn't have handed the warn obviously, or if he was just chilling/running by on D-Class, sadly that wasn't the case. As a long-time member of the community, and as a 2LT in CI, he should have known better...

Nonetheless, if the higher powers wish to remove his warn, go for it, but the warn is justifiable for the circumstances in my opinion.

[Piller]

7 minutes ago, Coolcaz11 said:

Not gonna give a + or - support since, well, you know lol

The reason why I issued the warn was because he did hop onto the D-Class job after being killed during a CI raid, and even though his voiced intention was that he 'just wanted to go to HCZ as D-Class' he did still hop onto another job after dying in a raid while the raid was still going on, and fought foundation personnel. As it says in the motd, "Switching to different branches or SCPs to target opposing branches after being killed/during a raid." 

Again, what his true intentions were I do not know, but when I was taking the sit, it was clear that he did hop onto D-Class after dying in a CI Raid, and attacked Foundation personnel, while the CI raid was still going on. If the CI raid was over, and then he did it I wouldn't have handed the warn obviously, or if he was just chilling/running by on D-Class, sadly that wasn't the case. As a long-time member of the community, and as a 2LT in CI, he should have known better...

Nonetheless, if the higher powers wish to remove his warn, go for it, but the warn is justifiable for the circumstances in my opinion.

I agree with Coolcaz.

-Support

[ItzGray]

34 minutes ago, Sprink said:

-Support

Just because you waited your NLR doesn't mean you didn't still hop onto d-class to kill Security and MTF after you died in the raid.

This has been stated as a no no at multiple CI, MTF, and Command Meetings.

 

[Chief_]

1 hour ago, Coolcaz11 said:

Not gonna give a + or - support since, well, you know lol

The reason why I issued the warn was because he did hop onto the D-Class job after being killed during a CI raid, and even though his voiced intention was that he 'just wanted to go to HCZ as D-Class' he did still hop onto another job after dying in a raid while the raid was still going on, and fought foundation personnel. As it says in the motd, "Switching to different branches or SCPs to target opposing branches after being killed/during a raid." 

Again, what his true intentions were I do not know, but when I was taking the sit, it was clear that he did hop onto D-Class after dying in a CI Raid, and attacked Foundation personnel, while the CI raid was still going on. If the CI raid was over, and then he did it I wouldn't have handed the warn obviously, or if he was just chilling/running by on D-Class, sadly that wasn't the case. As a long-time member of the community, and as a 2LT in CI, he should have known better...

Nonetheless, if the higher powers wish to remove his warn, go for it, but the warn is justifiable for the circumstances in my opinion.

 

58 minutes ago, Pillercat said:

I agree with Coolcaz.

-Support

 

[[GL] Fryingpan36]

1 hour ago, Sprink said:

-Support

Just because you waited your NLR doesn't mean you didn't still hop onto d-class to kill Security and MTF after you died in the raid.

This has been stated as a no no at multiple CI, MTF, and Command Meetings.

As shown in the logs the security was the one who started the combat between me and him, when I flagged onto D class. I was not passed the red line and had no intention of attacking security until he had falsely attacked me. Even if I had the intention to attack security I had still waited my NLR making it a False warning.

Edited October 19, 2021 by [GL] Fryingpan36

[Piller]

21 minutes ago, [GL] Fryingpan36 said:

As shown in the logs the security was the one who started the combat between me and him, when I flagged onto D class. I was not passed the red line and had no intention of attacking security until he had falsely attacked me. Even if I had the intention to attack security I had still waited my NLR making it a False warning.

Do you have a clip of that? It could easily be that you shot at security, missed, and they hit you first, thus (as far as the logs can tell) initiating combat.

[Sprink]

44 minutes ago, [GL] Fryingpan36 said:

As shown in the logs the security was the one who started the combat between me and him, when I flagged onto D class. I was not passed the red line and had no intention of attacking security until he had falsely attacked me. Even if I had the intention to attack security I had still waited my NLR making it a False warning.

You were over the line when the combat happened so obviously we have to shoot you. You had every intention to kill Security.

[Some Weeb]

I still think +Support 

They instigated combat with him in the rules it is against them to flag on for the purposes of killing them so it makes not sense for this warn to be here. 

Edited October 19, 2021 by Some Weeb

[Coolcaz11]

Let's try to keep arguing to a minimum please.

I don't want this appeal post to become muddled with back to forth, so before anything blows up, if you wish to argue, please resolve it in DMs. 

My last comment on this is the warn was *not* for trying to slip past NLR, but because Fring had hopped onto a D-Class job and got engaged in combat with an opposing branch while the same CI raid that he was involved in the previous life was still going on.

If more context, clarification, or whatever else is needed, please feel free to DM me and I will do my best to fill in on what I could tell at the time when I took the sit. Besides that, try to keep this to + or - Support, along with own thoughts and whatever else you wish to post, but please don't post something if you know it's going to incite argument in this thread. Keep it to DMs!

One final note, do NOT harass anyone who was in this report in DMs, if I catch wind of even the smallest harassment going on through DMs or other means, I'ma whoop somebody's ass. Thank you!

Man, colored text is fun

[ShadowPL]

5 hours ago, Sprink said:

-Support

Just because you waited your NLR doesn't mean you didn't still hop onto d-class to kill Security and MTF after you died in the raid.

This has been stated as a no no at multiple CI, MTF, and Command Meetings.

 

[Average Pipebomb enjoyer]

5 hours ago, Sprink said:

-Support

Just because you waited your NLR doesn't mean you didn't still hop onto d-class to kill Security and MTF after you died in the raid.

This has been stated as a no no at multiple CI, MTF, and Command Meetings.

 

[Sponge The Great]

5 hours ago, Sprink said:

-Support

Just because you waited your NLR doesn't mean you didn't still hop onto d-class to kill Security and MTF after you died in the raid.

This has been stated as a no no at multiple CI, MTF, and Command Meetings.

 

[FBI-01]

7 hours ago, Coolcaz11 said:

Let's try to keep arguing to a minimum please.

I don't want this appeal post to become muddled with back to forth, so before anything blows up, if you wish to argue, please resolve it in DMs. 

My last comment on this is the warn was *not* for trying to slip past NLR, but because Fring had hopped onto a D-Class job and got engaged in combat with an opposing branch while the same CI raid that he was involved in the previous life was still going on.

If more context, clarification, or whatever else is needed, please feel free to DM me and I will do my best to fill in on what I could tell at the time when I took the sit. Besides that, try to keep this to + or - Support, along with own thoughts and whatever else you wish to post, but please don't post something if you know it's going to incite argument in this thread. Keep it to DMs!

One final note, do NOT harass anyone who was in this report in DMs, if I catch wind of even the smallest harassment going on through DMs or other means, I'ma whoop somebody's ass. Thank you!

Man, colored text is fun

-Support 

Edited October 19, 2021 by FBI-01

[that one dude with the long name]

15 hours ago, Sprink said:

-Support

Just because you waited your NLR doesn't mean you didn't still hop onto d-class to kill Security and MTF after you died in the raid.

This has been stated as a no no at multiple CI, MTF, and Command Meetings.

 

[Phillers]

The whole reason that rule was added was *because* CI/MTF would immediately hop onto D-Class after dying in a raid to get back at the other party.
From what I can read here, that's exactly what you did.

-Support.

[Noah Lee]

On 10/18/2021 at 9:14 PM, Sprink said:

-Support

Just because you waited your NLR doesn't mean you didn't still hop onto d-class to kill Security and MTF after you died in the raid.

This has been stated as a no no at multiple CI, MTF, and Command Meetings.

 

[Rektify]

On 10/18/2021 at 6:29 PM, Coolcaz11 said:

The reason why I issued the warn was because he did hop onto the D-Class job after being killed during a CI raid, and even though his voiced intention was that he 'just wanted to go to HCZ as D-Class' he did still hop onto another job after dying in a raid while the raid was still going on, and fought foundation personnel. As it says in the motd, "Switching to different branches or SCPs to target opposing branches after being killed/during a raid." 

Again, what his true intentions were I do not know, but when I was taking the sit, it was clear that he did hop onto D-Class after dying in a CI Raid, and attacked Foundation personnel, while the CI raid was still going on. If the CI raid was over, and then he did it I wouldn't have handed the warn obviously, or if he was just chilling/running by on D-Class, sadly that wasn't the case. As a long-time member of the community, and as a 2LT in CI, he should have known better...

Nonetheless, if the higher powers wish to remove his warn, go for it, but the warn is justifiable for the circumstances in my opinion.

 

[Rektify]

Denied