(Sorry, right now I can’t read ALL the suggestions above but just want to throw mine here:)
How about giving some (more) responsibilities to the commanders? Wait, I don’t want to be polemic here, these are my ideas:
If you’re in a squad
- As you try to place a blueprint, the commander must confirm (like a yes/no join party question) its placement.
- Everyone can build on commander-allowed placed blueprints, being on squad or not.
If you’re not in a squad
- You can place whichever blueprints wherever and whenever you want.
- People can only build on a blueprint placed by someone not in a squad if they’re not in a squad either. If they want to build on that blueprint they’ll have to leave their squad (and then join again if it’s the case).
Why this would be good?
Commanders are there to command and organize. Ok, we know that much of this concept at WvW is sometimes applied as a pointless zerg magnet, even more after the 300g announcement. Still, they must have some control on how siege plays on certain attack/defense scene. With a commander restriction on what can be built on that battle scene things will probably go more as intended by the commander.
But most people aren’t in a squad, they’ll continue to place blueprints and, since most people aren’t on squads, everyone will build. What gives?
As I understand it, people go on zergs for two reasons:
- Protection, after all you can’t face an enemy zerg alone.
- Strategy, they trust someone (the commander if one is present) is creating something worth doing.
And it’s just too easy to do it. You join a zerg, maybe go intelligently as the group approaches things or maybe YOLO it and do your thing alone (probably dying in the process). I believe that, with the commander having more control on how things go inside his/her squad, it’ll make people want to join the squad. After all, things are actually managed there.
That said, let’s pretend this was implemented:
- Commanders start to build squads that place and build only intended siege pieces.
- In time, it’ll be known that Commanders actually control how attack/defense siege strategies go.
- People joining WvW worried about winning it will probably follow commanders zergs as usual. Blueprint placed? They will be “safe” from accidently buiding troll siege blueprints if they’re on commanders squads. If they’re not in squads they’ll eventually learn they should be on one by /map chat or game guides. If even then they can’t figure that out, well – sorry but that’s too clueless for WvW IMHO.
- If the above is confirmed, people not in a squad will see that most people don’’t build their siege blueprints, since most are on squads.
- Siege trolls will be there and still placing blueprints, but the people who actually are with the commander and following the commander strategy won’t build it because they can’t – unless they actively leave the squad.
Ok, I know this would demand a lot of new stuff, but in my honest opinion: it’s what being a Commander is about. If a Commander can’t control how siege is placed on attack/defense then I think it’s really a (now colorful) dorito on the map being a zerg magnet. Good commanders deal with this lack of control and make things happen, but kinda hard for them sometimes.
I really think there must be some way to Commanders have some control on siege placement (and no, I don’t have a tag myself, but I trust 70% of the commanders I’ve met so far).