Waystones

Waystones

123M Downloads

Waystone issues on 1.21.1

Saereth opened this issue ยท 8 comments

commented

Minecraft Version

1.21.1 (LTS)

Mod Loader

NeoForge

Mod Loader Version

21.1.22

Mod Version

21.1.1

Balm Version

21.0.18

Describe the Issue

When a waystone is placed the ui doesn't let you set a name its just blank.
image
image

additionally when waystones generate in the world they add a blank name to the map and this isnt removed even if you break and replace the waystone:

image

Logs

No response

Do you use any performance-enhancing mods (e.g. OptiFine) or custom server distributions (e.g. SpongeForge)?

No response

commented

Please provide the full logs. You can find the logs in the logs directory of the client or server. Most of the time latest.log is the correct file (unless the crash or issue happened during an earlier run).

Logs can be uploaded here by dragging the file into the comment field, or you can post them on a site like https://gist.github.com/ or https://pastebin.com/. Make sure they are set to be public (or unlisted) and to never expire.

commented

sorry for the delay, here you go! https://mclo.gs/iMqPaRS if you need anything else I'm happy to provide it. Thanks

commented

yeah that fixed it for me as well

commented

Cannot reproduce with just Waystones.

Does it happen without FTB Chunks? The map integration seems to be implemented there so it's likely the issue lies in there.

commented

Am having the same issue on a pack im working on in NeoForge 1.21.1
Tried to disable FTB Chunks and getting the same issue. Not sure what is causing this. Cant see anything in logs.

commented

Ok I think I may have found a fix. Its to do with the menu blur introduced in 1.21
if you go to options, accessibility settings, then change Menu Background Blur to Off and it shows the text on waystones again.

commented

Having the same issue in the ATM10 Pack seems like a waystone and mc issues not pertained to the pack it seems

commented

a little more investigating, if you turn the new vanilla blur option all the way off in the graphics setting it seems to solve this. This may be some interaction with sodium/embedium as well however.