Guild Wars 2

Healix.5819:

Imperator Nox.7509:

So, I tried to -image my install, but no joy.

-image only ensures that every file is downloaded.

-repair is what verifies each individual file.

Thanks for that distinction, Healix. I did the repair and although the mini still does not look as it did when it was first released (i.e., it still looks exactly like the other one mentioned), it does, at least, now move around with a different walk than its cousin does. (And who knows, perhaps that’s due to some redesign, and so therefore intentional — I really don’t know. (If so, it would be a horrible decision to have been made, but that’s neither here nor there.)) Regardless, I am very grateful to at least now be able to tell them apart.

And thank you as well, Inculpatus. That’s exactly what I will do next if I should happen to find out that the models should in fact NOT be the same.

Cheers.

So, I’ve been kicking this around in support on and off (with little followup after receiving weak or no answers) for over a year, but a recent reply I received from another person here has verified that a pet theory seems to be correct…

To summarize: Over a year ago, my Enraged Twisted Watchwork Nightmare mini went bonkers and STOPPED looking and acting like it always has (slightly different from the normal TW mini) and started essentially looking and behaving EXACTLY like the normal TW Nightmare mini.

In the interest of saving (your) time, I will snip out and not go over all the failed theories and suggestions I have been presented with and tested, but will instead cut to:

…so of late, I have come to suspect that my Enraged mini’s data is corrupted and it is simply reading the contents of the normal TWN mini from the DAT, since I have now heard from two others that their minis do NOT look/act the same. So, I tried to -image my install, but no joy. Same issue. It seems that, whatever else may be going on, the client does not see anything flagged as wrong in the .dat, and so is not trying to fix it.

So… any suggestions? I realize this is small potatoes compared to so many other issues discussed here, but I’ve honestly tried every other possible way of getting this resolved and none have worked.

…and it’s been like this for a very long time now.

…and I would be really appreciative if someone could help me fix this ridiculous situation.

Thanks!

I fought and beat Poobadoo twice today, with two different guilds ([THIS] & [TTS]), both times contributing substantially to the damage. I received credit & chest on all other bounties today (total 3 guilds), but both times on Poobadoo only, the guild received the favor, but I did NOT receive a chest or a commendation.

Anyone else experience this?

I think this is the wrong way to go about thinking regarding shared slots. Using this justification, you can ask for a refund for pretty much anything you have more than one instance of. Why not ascended equipment? After all, you can take it off, put it in the slot, and use it on another toon (assuming same armor type). And why stop there?

It is inevitable that new UI options will obviate some past functionality. While I agree with OP’s particular case (assuming I’m understanding correctly that you had JUST bought them prior to obtaining shared slots, and have not had the chance to even use some of them), I think one needs to consider that fact (about UI changes) as the first step.
PS – I also have a ton of them.

This is something that started well over a year ago. I have had a quite long break in the interim, and was hoping it would be fixed upon return, but it was not to be.

The Enraged Twisted Nightmare mini, at least on my client, is now virtually the EXACT same model, doing the exact same movements, as the normal Twisted Nightmare mini. This was NOT the case upon creation. At that time, the model was different (iirc, like the real things, it lost its medial arms in the second, “angry” stage, among other differences), and it certainly behaved quite differently.

So I don’t understand why anyone would make the decision to simply overwrite the behavior of one mini with another (although you’ve altered behavior (for the worse) other times; see the chainsaw skeleton mini, for example), especially given the much higher cost for the Enraged version. Now I have one normal, and one pointlessly expensive Twisted Nightmare. Yay.

I tried also repairing my DAT in the long hope this was all just a misunderstanding. Alas.

And so, I am still holding out hope (barely breathing… but still alive) this was not some absurd managerial decision, but a simple error, one that can be easily remedied… yes?

Please say “Yes”.

Oddly, I didn’t load the response from Jeffrey before posting the last message.

Jeffrey, thank you for responding. I guess I made it past, but I’m very glad your fix will prevent others from sharing the same frustration. Your attending to this is very appreciated!

UPDATE AND POSSIBLE WORKAROUND FOUND! (maybe!)

After another try, I may have discovered a workaround to the bugged code (and if this works, it should give anet a hint as to where to look to fix this).

This time, I tried something I’m pretty sure I didn’t try before: when going to the logging camp, do NOT take the right path around that hillock between the gate where you start and the camp. Instead, be sure to stay on the main dirt road, which goes the slightly longer way around to the LEFT of the hill.

Of course, make sure you let all the cutscenes play out and take your time about everything at the beginning as well… but this tiny change seems to have made all the difference. When returning, I took the road again, and this time, found a proper fight waiting, not the previously-encountered half-dozen risen randomly scattered about. They actually killed everyone in the party, and there were several waves before this part was done.

After reading these forums, I knew once I saw the giants in the cutscene that I was most likely home-free, and so it was.

So for those of you who, like me, simply tried to be as efficient as a war might demand and go straight to the trouble – haha, silly you! DON’T. Take the completely unjustified longer walk down the main path instead, and see if that does it for you. (If not, then this must surely be a randomized bug, because every other element up until the bugged point was played the same way this time, yet the outcome was very different.)

Thankfully, the bug is very much at the beginning of this very important mission, and not at the end!

I hope this works for everyone out there stuck in the same place! Best of luck to all of you!

This is just absurd. So many people have the same problem; why is it not being fixed when it impedes such a MAJOR part of the environment (using the kitten asura gates to travel to Orr)?

PLEASE FIX THIS NOW.

(Yes, I also am getting stuck, in the EXACT same place as everyone else… AND I DON’T have ANYONE with me. Just me. Solo. Five times now. This is so disappointing.)

I just tried to purchase 8 small fangs at a total of 8s80c, which the trading post took when I clicked “buy”, immediately prior to throwing me a “Network Error” message box, which, when I "OK"ed, I found my funds reduced as stated, with no fangs for pick up.

It does not show up in my recent transaction either.

Imperator Nox.7509
(error code not noted when thrown)