Crash to login screen when selecting item
 

Hey guys,

I'm having issues with my offline server. Using Minilogin, PEQ DB, and Underfoot client. When I click on an item and it is picked up, I crash to login window. I've tried it in different zones and with different loadskin, same outcome. Also the item itself is gone when I log onto the char again. Kinda makes stuff like equipping very difficult. My item select has become the new crash game/destroy item button. In my database I removed no drop from all items, and this change didn't show up in game. I wonder if there's a connection.

Is your client actually crashing or are you being kicked?

Post the item id and where you are picking it from (i.e., inventory, corpse, bank, etc...)

It isn't a full crash where the EQ game window is gone, so perhaps it is that I'm kicked back to login screen.

Also it doesn't matter which item I use, the moment I pick up an item with cursor, it happens. It's when I pick up an item out of my inventory. I can loot items off corpses using loot all.

I'm not sure what's going on there...

I've played on UF with the only difference being I use a private login server..never used the mini, but I hear it still works.

Try checking the zone logs to see what messages are being generated when you move an item.

How do I check the zone logs? I'm only familiar with checking my logs folder in my server folder, other than that I wouldn't know.

That's what I was referring to. There should be a record of the move request.


Also, in your game folder, there is a log folder there as well. Look inside for a file called dbg.txt. This is the client log file.

Sometimes useful information can be found there too.

Excellent, the error is located!
From my everquest log:
[Sun Nov 03 07:31:48 2013]00341:Initialization complete.
Entering main loop.
[Sun Nov 03 07:31:51 2013]00342:Zone Connect -- Received MSG_READY_ENTER_WORLD
[Sun Nov 03 07:31:51 2013]00343:Item done, MSG_WEATHER_EVENT received.

[Sun Nov 03 07:31:54 2013]00160: D3DXCreateTextureFromFileEx() failed to create texture pt_add_smoke.dds for particle system.

[Sun Nov 03 07:31:54 2013]00161: D3DXCreateTextureFromFileEx() failed to create texture pt_add_smoke.dds for particle system.

[Sun Nov 03 07:32:05 2013]00162: D3DXCreateTextureFromFileEx() failed to create texture pt_add_smoke.dds for particle system.

[Sun Nov 03 07:32:36 2013]00344:*** DISCONNECTING:



Server log:
[11.03. - 07:32:33] [INVENTORY__SLOTS] Test: Putting loot item Rat Paw (59967) into slot 25
[11.03. - 07:32:36] [NET__ERROR] Moved item from 26 to 31
[11.03. - 07:32:36] [INVENTORY__SLOTS] Test: Src slot 25 has item Rat Paw (59967) with 1 charges in it.
[11.03. - 07:32:36] DeleteItemInInventory(25, 0, false)
[11.03. - 07:32:36] [INVENTORY__ERROR] Test: Inventory desyncronization. (charname: Test, source: 25, destination: 30)

You should try logging into a server that is known to be working, like PEQ and see if it still happens. That would narrow down if it is a client issue or server issue. Those lines in the client log may be meaningless.

Definitely trust lerxst! He's set me straight more times than I can remember :)

I agree that the client logs probably won't yield anything in this case, especially since there's a 28-second difference between the messages.


[If if turns out to be your server...]

Going on the assumption of an autoloot->cursor pickup->delete action, this is the only segment of code I see that will cause this exact sequence:
https://github.com/EQEmu/Server/blob...tory.cpp#L1153

And since this is a fail return scenario, the resync code kicks in for the final message.


Hopefully something in this con-check will jog your memory or, at least, point us in the right direction :)


EDIT: Looking at this closer, there appears to be only 2 cases where the server will 'World Kick' you..that link is one of them.
This doesn't include the perl or lua interpreters, which would bring into account script files...

Here's what I see:

loosely interpreted as:

if(((<trade>) || (<shbank>)) && (<chknodrop>) && (<rule:fvnodrop==2>) || (<rule:nodropexemption<admin>) && (<rule:fvnodrop==0>))


There's probably a missing encapsulation somewhere in there somewhere.

I've been able to play on multiple EQEmu servers no problem. It's my server that has the issue. What do you suggest in order to isolate the problem? I have limited experience with programming. I only know how to source a database and do basic edits. Thanks for replies

Have you made adjustments to the server rules?

Yes, a whole lot of them. Which rules could affect items this way?

I'm not too familiar with the fvnodrop aspect..however...

..you don't appear to be trading or using the shared bank.


I can't follow the logic of that snippet I posted before, but I would check the 'MinStatusForNoDropExemptions' first.

The way that it 'looks' to me, it appears to be able to fail up to the '||' (boolean OR).

Then, if 'RuleI(Character, MinStatusForNoDropExemptions) < Admin()', it will kick in the success code regardless..which would explain your symptoms...


If that doesn't work, we'll keep trying :)

Good news. I changed one thing, I changed 'MinStatusForNoDropExemptions' to 250, the same as my account. And now my character isn't being kicked when moving items. What bothers me though, is that I deleted no drop on all items, but it's still saying no drop in game, and same with lore tag. Confused about that. At least one problem is solved so far.

Btw thanks for helping :)