Closed seema84 closed 3 months ago
That error is in the server itself and ideally needs to be fixed there (neither 1.20.6 nor 1.21 can be considered stable yet) and working around this isn't ideal but can you provide the serialized string of the item it fails on from your items.db? Or just your full file if that's easier for you.
That error is in the server itself and ideally needs to be fixed there (neither 1.20.6 nor 1.21 can be considered stable yet) and working around this isn't ideal but can you provide the serialized string of the item it fails on from your items.db? Or just your full file if that's easier for you.
created a zip because github does not support the .db format
I just tried it with your items.db file and it seemed to work locally for me. (Is the file you provided from the backup before updating? If not please provide that as the errornous data might've been removed)
I also then I double checked your post and noticed that you are using an old build and purposely remove the line for that hence me not catching it... Please test with the latest build (make sure that you use the items.db from before you noticed the error!) and stop trying to circumvent issue templates, they exist for a reason.
It was the items.db after the error. Here is the one from the backup:
It was the items.db after the error. Here is the one from the backup:
Ok I tried with this and it again worked without issues. Please test with that items.db and the latest build and see if the issue persists.
The error is still displayed with build 419. However, only if I use not only the items.db, but the entire Chestshop folder from the backup.
The error is still displayed with build 419.
Please provide the new log.
However, only if I use not only the items.db, but the entire Chestshop folder from the backup.
That does not make much sense, the error stems from the items in the items.db, while you might have names in other config files these have no influence on the location in the code where you get the error triggered from.
However, if I only replace the Items.db, the error does not seem to occur.
Server Log
Log However, if I only replace the Items.db, the error does not seem to occur.
Ah, right, I just remembered that the version
file contains the latest metadata-version hence why it wouldn't trigger it again when just replacing the items.db, it also needs to be a version file with an old metadata which triggers the conversation.
It looks like the database update is not performed if I only replace the items.db
Can you please provide what metadata-version is in your version file from the backup too? Just so I can test (and report if necessary) with the exact version.
Can you please provide what metadata-version is in your version file from the backup too? Just so I can test (and report if necessary) with the exact version.
version: 4 metadata-version: 3700
Ok, I checked this and you can safely ignore these warnings, it seems to have converted all the data properly not sure why exactly it prints that anyways... (Unfortunately I can't handle them better as they are printed from server-internals and not exposed to plugins)
Okay thanks. Should I report this to Paper?
Okay thanks. Should I report this to Paper?
If you want, sure. It doesn't seem to cause issues though as far as I can tell.
Paper has provided feedback on this. Can you perhaps tell me which items they are and where I can find them?
What is happening?
This error message was displayed after the first start with version 1.20.6.
Plugin Version
ChestShop v3.12.3-SNAPSHOT (build 403)
Server Version
Paper version 1.20.6-147-ver/1.20.6@e41d44f
Server Log
Log
``` Failed to parse custom name from string 'Player's Kiste', discarding com.google.gson.JsonSyntaxException: com.google.gson.stream.MalformedJsonException: Use JsonReader.setLenient(true) to accept malformed JSON at line 1 column 13 path $ at com.google.gson.JsonParser.parseReader(JsonParser.java:76) ~[gson-2.10.1.jar:?] at com.google.gson.JsonParser.parseString(JsonParser.java:51) ~[gson-2.10.1.jar:?] at net.minecraft.network.chat.Component$Serializer.fromJson(Component.java:304) ~[paper-1.20.6.jar:1.20.6-147-e41d44f] at net.minecraft.world.level.block.entity.BlockEntity.parseCustomNameSafe(BlockEntity.java:365) ~[paper-1.20.6.jar:1.20.6-147-e41d44f] at net.minecraft.world.level.block.entity.BaseContainerBlockEntity.loadAdditional(BaseContainerBlockEntity.java:42) ~[paper-1.20.6.jar:1.20.6-147-e41d44f] at net.minecraft.world.level.block.entity.ShulkerBoxBlockEntity.loadAdditional(ShulkerBoxBlockEntity.java:242) ~[paper-1.20.6.jar:1.20.6-147-e41d44f] at net.minecraft.world.level.block.entity.BlockEntity.loadWithComponents(BlockEntity.java:94) ~[paper-1.20.6.jar:1.20.6-147-e41d44f] at net.minecraft.world.level.block.entity.BlockEntity.lambda$loadStatic$5(BlockEntity.java:205) ~[paper-1.20.6.jar:1.20.6-147-e41d44f] at java.base/java.util.Optional.map(Optional.java:260) ~[?:?] at net.minecraft.world.level.block.entity.BlockEntity.loadStatic(BlockEntity.java:203) ~[paper-1.20.6.jar:1.20.6-147-e41d44f] at org.bukkit.craftbukkit.block.CraftBlockStates.getBlockState(CraftBlockStates.java:291) ~[paper-1.20.6.jar:1.20.6-147-e41d44f] at org.bukkit.craftbukkit.block.CraftBlockStates.getBlockState(CraftBlockStates.java:276) ~[paper-1.20.6.jar:1.20.6-147-e41d44f] at org.bukkit.craftbukkit.block.CraftBlockStates.getBlockState(CraftBlockStates.java:266) ~[paper-1.20.6.jar:1.20.6-147-e41d44f] at org.bukkit.craftbukkit.inventory.CraftMetaBlockState.getBlockState(CraftMetaBlockState.java:411) ~[paper-1.20.6.jar:1.20.6-147-e41d44f] at org.bukkit.craftbukkit.inventory.CraftMetaBlockState.Agreements