Guild Wars 2

Making siege throwable only by commanders: It’s an horrible idea since there are newbie players and guilds. Them having no idea about squads or tags should also be able to siege the nearest tower. It’s also punishing the poor little guilds. This situation also forces commanders to tag up. Half of commanders and most of guild raids doesn’t even use tags. I don’t even mention how many rams I used to fear people on borderlands garrison gate while defending enemy North Camp on my solo/duo runs.

Making siege throwable only by squads: This is only a little better than the previous one. There are various problems with it. First, there is a squad member limit and usually there is only 1 commander tagged up on entire map. Second, it forces people to actually join a squad to just drop one single ram. At lower rating servers it’s a miracle to find a commander on certain time periods. It punishes the lower populated and over populated servers both. Only acceptable for medium range and still not good since some trolls I know had commander tags anyway.

Exhaust: It’s only good if it triggers on the supply, not sieges. But still, non built sieges should not count on siege limit for it to work.

I still think voting on siege is best method. It both gives a sense of unity on community and doesn’t punish good people. If it’s hard to code, maybe being able to seeing the names of people on built siege might work too since it’ll allow us to report them.

I’ve discussed this issue many times with many people. These are the ideas we came up with back then;

Marking the siege: Basically any player will be able to rate a siege by right clicking the ally siege and giving a downvote or upvote. This way it either refreshes the uptime of that siege or reduce it. If too many players downvote a siege it’ll break down and return the supply it consumed to nearest tower or garrison. A player can only rate a siege once.

Downside: A large group of people, lets say a troll guild, can downvote entire defense of a structure, which is troublesome.

Marking the builder: when x amount of players downvotes a siege, builder of it is unable to build any siege for y amount of time. It’s can be either forgiving or punishing.

Downside: If too many people downvotes, lets say a commanders siege, it’d be bad. Like, very bad. Again, putting an upvote option for marked siege could solve the issue.

TLTR: Add a thumbs up on siege drop down menu after it’s built.

My transmuted whisperer staff of earth returned to it’s original state too. All I did was logging off. Fine transmutation stone and good looking staff were also disappeared. And there is the best part; When I tried to buy another whisperer staff with low level and low price, It looked like normal oak looking default staff after getting into my trade post inbox. Item visuals are probably bugged.