Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Renamed tomes lose their name when they transform #37

Open
TheDeviantCrafter opened this issue Aug 2, 2018 · 6 comments
Open

Renamed tomes lose their name when they transform #37

TheDeviantCrafter opened this issue Aug 2, 2018 · 6 comments

Comments

@TheDeviantCrafter
Copy link

In the pack I'm working on, I'm including an akashic tome with every guide book in the game already included. I've added a recipe, made players start with it in their inventory on world creation, and forced it to appear in JEI.

The book is renamed to the Universal Guide. When the player turns it into a guide book and back, this name is lost.

@TheDeviantCrafter TheDeviantCrafter changed the title Renamed books lose their name when they transform Renamed tomes lose their name when they transform Aug 2, 2018
@DoomRater
Copy link

Duplicate of #9, pretty sure

@TheDeviantCrafter
Copy link
Author

TheDeviantCrafter commented Aug 7, 2019

It's caused by the same issue. Morphing the book deletes all NBT data.

@DoomRater
Copy link

Oof, it even strips Armourer's Workshop skins off it.

@DoomRater
Copy link

Anyway, my current recommendation if you want the book to be renamed is to include a resource pack that changes the relevant translated name in the en_us.lang file. To do this, include the folder structure assets/akashictome/lang/ and inside that lang folder include a modified en_us.lang file. Include relevant pack.mcmeta and a pack.png file in the root folder, and ZIP it up. This won't solve the other issue I linked to, but it should solve yours.

@Uraneptus
Copy link
Member

I need confirmation that this is still happening in version 1.20

@Uraneptus
Copy link
Member

Got confirmed and will be fixed for 1.20.1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants