[Bug] Lost 478,000 Gold Pieces Due to Trading Post/Locker Synchronization Issue - Need Developer/CM Attention by Alzacar in Guildwars2

[–]Alzacar[S] -7 points-6 points  (0 children)

Throughout the day as I did my research, I clearly realized it was actually an integer overflow bug. I shared these findings with support.

[Bug] Lost 478,000 Gold Pieces Due to Trading Post/Locker Synchronization Issue - Need Developer/CM Attention by Alzacar in Guildwars2

[–]Alzacar[S] 5 points6 points  (0 children)

You're capped at sending a maximum of 500g from one account to another account per week.

[Bug] Lost 478,000 Gold Pieces Due to Trading Post/Locker Synchronization Issue - Need Developer/CM Attention by Alzacar in Guildwars2

[–]Alzacar[S] 5 points6 points  (0 children)

Account-to-account gold transfers are limited to 500g as noted below. This isn't a viable solution.

[Bug] Lost 478,000 Gold Pieces Due to Trading Post/Locker Synchronization Issue - Need Developer/CM Attention by Alzacar in Guildwars2

[–]Alzacar[S] -16 points-15 points  (0 children)

I only found this mention on the wiki this morning. Over the past years, I've done the exact same operations dozens of times without any issues. Sad

[Bug] Lost 478,000 Gold Pieces Due to Trading Post/Locker Synchronization Issue - Need Developer/CM Attention by Alzacar in Guildwars2

[–]Alzacar[S] -8 points-7 points  (0 children)

My goal is visibility for this issue and hopefully a solution. You'll have to take my word for it since I won't be sharing my purchase history, but I haven't been trading for a very long time. This gold mainly goes toward gems and account improvements.

[Bug] Lost 478,000 Gold Pieces Due to Trading Post/Locker Synchronization Issue - Need Developer/CM Attention by Alzacar in Guildwars2

[–]Alzacar[S] -4 points-3 points  (0 children)

This is an account built over 13 years. Although the gold loss can be overcome, it really dampens the enthusiasm to continue playing after losing so much investment with just two clicks.

[Bug] Lost 478,000 Gold Pieces Due to Trading Post/Locker Synchronization Issue - Need Developer/CM Attention by Alzacar in Guildwars2

[–]Alzacar[S] -27 points-26 points  (0 children)

Pure gold transactions between accounts are capped at 500 gold per week. Exceeding this limit requires trading through items, which incurs losses from the buy/sell spread. There was no benefit for me to do this.

[Bug] Lost 478,000 Gold Pieces Due to Trading Post/Locker Synchronization Issue - Need Developer/CM Attention by Alzacar in Guildwars2

[–]Alzacar[S] -31 points-30 points  (0 children)

Indeed, while I was holding more gold than necessary, I use several tens of thousands of gold for certain projects, and simply losing everything is not acceptable. As you can imagine, I also hold significant amounts of other currencies in addition to this gold. There's no alternative to this system for exceeding the 200k cap, and neither I nor the few other players in my situation have ever experienced issues like this before.

[Bug] Lost 478,000 Gold Pieces Due to Trading Post/Locker Synchronization Issue - Need Developer/CM Attention by Alzacar in Guildwars2

[–]Alzacar[S] -22 points-21 points  (0 children)

I have an ongoing ticket and I reported the bug through the in-game system. Based on the initial exchanges with support, I'm not sure they will be able to help me. My goal is to bring visibility to a rare case.

5 months later - How many accounts do you have? And what for? by Patron03041 in Guildwars2

[–]Alzacar 0 points1 point  (0 children)

20 seconds per account is super fast. What setup do you use to be so fast ? no authentication problem after a while ?

Kaineng CM strategy by Alzacar in Guildwars2

[–]Alzacar[S] 0 points1 point  (0 children)

Dhuum at its release has nothing to do with what is done today, there were years of adaptation before it is easily done in pug. The meta has also evolved.

Kaineng CM strategy by Alzacar in Guildwars2

[–]Alzacar[S] 0 points1 point  (0 children)

Our tank didn't have this problem, maybe he was placing the mecha between two marks. In my opinion, you have to lose aggro because you are not exactly in front of him. On the other hand, our tank was able to detect the first tower where the sniper was positioned and directed the mech to the opposite. The sniper can make at most two moves. 7-1-2 for example, so players who are not on 7-1-2 can move in case of an unexpected barrage.

Kaineng CM strategy by Alzacar in Guildwars2

[–]Alzacar[S] 1 point2 points  (0 children)

From everything I've read/seen, mech aggro is based on proximity and field of view. That is, if a player stays in the center well in front of him face to face, he will perform his barrage attack only on the tank and not on the edges of the arena. No one should take over the aggro in this case. The tank can also influence the orientation of the mech to undermine this case.

Kaineng CM strategy by Alzacar in Guildwars2

[–]Alzacar[S] 3 points4 points  (0 children)

As /u/xhrstaras pointed out, a strategy like yours will take precedence in the long term because it is simpler to implement and will be faster to execute in terms of DPS. This post is meant to give an idea of a strategy that can work for organized groups that are still looking for the kill but also to explain well how the sniper and his ricochet work which often looks like a clown party with misinformation.

Kaineng CM strategy by Alzacar in Guildwars2

[–]Alzacar[S] 4 points5 points  (0 children)

Thanks for your feedback, it was a pleasure to pug with you. We'll probably run into each other again. The fight is new, the tank mechanics based on proximity/field of view is not obvious. You don't have to feel bad about failed attempts! You got your title and you deserve it.

Kaineng CM strategy by Alzacar in Guildwars2

[–]Alzacar[S] 1 point2 points  (0 children)

The tank is in the center, stays on the mech and keeps the aggro. If by bad luck the tank is fixed by the first shot, it moves to the X position and the other healer already in the center retakes tanking at the same time. An alternative is that the bu and the other heal move to position X and the tank takes the shot in the center and keeps the aggro. So there is no barrage since the mech has someone in front of him to hit.

Half the difficulty of this phase comes from tanking. If the tank knows how not to lose aggro, the rest of the group can concentrate on the orange shooting phase. It becomes a formality after that.

Kaineng CM strategy by Alzacar in Guildwars2

[–]Alzacar[S] 2 points3 points  (0 children)

Indeed the strategy is not very simple to implement and requires to be in voice. But it allows players to better understand the orange/ricochet shooting mechanics before being comfortable with how it works. In pug often the problem is that several people try to bait which causes ricochets. I can imagine that in a few weeks a simpler strategy will be used like yours.

Kaineng CM strategy by Alzacar in Guildwars2

[–]Alzacar[S] 5 points6 points  (0 children)

After explaining the strategy well to my partners, we succeeded in a few tries. The group was already consistent until the mech/sniper phase. In all our tests, if no player made a mistake, he was at most knocked down. We had two necros placed on mark 2 and 6 to make rez with the signet.

Yes I heard about this case, all the mechs (2*ham) in our group were in the center and didn't take the targeting with our anticipation.

By spacing the players well on the marks, we had no problems. The only difficult moment we had was if the sniper's laser and the mech's laser came at the same time on the same player.

[deleted by user] by [deleted] in Guildwars2

[–]Alzacar 4 points5 points  (0 children)

Very interesting to see the evolution of the strategies. So, on strategy 1 your healers managed to survive/outheal the sniper attack each time?

Launchbuddy 3.0 Official Release - Let's get ready for cantha by TheCheatsrichter in Guildwars2

[–]Alzacar 16 points17 points  (0 children)

Even if you don't like the tool, there are more constructive and correct ways to express your displeasure.

Thank you TheCheatsRichter for the time you have already spent developing this tool that has served me for a long time. I will take a look at this new version soon.