First off lets set the stage, every other squad from last sunday re scheduled to a day that works for each squad. The new admin forced this day without asking captains or advisers what they thought, maybe he asked but it would be news to me, with my efforts going dull on them we had to set up at a time the "new" admin setup, I guess dp is stepping down mid season, news to me. So this is like finding out you're in marshal law because pence is now president and you didn't realize trump died but you found out because you're in a new hell when you awoke and don't realize why.

About 20 minutes before the match the admin messages me and says "yall forfeiting?"
I respond with we have enough.
Red flag 1) chris used to brag about being able to be admin and not be on a squad so he wouldn't ever show biased in his decision, guess that mindset changed. Also hes not a captain but put himself in captains chat for our match and FD is have 5 members in the captains chat with the ref any myself.

As the match is about 5 minutes to start after we need a delay I communicate we are having issues getting our nt (uzo) to configure mumble. The ref responds oh well match is going to start in x minutes regardless. Not a red flag would just think if we actually wanted to play a legit match I could get FD to help with a delay we obviously doing what we can to play this match. But it's within the rules so you have to power forward and we did.

So match started and our nt can't hear us so I have to type to him (2 minutes into the game he can hear and is fixed)

At about the 22 minutes mark I setup a play outside the C1 building, we have 4 members at the top of KR in coord C2 out of vision. 3 inside C1 building in coord C1. The group inside C1 Building is seen and the enemy immediately retreats. After about 60 seconds of waiting I decide to switch it up and send the group to sit outside the building and for uzo to move further away for bait. I move the kr group from c2 to b2, and have the 3 around Tap building move down to the top of C2 to try and bait. I have uzo do a further bait to the east he gets all the way into D2 before getting specced.
Now we are playing down a man for 10 minutes, and the ref failed to notify the enemy of our position as per the rule states it would when a player gets specced.

here's where I'm going off of spec for this information so i'm sorry if I was wrong or misinformed.

The enemy retreats when they see us around minute 22 and they fall into stationary spots for this duration while this plays our over 4-5 different coords, but are just holding looking in our direction waiting to see a dot.
Shouldn't FD have gotten some kind of camp timer warning?
From the 4 people I talked to about my match (minutes after the match) they confirmed and confirmed again FD sat in their spots without moving, while I didn't have my team sit in the same coord specifically for this camp timer rule, we never went back to the same coord within the 2 minutes we actually have everyone but 2 people move the entire time.
Mind you at this time the score was only like a 10 kill lead at this time.

With 30 seconds to go in the match I told the ref we want an appeal and the response I got was "well you had all 7 in same coord when I specced uzo" Which was flase to begin with.

So with this appeal im basing a lot off of spec I just assumed FD was moving the entire time but if they were camping just more spread out they got nobody specced or warned for mirroring us.

9.3 The League Administrator or any other Head Staff who is present and not involved in the match will decide the result of the appeal

I don't know if any advisor was in watching our game (apollo I think was watching) but please review this and just let us know. I hope I was able to show how playing down one man for 10 minutes is grounds for an appeal.

I decided to post this in public and see if others can offer what they saw, or maybe the people who were communicating with me will want to shed some light on what they saw so whoever can review this can get more details, assuming they didn't watch the match.

Nobody fucking cares dude LOL

Didn't you get caught hacking?

1. I never asked "yall forfeiting?" I don't use "yall". I asked "How many players do you have?" just to see if the match would be happening or not or if we needed to reschedule.

2. As an admin I have just about every right to be in the chat as any other captain or staff member.

3. You used your delay and the timer ran out. Once that delay timer runs out the match is going to start regardless. You had 7 people in and the delay timer still had 3-4 mins left. Plenty of time to get things going.

4. Something you fail to understand is that every battle you went to a hiding spot and stayed there until we found you which means your camp timer always started way before we would have ever been considered "camping". Any time we found your hiding spot we would just move away to draw you out which gave us at least a 20-30 second window over you. Emp gave a 30 second warning on your remaining camp timer and as soon as we saw that in the captain's chat we immediately moved because we knew you would be moving. So that already nullifies our camp timer. The only time your camp timer hit 0 was when Uzo was specced. Which, again, we had the 20-30 second window and we engaged you in battle which means the "camp" is over.

5. Posts like this belong in the captain's forum but I know how much you like the attention and trying to rally the hate bandwagon.

I feel like this belongs in the captains forum

So when are we going to amend the rules to have this spoken "engagement" rule? rofl... Still a crock of shit that you're picking that leg to stand on. This league reminds me of beer pong and the 100s of different rules you have to remember just cause you're playing someone different.

Fact is, there were multiple people in spec that saw what they saw which was BOTH squads remaining in the same position throughout the entire camp timer. FD knew EXACTLY where NS was to begin with so this is hardly even a case of camping. Just a case of forcing a squad to sit in the same place or come out and die from lack of angles. How is that even remotely a fair/just rule?

1. I gave you a 10-minute delay, just following the rules man. I asked you maybe 5x over a 5-minute period and you didn't even respond once.

2. I gave you well over 2 minutes each time I initiated the camp timer.

3. Despite what Octavian and HellSpawn were saying, no one considers FD being spread out south of KR all the way to E1 to be camping. Why would that be considered camping?

4. I didn't announce your location because FD obviously knew you were at C1, hence them having 3 separate groups spread out watching that area.

If you didn't want to run into trouble with the camp timer, why did ya'll keep camping? Do yourself and the ref a favor in the future if you don't think you're camping, MOVE. If I can see all 7 of your players on my monitor, you're camping. Because one player was moving around acting as bait while the other 6 hid in buildings and behind a rock for 3+ minutes, you want to act like that isn't camping?

Come on man.

Sorry you got forced into playing Wednesday, but don't act like I wasn't as lenient as possible with the rules.

Maybe newer USL players like yourself wouldn't understand but camping has always been defined as hiding/holding a spot not engaged in battle with the enemy. Imagine if we used camp timers for squads that are fighting each other in a heated battle that is happening in the same coordinate for 2 minutes? Give me a break. It's such common sense that I literally can't think of any other way to simplify it.

They camped and we used a strategy that punished their playstyle. It's as simple as that. If you don't want to be punished for camping, then don't do it. Or do it better. Any other squad with USL experience would have done the same thing we did. Box them in and watch them drop.

But it wouldn't be true to manu's fashion in thinking logically therefore he posts it here seeking attention.

I was going to cover the whole "camp timer window" but champ hit it right on the head with the <b>"Any time we found your hiding spot we would just move away to draw you out which gave us at least a 20-30 second window over you."</b>

But anyways gg

wow champion corrupt here just like he's corrupt on poe and always gets the best loot
are you the living embodiment of atziri

Does POE have a Xur, no it doesn't. Come play destiny 2.

says the guy who got a fuckin 60ex belt -_-

"I guess dp is stepping down mid season, news to me. So this is like finding out you're in marshal law because pence is now president and you didn't realize trump died but you found out because you're in a new hell when you awoke and don't realize why."

LMFAO.

When's everyone coming to fortnite ?

Appeal granted

i got 2 of those, get it right nerd

From what I remember with old school back in the day camp timers...

We always used the "engagement rule" where camp timer was broken anytime a squad engaged another and that was pretty much understood to be hitting a few bullets or being within 2 coords.

However, that's not even an official rule so you can't really use that in an appeal request.


My interpretation of the rules according to how they are actually worded would be that a squad is camping anytime they do not move more than 2 coords in the span of 2 minutes - engagement doesn't matter. And I would go even further to imply that the whole entire squad must move more than 2 coords. If any member of the squad is within 2 coords of the same spot from the camp timer then they are violating it. A squad being spread out is still the same as camping bunched up. You can't move 1 player and cancel a camp.

Scenario that lead to uzo being specced involved No Stones camping, getting a camp timer...

FD then disengages but spreads out their guys so No Stones has no way to escape.
There was little to no movement once FD disengaged and resetup to block No Stones escapes. A camp timer should have been called on FD after they stayed 2 minutes in their setup.

FD then should have had to have each player move at least 2 coords or they would have been in violation of policy. They didn't even rush immediately after Uzo was specced. They cautiously approached. And there were definitely some players on FD that did even move 2 coords from where they were camping to engage No Stones.

For the camp timer and speccing Uzo decision to have been fair without FD losing a player shortly after as well, FD should have actually moved like going all way to F3 and then coming back or looping around KR. That's the intended movement for a squad that isn't camping when a camp timer is called.


The rules suck. Technically FD should have lost a player about 20-45 seconds after Uzo was specced. We need new rules.

I'd like to see an engagement clause put in that can break a camp timer.

As well as a rule that two camp timers cannot be going on at the same time, and the first camp timer is voided if another is called: i.e. when FD strategically camps to counter No Stones camping then FD gets a camp timer and No Stones would have been off the hook.

And another clause regarding each player having to move 2 coords.

Poor manu, received info from spec based on their interpretation of the rules when no one has complained once about it for so many seasons. I'm more interested in learning about how pence is now president but did not realize trump had died but found out later when you woke up to new hell but didn't realize why. https://i.kym-cdn.com/entries/icons/original/000/018/489/nick-young-confused-face-300x256-nqlyaa.jpg

I like your interpretation oct. Reminds me of someone stating that Cazzo Forge brought in 15-20 new players to the game and will be retained thanks to the zone but just so happens to not log on yesterday when there was 30+ people online.

Do you know why this camp timer was punished more so than any other situation? No one would camp at tap, a location isolated on the corner of the map where you have no leeway to transition to another safe location without getting punished hard. Now I understand why Kippa led that one game now. Makes sense. Rules are fine. Should focus on increasing peak pop(what is it now, like 10?) oct instead of blaming hellspawn for ruining the zone.

BTW, this is what I saw:

<b><u>https://i.imgur.com/e4HiNF6.jpg</u></b>

The two big circles are No Stones, the three little circles on the radar are Fwaming Dwagons.

Why would I spec FD for being spread out and out in the open, when NS moved to their spots first by a good bit (as everyone keeps saying, this means the timer starts on them sooner). Stayed in their spots far longer (timer never went away by staying so stationary for 2+ minutes). And they are clearly the ones trying to hide and camp, which is the point of the rule in my opinion: to discourage players from picking one spot on the map and sitting there.

FD tried to fight NS. NS ran into the building. FD disengaged because it's obviously a losing situation to charge in there. They shouldn't have to go all the way across from the map to start a camp timer. The point of the camp timer is to limit how much time the other team can sit idle in a building.

That's how I interpret the rule.

Simple fix to "FD then disengages but spreads out their guys so No Stones has no way to escape."

pick a better camping spot where you have more than 1 maybe 2 true outlets to escape. <b>And during the time we were disengaging and moving to 3 separate locations they remained in the same spot thus receiving the camp timer and spec.</b>

"They didn't even rush immediately after Uzo was specced. They cautiously approached."

Yet we still moved in.

The difference in so called "camping" from FD is that we weren't avoiding fighting we disengaged to get better angles as the camp timer for them was being placed. <b>And because they weren't moving while we were they got the spec.</b>

Your interpretations oct clearly help confuse manu, please keep it up as it's highly entertaining.

Should learn how to play to win instead of "lets just keep the score down and camp while we're down"

Agreed with sov its no wonder kippa shows up randomly and gets asked to lead for your team.