Guild Wars 2

Since we know who built it, we know who to punish if it’s troll siege. Thus, the timer is no longer necessary. Also, we could allow the guild that built it to set it to self-destruct if they really need to remove it.

Since it’s not easy to create, it’s very unlikely that anyone will troll with it. If they do, they can be stopped easily and won’t be able to troll again until they build another guild.

Siege timers are there to prevent a siege limit from being hit on a map.A guild could still troll with tons of guild siege to hit the limit.

Caedmon.6798:

Siege timers are there to prevent a siege limit from being hit on a map.A guild could still troll with tons of guild siege to hit the limit.

And siege limit is there to prevent anet from having to do any work.

If a guild does that, it will be a simple matter to either forcibly disband them or punish the users in question. Also, it would take a huge amount of resources for them to make all of that siege and days to build it.

Basically, trolling would be very hard to do and impossible to do more than once or twice a year without a dozen people all working very hard just to troll.

Sviel.7493:

If a guild does that, it will be a simple matter to either forcibly disband them or punish the users in question. Also, it would take a huge amount of resources for them to make all of that siege and days to build it.

Basically, trolling would be very hard to do and impossible to do more than once or twice a year without a dozen people all working very hard just to troll.

Lol you’re kidding, right?

Heck, I’ve sieged capped a map on my own many times (and not on purpose).

It’s not as easy to do when you have to build all the siege via scribing and let it sit in a pipeline for 24 hours before it becomes usable. In order to siege cap a single keep, it would take more than a month—not counting the time or gold needed to even get the scribe leveled.