Some major problems that most people don’t know about because it hasn’t happened to them. Please bump this thread by inputting feedback so this is fixed.
Eternal Battleground
Map Siege Cap – Some servers can’t even build rams to take towers or siege to defend what they have because the entire map is siege capped for the server. People are putting/building TOO much siege in random places and can’t be stopped from doing so.
My suggestions for the solution of population/siege cap in EB:
Don’t count the player/siege count built in the jumping puzzle.
Destroy unmanned siege OUTSIDE Camp/Towers/Keeps/Castle radius after 15 min of unmanned.
Give the ability for players who SET the siege to because to also destroy the siege.
Jumping Puzzle – I am not sure if EB JP population is linked to EB or not, but if it is then I’m sure the siege is too. Which is doing 2 things: Taking up player count in EB thus adding a queue to a WvW map & people building siege in the jumping puzzle contributes to the siege cap. One major problem is some guilds, mainly PVE guilds, taking a ton of members to ‘camp’ the jumping puzzle for fun, which is fine, but it hurts the server when they do this.
Solution: Unlink the JP from EB if it does count toward the population count.
Upgrades – Anyone can upgrade places owned by their server. Which allows trolls and bad (uninformed) players to queue upgrades thus wasting a ton of supply which in some situations makes it so the server loses that place. For example: A server having the Castle, Reinforced with 1500 supply, no camps, and is being pushed really hard. They are trying to bunker down and hold it with the supply in the castle long enough for reinforcements to come (primetime to end for the opposing server) or for players to log in. If a random person were to queue Merchents or Fortify, that would drain the entire supply count out of the Castle which makes it a lot easier for the opposing server to cap. (Spies/Alternate accounts can do this and it is impossible to find out who upgraded it too).
Suggestions: (Not really sure how to fix this)
Only allow Commanders to upgrade or the Guild that claimed it.
Random Siege Dropping
Trolls/Spies often drop siege down to siege cap certain places/map siege cap or to drain supply from zergs/towers/keeps/castle.
Uninformed players also do this because they are trying to help out and the problem is players will actually build it, thinking their commander placed it.
Solution: Allow everyone to see the NAME of the player that placed the siege down so they can either be informed on why they shouldn’t have done that//reported.
If you have any other suggestions please note them below.
S(KILL) Gametypes > WvW & sPVP