Kutjevo-Refinery, playing as Runner, All slots filled, everyone fully evoed, It's 12:25 and marines finally drop. Queen decides to drop the ovi and go to the frontline. Marines are too pussy to push together so we hold them at FOB and begin fighting. Then we get these messages pop up
457c5f9f771a0245e3605928aa389649.jpg
3698355681d17cf5c62212237f149131.jpg
Followed by
a0a153ad6f94b49ef2adc505c38448c3.png
From this point, the Queen is forced to fall back to Botany, allowing marines to push out,recover corpses, intel and build up their cades
However, the Marines do not push far enough, and so, the Queen eventually pushes out and starts taking out the marines.
The Marines were at a slight disadvantage, but nothing the specs, smargunners and SLs couldn't handle should they coordinate. Staff decided to step in for some reason and threaten us with Queen Mother Intervention, instead of marking it as proper Xenomorph response, and IC behaviour. Yet they don't care about Marines metaing Tac shotties on Prison, marking such reports as IC issue, neither do they seem to moderate Shotgun juggling, which obviously bypasses the intended use of shotguns and makes them a machinegunning T3 obliterating weapon of destruction.
Instead, when Xenos are at an advantage, show competent cohension and assault the FOB with proper, intended features, suddenly we are stepping out of our boundries ???
Grimreaper followed up by stating that
d2b9b7d2683c1dc69f9e251c2845b1bf.jpg
As if Marines blarting out "Bitch", "Xenos Mad" or breaking into hive to PB the helpless Larvas is sportmanlike, but you don't see staff calling them sportsmanlike.
CM-13 is fun, and I feel the thing holding the game down is the fact Staff are trying to moderate the game flow, sure, they can compensate marines or xenos if the opposing side is obviously abusing some kind of game-breaking bug, but trying to stop Xenos from playing optimally while marking Marines breaking the game as an IC issue is something of a bias.
And before you say this is a #StaffReports Deal, Grimreaper did not step in in any way, so I don't think there's anything to report there. Could be wrong.