Guild Wars 2

Six or nothing. Preferably none, to fit how other charr styles tend to operate and given prior lore understanding of charr mammaries and clothing standards.

Hey Mo,

Thanks for giving us an update this early, even if it’s not the news we’d like to hear. Your honesty is appreciated.

I’ve got a quick question on the technical side of things: Has tooling been one of the pain points? Are Legendary Weapon systems difficult to modify for both developers and content creators?

I mostly ask because if the issue is something like this, where better tools need to be created first to enable rapid creation later, I believe the response from the community may end up being more reasonable. As it is, we’ve got nothing to go on. I personally trust this was considered very carefully and that you have very good reasons for making this choice, but most others will not see that and will leap to their own conclusions. Simply understanding some of the backing problems at a high level will give us more trust in the decisions we hear about without having to make additional promises.

Regardless, hope to hear more early communication like this in the future. Take care, and hope this doesn’t cause too big a firestorm for you folks.

Could have to do with a specific piece of equipment or trait, something that would either cause the server or all clients to perform unnecessary processing to handle. For example, if a boon keeps refreshing itself once every frame, that’s a server-side check that’s continually being performed.

Seems to me that part of the problem stems from lack of commander authentication and authorization.

Many of the proposed solutions would deliver more control to commanders to mitigate or reverse siege trolling behaviour. However, unless there is a way to verify that a commander is trusted to make decisions for the benefit of a server, all this does is open the door for more forms of specialized trolling available to commanders specifically.

The problem, then, is either directly dependent on a solution to the commander problem, or is one and the same as the commander problem. Without a solution for commanders, fixes for siege trolls will be greatly limited in success.

Keep in mind that one goal for the design team will probably be to minimize the amount of direct intervention required by ArenaNet staff. If siege trolls and commander authentication can be internally governed by each world’s community, then I believe the fix would be successful in the long term, and would scale naturally with the game.

This is our experience as well on Yak’s Bend.
Reddit Post from servers with similar experiences

Reviving this topic: Yak’s Bend seems to be missing its Sotzz. No-one has spotted him for quite a while, and several guilds have failed bounties because of it, and this was after over an hour of a full-sized guild scouring the entire map, before, during and after the bounty.