Starting_Items Issues

[utbbop]

Hi All,

Did some searching and couldn't find anything specific to support me so I am back and need some guidance...

I am having issues with my starting items.

My Starting_Items table:
"id" "race" "class" "deityid" "zoneid" "itemid" "item_charges" "gm" "slot"
"1" "0" "0" "0" "0" "15865" "1" "0" "-1"
"35" "0" "0" "0" "0" "18390" "1" "0" "-1"
"3" "0" "0" "0" "0" "9991" "20" "0" "-1"
"2" "0" "0" "0" "0" "9990" "20" "0" "-1"
"5" "0" "1" "0" "0" "1446" "1" "0" "-1"
"10" "0" "2" "0" "0" "18388" "1" "0" "-1"
"6" "0" "3" "0" "0" "3539" "1" "0" "-1"
"7" "0" "4" "0" "0" "3904" "1" "0" "-1"
"249" "0" "4" "0" "0" "8005" "100" "0" "-1"
"248" "0" "4" "0" "0" "18442" "1" "0" "-1"
"8" "0" "5" "0" "0" "3905" "1" "0" "-1"
"11" "0" "6" "0" "0" "18408" "1" "0" "-1"
"12" "0" "7" "0" "0" "3902" "1" "0" "-1"
"250" "0" "8" "0" "0" "18640" "1" "0" "-1"
"251" "0" "8" "0" "0" "14834" "1" "0" "-1"
"14" "0" "9" "0" "0" "18641" "1" "0" "-1"
"13" "0" "10" "0" "0" "18409" "1" "0" "-1"
"15" "0" "11" "0" "0" "18387" "1" "0" "-1"
"16" "0" "12" "0" "0" "14300" "1" "0" "-1"
"17" "0" "13" "0" "0" "14213" "1" "0" "-1"
"18" "0" "14" "0" "0" "18641" "1" "0" "-1"
"19" "0" "15" "0" "0" "18601" "1" "0" "-1"
"247" "0" "16" "0" "0" "2840" "1" "0" "-1"


In an effort to keep this simple, the types of issues I am having is that I am starting with random items not outlined in my starting_items table, on multiple different classes.

An example of the types of errors I am having is as follows:
- When making a bard, I start with the items outlined in my table above AND with "random" items, such as items 8500 and 59967 which are quite obviously not in my starting_items table...


Anyone able to advise how or why this might be happening and perhaps advise on a fix?

As per usual, thanks for your time/help.

[Uleat]

I see item '8005' in your table..but, not 59967.

Are you also getting '18442,' '18640,' '14834,' and '2840' as random items, per chance?

[utbbop]

I see item '8005' in your table..but, not 59967.

Are you also getting '18442,' '18640,' '14834,' and '2840' as random items, per chance?

Sorry about that, i meant 8500 and 59967 and showing up out of nowhere.

Cant for the life of me figure this out. Also getting 32601 out of nowhere (this is Backpack*)

[Uleat]

I looked through the source code that loads starting items and did not see anything that stuck out...

There's no consistency in what race/class combo gets what 'random' items?

[utbbop]

I will gather up more info and provide it here.
Going to go through and test all race/class combos and will report my findings.

Anything else I can provide that would be helpful for you in assisting me?

[Uleat]

Have you modified your source code in any way?

I've been looking through scripts to see if '59967' pops up anywhere. TutorialB has a few numbers near that..but, they are called after npc interaction.

Gonna check tasks next...

[utbbop]

Have you modified your source code in any way?

I've been looking through scripts to see if '59967' pops up anywhere. TutorialB has a few numbers near that..but, they are called after npc interaction.

Gonna check tasks next...

I dont think I have, if I did, it was unintentional.

I just had a VERY strange thing occur when making a Beastlord...
It spawned in the wrong zone and was wearing a full set of my custom warrior armor, had a bag full of random starter armor, and some other odd items...

Got some duplicate entry errors in world.exe window as well...

I sent you a PM, any chance you can join me on skype real quick to view this in action?

[utbbop]

Here are the errors I am receiving. So strange.
Definitely my biggest issue/concern with my server at this point :(


[03-03-2015 :: 20:57:55] [MySQL Error] 1062: Duplicate entry '33-22' for key 'PRIMARY'
INSERT INTO `inventory` (charid, slotid, itemid, charges, color) VALUES (33, 22, 15865, 1, 0)
[03-03-2015 :: 20:57:55] [MySQL Error] 1062: Duplicate entry '33-23' for key 'PRIMARY'
INSERT INTO `inventory` (charid, slotid, itemid, charges, color) VALUES (33, 23, 9990, 20, 0)
[03-03-2015 :: 20:57:55] [MySQL Error] 1062: Duplicate entry '33-24' for key 'PRIMARY'
INSERT INTO `inventory` (charid, slotid, itemid, charges, color) VALUES (33, 24, 9991, 20, 0)
[03-03-2015 :: 20:57:55] [MySQL Error] 1062: Duplicate entry '33-25' for key 'PRIMARY'
INSERT INTO `inventory` (charid, slotid, itemid, charges, color) VALUES (33, 25, 18601, 1, 0)
[03-03-2015 :: 20:57:55] [MySQL Error] 1062: Duplicate entry '33-26' for key 'PRIMARY'
INSERT INTO `inventory` (charid, slotid, itemid, charges, color) VALUES (33, 26, 18390, 1, 0)
[03-03-2015 :: 21:06:13] [Status] SoF Start zone query: SELECT x, y, z, heading, start_zone, bind_id FROM start_zones WHERE zone_id = 29 AND player_class = 15 AND player_deity = 208 AND player_race = 2



Appears to be happening "randomly" and providing "random" items.
Made 2 Beastlords, same Diety/Start Zone/Race/etc, both generated random items. One Beastlord had full warrior gear as I stated earlier, another had bandages, short sword and gloomingdeep lantern (as well as having a custom bag that it should have per my start_item table). The bandages/lanterns/short sword are a definite red flag as I had removed those as starting items entirely I thought....

[Uleat]

I don't have skype set up :/


How old is your source code?

The inventory save code uses an 'INSERT' to save the inventory..so, those errors tell me that something already occupies the slots
that are attempted to be saved at.

A character save failure 'might' be returning the previous characters ID..but, I don't know that much about queries...

You might check to ensure that the character being made is indeed the one at that index (33.)


ref: https://github.com/EQEmu/Server/blob/master/common/database.cpp#L704


EDIT: Someone else more knowledge about the character creation process may have more insight :)

[utbbop]

ISSUE RESOLVED

Moral of the story? Dont manually delete characters from you DB, use the PEQ DB Editor tool, located on the "Player" tab.

There are too many dependencies and deleting just the character from the DB caused all of these issues.

Thank you to JJ and Uleat for helping me through this and especially to JJ for his time with correcting all of my DB tables.