[DiscordArchive] what if i said you werent losing them from item_instance but character_inventory?
[DiscordArchive] what if i said you werent losing them from item_instance but character_inventory?
Archived author: Tea • Posted: 2025-08-04T15:51:25.228000+00:00
Original source
what if i said you werent losing them from item_instance but character_inventory?
Archived author: stoneharry • Posted: 2025-08-04T15:54:02.288000+00:00
Original source
I would need to investigate it, my focus thus far has been on item_instance
Archived author: Takenbacon • Posted: 2025-08-04T15:56:40.164000+00:00
Original source
vanishing on just a map change would be a bit odd. I could understand on relog but map change tells me it's not database
Archived author: stoneharry • Posted: 2025-08-04T15:59:11.695000+00:00
Original source
I have not actually managed to reproduce it, but I have a lot of player reports. It's possible it is only on relog but they misreport on map change too ♂️
Archived author: Tea • Posted: 2025-08-04T16:00:47.065000+00:00
Original source
damn users
Archived author: Takenbacon • Posted: 2025-08-04T16:13:37.884000+00:00
Original source
I used to dump all the mysql errors to a log and review periodically. not fool proof but gives you an idea if there was some issue with data loss and with duplicate key entries
Archived author: jackpoz • Posted: 2025-08-04T16:16:01.569000+00:00
Original source
Long ago I had the thought of having a queue for each player, where only one thread could process 1 query at a time
Archived author: jackpoz • Posted: 2025-08-04T16:16:29.406000+00:00
Original source
Or different queues for different scopes, like 1 for instances, 1 for items, etc
Archived author: jackpoz • Posted: 2025-08-04T16:17:32.482000+00:00
Original source
Right now the delete item query can be executed before the create item by 2 different async threads (don't take this example too literally as I didn't check items code)
Archived author: jackpoz • Posted: 2025-08-04T16:18:42.756000+00:00
Original source
But yeah, you need some sort of order for async db queries and that order doesn't exist atm