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

JMC 113 and 114 grass paths bugged/removed #173

Closed
xelacreations opened this issue Nov 2, 2021 · 3 comments
Closed

JMC 113 and 114 grass paths bugged/removed #173

xelacreations opened this issue Nov 2, 2021 · 3 comments

Comments

@xelacreations
Copy link

Hi,

I recently updated to JMC 114 and noticed that suddenly all the grass paths where gone from exports.
I checked if they where just hidden but no, they where ticked on.

Even after updating the world to 1.17 it still got removed, and when going back to JMC 112 the grass paths are back.
I also tried a clean folder for 114 but then the paths are still gone.

Is there any fix for this?

  • Xela
@mmdanggg2
Copy link
Collaborator

I'm not seeing this issue on 114 with a 1.17 world, maybe try to restore factory settings. Are there any errors/messages in the console/log?
image

@xelacreations
Copy link
Author

Hey,

So after some invesigations new world in 1.17.1 work with paths exporting.
But when I grab a world with 1.16 or older they start not exporting anymore even after opening the world in 1.17 afterwards.

I don't see any errors in the console and it says it exports right but they just do not appear and it just removes them.

  • Xela

@mmdanggg2
Copy link
Collaborator

Ok, I had another look and this is because grass_path was renamed to dirt_path in 1.17 and so it can't find the block model for grass_path from the 1.16 world in the 1.17 minecraft jar. It should say in the log that it couldn't find the block in the resource packs when you export:
image
I'll have a look at making that error more visible.

I found that loading the chunks in 1.17 did update the block to dirt_path and that exported fine afterwards. It could be that just opening the world and not being near those chunks doesn't update them.
If you want to keep using 1.16 then you can manually set 1.16 as the resource pack to use:
image

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

No branches or pull requests

2 participants