When trying to make a pack that used language files, (see example attached) when importing it into the game its name will be "pack.name" and will be imported into a folder named "pack.name" despite the localized name appearing in game
this is a problem because if i make another pack, it will complain that the name "pack.name" is already imported.
[media][media]
Attachments
Comments 7
sorry i took these screenshots a few days ago. i tried it on the beta when i wrote this and it seemed to have the same problem.
just updated to 1.18.10, and it still imports as "pack.name" so, it affects that version also.
Ah, that would be why I'm confused. Since you mentioned you were using the beta, I think you probably thought that the Windows 10 beta was 1.18.20.24. Although it's actually 1.18.20.23, I'm not trying to force you to correct that.
Thank you for your report!
However, this issue has been temporarily closed as Awaiting Response.
Is this still an issue in the latest version? If yes, can you please add it to the affected versions (or mention it if you are not the reporter)?
This ticket will automatically reopen when you reply.
Quick Links:
📓 Issue Guidelines – 💬 Mojang Support – 📧 Suggestions – 📖 Minecraft Wiki
Cleaning up old tickets: This ticket had been set to 'Awaiting Response', but has not received a response from the reporter (~3 months+) so is being closed as Incomplete. If you feel this is still a valid issue then please comment, or create a new ticket following the Issue Guidelines which includes steps to reproduce the problem.
For any account or purchasing related issues, please contact Minecraft Customer Support directly, as we cannot assist with those here at the bug tracker.
Quick Links:
📓 Issue Guidelines – 💬 Mojang Support – 📧 Suggestions – 📖 Minecraft Wiki
The version you are using is unclear. You have reported this as affecting the 1.18.20.24 Preview version, which is currently not available on Windows. According to your first screenshot, you are having this issue on 1.18.2. However, there was an update released earlier today with the version number 1.18.10. Are you experiencing this issue in 1.18.10?