zephyrus-store-preview-new-syntax icon indicating copy to clipboard operation
zephyrus-store-preview-new-syntax copied to clipboard

Inventory Glitch

Open ParzivalGG opened this issue 4 years ago • 12 comments

If somebody is buying custom weapon models, then it works for that particular period and afterwards when they join again their inventory is gone, and they've to buy it again.

ParzivalGG avatar Sep 25 '21 04:09 ParzivalGG

If you using mysql as database. Can you give me a screenshot at the time player buy an item in the store_plugins_log table. If you're using sqlite open the .qc3 file and give me the same table screenshot

nuclearsilo583 avatar Sep 25 '21 05:09 nuclearsilo583

image There ya go!

ParzivalGG avatar Sep 30 '21 04:09 ParzivalGG

image

ParzivalGG avatar Sep 30 '21 04:09 ParzivalGG

Could keep using it for a couple of day to see if this may happen again.

nuclearsilo583 avatar Sep 30 '21 08:09 nuclearsilo583

Close due to inactive

nuclearsilo583 avatar Oct 25 '21 05:10 nuclearsilo583

It is still not saving

KillerRoi avatar Nov 28 '21 18:11 KillerRoi

Everytime, players need to join and equip it again and again

KillerRoi avatar Nov 28 '21 18:11 KillerRoi

Sorry for necroing. This happens when the previous playerskin was expired but not removed from store_equipment database table. Everytime when a player reports the store bug to me, I have to remove the loadout from the database manually.

L 08/23/2022 - 02:23:20: [store.smx] SQL error happened.
Query: INSERT INTO store_equipment (`player_id`, `type`, `unique_id`, `slot`) VALUES(438, "playerskin", "uid_model_megumin", 2)
Error: Duplicate entry '438-playerskin-2' for key 'PRIMARY'

Oz-Lin avatar Aug 23 '22 07:08 Oz-Lin

Can you give me screenshot me the store_equipment table structure.

nuclearsilo583 avatar Aug 23 '22 19:08 nuclearsilo583

Here you go. 图片

Oz-Lin avatar Aug 24 '22 03:08 Oz-Lin

probaly you have done something to that table because the table doesn't contain any primary keys and unique key which make the data can't insert duplicate. This is how the structure from myside even with the fresh/ currently created table. You should backup the store_equipment table and drop it via mysql. And restart the server so it can create that table again with the most exact sync. image

nuclearsilo583 avatar Aug 24 '22 04:08 nuclearsilo583

Thanks, hopefully the problem is solved after moving values from the old store_equipment to the new one.

Oz-Lin avatar Aug 24 '22 05:08 Oz-Lin