search

mega12345mega / NBT-Editor

Edit items, blocks, and entities in-game.
MIT License
31 stars 9 forks source link

Editing sign NBT don't work in the latest update #63

Closed Maks7594 closed 5 months ago

Maks7594 commented 1 year ago

Editing the sign NBT data to have some text doesn't work. The sign is blank.

HyperSoop commented 1 year ago

try doing this in singleplayer; you can't do some NBT editing on servers without having OP

mega12345mega commented 1 year ago

As far as I'm aware, everything should work the same regardless of op or single vs multi. @HyperSoop can you specify what only works with OP (possibly in a different issue)? It is possible Minecraft started "regulating" creative mode's ability to create any item - if so that's very unfortunate. All edits are sent through the same creative slot update packet, so I would expect all edits to function the same.

@Maks7594 which Minecraft version are you using? 1.19.4 and below handle signs differently then 1.20 and above, since 1.20 supports editing both sides. If you happen to be trying to place a sign from 1.19.4 in a 1.20 world, you will need to run /itemfactory signboard import first. If that isn't the issue, I'm assuming that the editor itself shows the text (even when reopened), it just doesn't show when placed down.

EDIT: I'm also assuming that you're using the new /itemfactory signboard editor. If you are using the /nbt editor directly, you may just need to switch to the new format (https://minecraft.fandom.com/wiki/Sign#Block_data).

HyperSoop commented 1 year ago

It is possible Minecraft started "regulating" creative mode's ability to create any item

I am not sure. It might be a patch in PaperMC. What's prevented is mainly things that can give you OP, like spawn eggs of command minecarts and falling command blocks/ spawners, i think also signs and books, but again I'm not sure.

mega12345mega commented 5 months ago

Since I haven't gotten any more information on this issue, and it seems to work fine in my own testing, I'm closing. If the issue is still occurring, please create another issue (unless you're able to re-open this one).