Siege camping is one of the main reasons people quit this game, It's about time.
Old players quit because of siege camping, new players leave because of Shagroth(s).
- It can instantly kill a fully equipped unit with 1 shot(whereas its true purpose is buildings, not units)
Although 1 shot kills are a high vulnerability, sieges are themselves even more vulnerable to these fully equipped units (and other sieges)
if they're not close to respawn points. Leaving the dictionary purpose of siege units aside, they are still needed. In a 9vs9 match on public, defending against 9 behemoths is not happening without siege. It would need an extent of coordination that goes very far beyond a rabid and another player with a blaze.
- "Use ranged weapons" If you are the sole person who can push for your team, you cannot do that as beast with ranged.
You are not supposed to push alone, although the old players that you've mentioned in your first line of course would like to be able to do so. If absolutely needed you can still hide behind a tree. But if your definition of pushing is to crush anyone who spawns from strongholds (of course to give room for summs to kill shields, harvester of noobs), so god be with us.
With my (human) viewpoints in mind, the only solution that I could see working would be a damage
reduction against siege if sac has been activated in a certain radius around respawn points. Against beast siege, I could see a damage reduction on behemoth hits working if the human unit is carrying a
demo pack. This needs to be of course tested and the % or # of reduction should be likely not the very same for both races.
Another solution could be to have caps on siege units, for exaple, maximum 1/3 of the team, unless team is below three players in total.
As far as I remember, there was a server that did that and it just led to sieges never available when one needed them.
Show Posts
that's enough.
. Since recording demos takes too much resources of my precious FPS, is there any other way I can follow up on this? Last time it happened at 13:54 PM (CET/UCT+1) on 27.07.2017 (Schnapszahl, prosit!), the console looked like this: 
.
