Guild Wars 2

hey all,

today it happened that we reached the siege cap for flame rams, while there were not even 100 flame rams on the map.
quote from GuildWars 2 wiki: "This map limit is explained by Mike Ferguson of ArenaNet as “basically anything that is not a ram counts towards one ‘limit’ for the purpose of this explanation and each team can have up to 100 of these types of weapons out at any time per map. Each team can also have up to 100 rams placed on a map.”

it is not the first time this has happened, but this is the first time I had seen it.
is it possible that this siege cap is bugged or something like that?

This has happened to us on SoR as well. There is some sort of bug with the cap numbers. There are instances where we are forced to man mode a gate because we can’t place anything down at all including rams and golems. It’s annoying.

Maybe it counts the animal rams as well.

Wouldn’t be the first time we see that confusion occuring in GG…

Sounds like your server has encountered the crappy tactic that is enemy players coming to your server and hiding siege so nobody on your team can build it

Most likely you’re being spy siege capped… which anet has no urgency to fix.

Simply limiting the amount a single player can lay down at one time on one map should be 1-3.

Commanders have unlimited.

Maybe make only siege dropped by Commanders in the keep refresh with view only.
If dropped by players they need a normal manual refresh.

Maybe tagging each siege with a name of who created it.

Problem solved.

We have been siege capped at Piken quite often the latest days.
It also has been busy, but it’s not like it has never been busy before.

It even gotten to the point where the other servers ‘mention’ we put up golems for the simplest doors… which are the only things you can still use when siege capped.

Some foul play could be at work.
Or a bug.
Or of course the simple fact it has been busy and crowded… but we had that worse and it occured less than.

Energetik.6471:

Simply limiting the amount a single player can lay down at one time on one map should be 1-3.

Commanders have unlimited.

Worst idea ever…

If rams are counted on their own, the very simple solution would be:

only let a ram be deployed at an enemy door itself.
Give an error message outside that radius, and if on your own door.

That way even if people put them down to annoy the team, they at least would be standing at enemy doors…

Ony works if rams are counted with no other siege than rams of course.

Player limit could work, but very often it’s the same players using several, and the ‘masses’ not putting much down.
Of course, this would also balance that out a bit

Iruwen.3164:

Energetik.6471:

Simply limiting the amount a single player can lay down at one time on one map should be 1-3.

Commanders have unlimited.

Worst idea ever…

it’s not so bad as an idea, it would be very very restricting on players who put down a lot of siege now.
But it might force others to use more siege as well for a change.

Or do you consider this tactic of wasting siege so the team gets siege-capped a valid tactic too?

No, it’s exploiting game mechanics. But we for example often have trainee commanders running who don’t have a book yet, that would hurt the gameplay a lot. It’s just replacing one evil with another.

Kimbald.2697:

only let a ram be deployed at an enemy door itself.

That’s what I’d do.

Iruwen.3164:

No, it’s exploiting game mechanics. But we for example often have trainee commanders running who don’t have a book yet, that would hurt the gameplay a lot. It’s just replacing one evil with another.

Kimbald.2697:

only let a ram be deployed at an enemy door itself.

That’s what I’d do.

I fully understand you on the ‘trainee’ commanders.
often people take up responsability in WvW in one form or another, organised or not.
Those are the ones who would feel such a limit of course.
Not the ones who never put down siege, and not the commanders… but those in the middle.