Closed EliConstructor closed 6 months ago
Could have sworn I searched with those exact words, but I guess I didn't. Disabling removeExperimentalWarning in frozenlib.json5 did the trick, thanks.
No problem! The option’s being set to disabled by default in the next release, so I’m hoping people won’t run into this anymore.
Description of the Bug Encountered When I try to open an existing world with only Fabric API, Wilder Wild and Tectonic installed, the game fails to load the world, with the message "Failed to access world [world name]" (See screenshot). This doesn't happen with just Tectonic or just Wilder Wild, only both together. It's probably worth noting that generating the world works fine, I can make a new world and the game runs normally. But if I close the world and attempt to reopen it the error will show up.
Steps To Reproduce
Expected Behavior The world opens as normal
Screenshots (The world is called test)
Logs Error that shows up in log when attempting to load the world:
Additional context Minecraft version: 1.20.1 Fabric Loader version: 0.15.10 Fabric API version: 0.92.1 Tectonic version: 2.3.4 Wilder Wild version: 2.3.3