Wont boot. java.lang.NumberFormatException: For input string: "4}" about cratereloaded

[imWillX]

@TomLewis I'll fix the issue where the parser crashes rather than outputs an error.

I knew this was going to be a breaking change thus the major version update. I can add backward compatibility.

[scottyboii]

Please attach your crate file(s)

[TomLewis]

Crates work fine and have done until this update.

[imWillX]

@TomLewis we recently have had an update with breaking changes. https://www.spigotmc.org/resources/pro-crate-reloaded-mystery-crate-1-8-1-19-x.3663/update?update=487696

[TomLewis]

I don't use nbt or CustomModelData which was listed as the breaking changes.

[imWillX]

Could you DM me your crate on discord? It’ll help debug this quicker.

[imWillX]

@TomLewis Do you use durability values? Sorry, I didn't include this in the update logs but damage is moved to a flag.

Before: dirt:123 1

e.g. dirt 1 durability:123

[TomLewis]

Ahh I may do! That may be it then! I will look over my files when I'm home tonight! Thank you

[scottyboii]

@TomLewis Did you manage to solve this?

[TomLewis]

I haven't had time to look over all my configs, I just wont be able to update if it breaks everything and there's no clear message that tells me exactly what needs to change.

It is insnae we have to go back and search through all files, why it wouldn't just output the error instead of entirely killing itself. Very poor implementation.

[scottyboii]

If you want to send over your crate files to one of us, we can take a look for you and let you know!

[WhatsTheBadNews]

@imWillX Sorry if this is too unrelated to the issue, but with "durability:" being switch to a flag for how damaged an item is, what is now the recommended way to show the Unbreaking enchantment? For example, in previous versions, if we wanted to display an item with Unbreaking 3, we would put durability:3 in the config. Now, all those same items no longer show Unbreaking, but do show the item as being damaged. Any help would be appreciated. Thanks

[TomLewis]

The latest version seems to boot fine now! And it gives an error message:

[10:32:30] [Server thread/INFO]: [CrateReloaded] Found NBT in deprecated format. This will not be parsed: [{CustomModelData:4}]
[10:32:30] [Server thread/INFO]: [CrateReloaded] Found NBT in deprecated format. This will not be parsed: [{CustomModelData:4}]

So I searched through all my files and found this! Which is weird as I dont have a RP at present on the server and no need for this! Very odd! At least I was able to find this deep in my crates files from the error message now! If you wish to improve on it further you could output the crate name/line number for anyone else that may not know how to search files for text.

[scottyboii]

Did you manage to solve this, @TomLewis?

[TomLewis]

@scottyboii yeah! So if you use VScode you can right click on the folder of all your crate files and search all files, I used the text that was shown in the startup error to search all my crate files for the "legacy" broken bits across all crates, vscode then lets you click and takes you to the line where it is, so you dont have to spend ages searching through each doc one by one!

[scottyboii]

Awesome, glad you fixed it!