Salvage bug (fixed)

[Tanker]

Some of you have probably already been working around this, but I thought I'd explain it a bit.

Seems that if Salvage fires while you're performing an old-style combine in a world container, you'll eventually get logged out (which resembles a crash, but isn't).

There was a client/server sync issue which caused the server to think the salvaged item was still in the world container (correctly), but the client cleared out the world container (as it would always do before Salvage existed). If you then tried to place an item where the phantom item was in the world container, you'd be looking at your windows background fairly quickly.

Anyway, it's fixed now, but the code won't go up for a bit (our patch schedule being what it is around expansion betas). As a workaround, when doing old-style combines in world containers, be sure to close the container every time salvage fires. This should eject any phantom items into your inventory, resynching the client.

Thanks to all who helped find this one, it was a "I heard of something like that, but don't know how it happens" for a pretty long while.

[Maevenniia]

Thank you for taking time from your busy day to come post this here, much appreciated!

[KyrosKrane]

Woot! Many thanks for the heads up. =)

I'm very curious why it would log you out, rather than crash. That implies a controlled process (though perhaps an unexpected one). Sounds like a defense against hacking was kicking in or something.

[Tanker]

Sounds like a defense against hacking was kicking in or something.

*points at nose*

[Konjure]

Oh! I got Salvage 3 and now I think this is what happened to me a few days ago. But at the time I choosed to blame and curse WinXP.

[Boleslav]

WinXP deserves it anyway, lol.

Boleslav

[Eggborn]

I was wondering if this bug might be related to my experience the other day.

I experienced two things, one was doing tradeskills, the other was not, but they seemed similar.

1. I was using the new tradeskill window, but salvage fired twice. I got one thing back in my inventory, but the other didn't show. I closed out the container as suggested. When I looked in my inventory , the second item showed. I reopened the window and had no problems after that.

2. Later that day I was in a raid in DoN. (Emoush) We had just engaged Emoush, so I wanted to change out my 1hb + Shield I do for offtanking for my 2h slash epic with group clicky. I have a bandolier set up for it. When I hit my epic bandolier, I noticed text that I was slashing the mob, however, when I opened my inventory to click on the weapon it didn't show anything was equipped. I had gotten a message I did it successfully though. I hit bandolier again, said success, still nothing, so I reached into my bag and got my weapon out to equip it. I continued to slash the mob. When I tried to click on the weapon I went to the "You have been disconnected" screen. Grr, we killled Emoush, no crystals for me, and no logs to show that I won either later from GM, But..

I wonder if the two incidents are the same bug?

If they are, be careful. If the GM couldn't see what we had just done in my logs, then your combines might not count either. On another related note, I have a few friends that have had their GM quest progression erased each time we patch. If you are in the middle of one, try to finish it before the next patch. My husband also lost all of his Don progression task records as well. It's still buggy, so finish that stuff before they patch if you can.
Anyone else see this stuff in game? Please move this post if you don't think they are related.

[waldora]

The pain of this bug.

I recently did a skill run from 234 to 251 in baking. I have salvage 3, and was doing MTPs. What an annoying bug. The good news is: my salvage seemed to fire for every failure, the bad news: I had a LOT of failures (as expected) but what a pain to have to close the oven after every failure.

Open, select MTP, click combine, fail, salvage kicks, close, open, select MTP.

I did not go LD even after some 400 combines.

[Tanker]

While it certainly seems this is another case of the client and server losing synchronization, it definitely isn't caused by the same code that I fixed last week. That fix will NOT fix this other sync issue.

I'd be very interested in reproducible steps for this new sync issue. Things to try/look for when you do a bandolier switch, and notice a "missing" item (it's not missing on the server, just on the client):
- Write down the items that were in your 4 bandolier-type slots (Main/2nd, Range, Ammo) both before and after the swap.
- Write down the items that are in the bandolier entry that should be equipped now (that should give us what failed).
- Look at your general inventory, how many slots are empty in your bags? If there's only one "blank", it's probable that your missing item is there (on the server). Write down how many empty slots you have in general inventory (and what "size" they can hold).
- Write down any empty worn slots you had prior to the swap, even those that aren't bandolier-type.
- Post about it, but over on the EQ boards, so that more than just those of us who look here can see it. This isn't really a tradeskill issue, and these aren't SOE boards, so it really belongs over there.

After you've done all that, you'll want to zone or log/log in order to "fix" the sync issue, so you don't get dumped when you accidentally perform an item move that the server finds offensive.

Thanx for bringing this up.

[waldora]

Shameless bump,

Any chance we can get a confirmation that this was fixed/or not?

[Tanker]

My understanding is that this was NOT pushed with the patch this week. That we patched any code at all this time was a concession to design's ongoing world-changing events, plus a few hack fixes. Those changes were added to the code last patched, directly.

When the decision not to patch new code was made (several weeks ago), the new code was fairly unstable on it's way to beta for DoD. Since then, we've fixed it up right, but had progressed along the workpath of the decision not to patch code too far to change.

Look for this fix when we update to current code, which will definitely be at expansion launch, if not sooner.

[Tiliki]

My understanding is that this was NOT pushed with the patch this week.

It appears that the fix did go in, unless I misunderstand the problem, or solution. This is what happened: I put a small block of clay, vial sketch, zombie skin and flask of water in a pottery wheel and hit Combine. I failed the combine, but salvaged the clay. The clay remained in the pottery wheel, rather than appearing to go into inventory, which is what I would have expected if the bug was still live.

Am I correct, and the fix actually did make it live?