[REJECTED] Arcway WoW Error 132

[Echoman]

Hello,
I would like to make a compliment in connection with a serious PVE bug in Arcway.

Bug description: Nal'tira makes everyone crash when the spider pulls us to herself. The only one who did not crashed was me, 3 times.
Proof: https://cdn.discordapp.com/attachments/289850473085927424/470317198515240960/Screenshot_3.png [This happened 3 times in a row before we forfeited]
Opinion: It is very unfair to me and to everyone who has arcway keystone, because we automatically can declare it as depleted immediately when we receive it. I can even understand how Arcway is available for keystone while it has so serious bug. A PTR server would make sense, since the fixes made to various instances usually makes more bugs than it fixes.

I would like to require another keystone or to fix that bug and of course undeplet my keystone since it was not our failure.

Yours faithfully, Beszeda.

[Aralisha]

This is not a server problem, hundreds of Arcway keystones are done every day, we cannot and will not replace your keystone for a new one, if it's depleted simply rerun it, next time delete the cache folder before going in a dungeon and remake party


I'm the best Hunter, fight me

[Grazzia]

So that is an expected behavior of WoW in Arcway?

I made the screenshot, when I've crashed on 3rd time. Just Beszeda was who did not crashed, everyone else did.
That's true that there were many successful Arcway runs, but there were many with this WoW error too(sometimes just once, other times like on that keystone we stuck with it), it doesn't happen always but nowdays it seems to happen more often than it used to.

Also, if it is really about the cache folder(which has been deleted so many times for multiple reasons like WoW error on equiping traded item and so on) there must be something that makes it corrupt. If this "thing" is similar to equip error than that means deleting the folder is just only a one time solution not permanent since that is the stance with the equip error too, it also crashes a bit later again.

Maybe if I would launch the launcher using a script that deletes the cache before starting the app would prevent this error so no more keystones would deplet because of this?