Minecraft Version

1.21

Mod Loader

Fabric

Mod Loader Version

0.16.0

Mod Version

21.0.8

Balm Version

21.0.14+fabric-1.21

Describe the Issue

I recently upgraded my game from 1.20.4 to 1.21. Things were working great in 1.20.4, but there are several issues that came with upgrading, and I am not sure how to resolve them.

Issue 1
I am unable to access the settings menu. When trying to activate the settings I see this:

Issue 2
On 1.20.4 I used to see a blank stone until I activated it, which then added a more pronounced marking on the Waystone. With 1.21 I don't see any of this... They just appear blank.

Issue 3
Since I am unable to access the settings for this mod, I thought perhaps loading my old waystones-common.toml settings file would shed some light on things. While it didn't resolve the issue of the blank stones, it did migrate some settings (like removing the XP cost I had set previously). If I remove this old file, and allow the mod to generate a new one, all the default settings are restored.

Issue 4
Unable to crouch and click the Waystones to modify their names now. This was something that was really useful, and I am not sure why it does not work anymore.

Not sure if anyone else has these issues. Any insight on how to restore things back to working would be appreciated!

Logs

No response

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

No response

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.

latest.log

I've posted the latest because all of the issues I described are persistent.
Thanks!

Awww too bad. I was hoping there was a shader setting, but even the Waystone disableTextGlow did not fix the issue. I will report to the folks at the shader mod about this and hopefully somehow there is a fix. I mean, it was working with 1.20.4 so its possible, its just a matter of finding out what broke.

Thanks again.

For future reference, here is the ticket I opened up at the Complementary Reimagined Shader mod at GitHub:

ComplementaryDevelopment/ComplementaryReimagined#125

I will post back here when more info comes in just in case that helps any other users.

I have checked almost every setting I can in the shaders to test which part is causing the issue but I have had no luck after 30 minutes of testing the settings. Is there anything you can think of that might help?

Thank you !

It is up to the shader mods to ensure they don't break mod compatibility so you would have to report this issue to them.

Only other thing you could try is disabling the text glow in the waystone config (disableTextGlow).

Hey, wondering if the log I provided was the right one or if it was able to shed any insights as to why I am having all these issues? I am eager to get this working. Do you think a complete reinstall of the mod would work (purging all the data configs etc)?

Thank you.

@BlayTheNinth Thank you for pointing that out. That resolved the issue of not being able to click on already placed Waystones to edit them and I can now also load the settings page.

The one lingering issue now is that all the Waystones are still blank. I tried to simply destroy an existing one, and place it down again, yet it is still blank:

Any idea what might be causing this?

What happens if you activate it? Does anything appear in the log? Does it show up in the list of waystones to teleport to?

The log is incomplete, it seems to start halfway through and doesn't contain any of the startup logs.

I recommend reproducing every of the above issues and then taking that latest.log to make sure the log contains as much information as possible.

latest.log

The log is incomplete, it seems to start halfway through and doesn't contain any of the startup logs.

I recommend reproducing every of the above issues and then taking that latest.log to make sure the log contains as much information as possible.

Thanks for this recommendation. I just quit the game and restarted. I wasn't sure what to do while playing, so I attempted to access the Waypoint settings in the Mod menu, but I am not sure that is something that will show up in the logs, as it seems to be a hover notification (the one I showed in the screenshot in the previous post).

Another thing I did while playing was to simply destroy one of the Waystones and place it back again, giving it a name. There doesn't seem to be much else I can do to interact with the waystones other than teleporting around (I did this once as well).

Looking through the logs I am seeing this:

[13:23:06] [Render thread/ERROR]: Error from mod 'waystones'
java.lang.NoSuchFieldError: Class net.minecraft.class_437 does not have member field 'net.minecraft.class_2960 field_44669'

Please let me know if this log file provides sufficient data for you to analyze. I am open to any and all recommendations you might have to make this work as it once did.

Thanks for your time and effort!

java.lang.NoSuchFieldError: Class net.minecraft.class_437 does not have member field 'net.minecraft.class_2960 field_44669'
at me.shedaniel.clothconfig2.impl.ConfigBuilderImpl.(ConfigBuilderImpl.java:53) ~[cloth-config-13.0.121-fabric.jar:?]

The config screen issue comes from Cloth Config and it looks like you're using an outdated version of it (13.0.121 is a version for Minecraft 1.20.4, not Minecraft 1.21).

It does show up in the list of available locations. I did notice some errors in the log but not sure if they are related. I cleared the log file and then used the Waystone to make the file smaller and easier to observe. Let me know if you want a full log again. See link below.

https://paste.ee/p/QhVAj

Thank you !

Does turning off your shaders fix the problem with the runes not showing?

Does turning off your shaders fix the problem with the runes not showing?

Yes it does. Good to know we are getting close. I had the same shaders in 1.20.4 with the runes working fine. Is there something I can do to fix this?

Closing here since I don't think there's anything to be done on Waystones' side.

One last thing you could try is whether a resource pack (e.g. https://bdcraft.net/community/viewtopic.php?t=6469) solves the issue to see if it's an issue specific to the texture or something deeper within shader mods.