Guild Wars 2

I don’t think allowing players to deconstruct siege equipment is the answer, as it will allow trolls/griefers to deconstruct legitimate equipment. However, I do think that setting a minimum level on siege construction may help…perhaps lvl 30+?

It does suck that a few people trolling spoils it for everybody else. Kind of like how the power orbs were removed due to the exploits/hacking. Hopefully ANet can do something about the siege caps without going to that extreme.

TwoBit.5903:

Simple fixes to address siege sabotage:

• Remove mapwide siege cap
• Section off the map and give each section its own siege cap
• Limit the construction of flame rams to gates, and up to 3-4 per gate.

These are some great suggestions. Definitely agree with limiting the construction of flame rams to gates only, as well as each section having its own siege cap.

What is ‘Siege Cap’ing?
It is when a player builds a ridiculous amount of siege equipment (usually flame rams) in useless places. This makes your team reach the siege cap a lot quicker than it would take in normal play. This can be done by an opposing team, transferring a player to your server, builds a bunch of flame rams in random places, using up your supplies and stopping you from deploying sieges. It could also be done by a random troll on your server.

Impact:
If a team is Siege Capped, it severely limits that team’s ability to deploy defensive siege equipment to fend off an opposing team’s attack. Likewise, it also severely limits the impacted team’s ability to deploy offensive siege equipment to attack towers/keeps/etc.

Comments:
Please take a look at the screenshots I have attached here to see what I mean. It is frustrating to mount any kind of offensive/defensive effort when you cannot deploy any siege equipments…meanwhile, you have 10+ flame rams sitting along your keep in random places.

I have seen this done since release and nothing has been done. I don’t know how to fix this issue, but I’m hoping that by raising awareness for this issue, we can:
1. Bring more attention to ANET regarding this issue.
2. Get a discussion going on how to fix it.