TheOneProbe information displays correct mod name
GreatestFool opened this issue ยท 11 comments
Bug description
The One Probe information displays which name the fake block is from, regardless of which block it is mimicking.
Expected behavior
In the gif on the mod page the mod name changes to whichever mod it's from, in the gif it was from Fake Blocks to Minecraft.
When I try to replicate this behavior, mine does not change its name.
Versions
- Minecraft: v1.16.5
- Forge: v36.1.10
- Mod: v1.0.2
Other mods
I have a few other mods, but I doubt they cause this issue.
- The One Probe: v3.1.4
- Item Zoom: v2.3.0
- Just Enough Items: v7.7.0.99
- KubeJS: v1605.3.10-build.8
It still happens even if all other mods than The One Probe and Fake Blocks are disabled.
This mod currently only supports WAILA.
I have to look into it, if it is possible to do the same with the one probe.
Aha. That explains it. Was not aware it was only for WAILA, sorry for the inconvenience.
I'd greatly appreciate if you could look into if the same is possible with The One Proble :)
Is it Hwyla Fake Blocks has integration with on Minecraft versions such as 1.16.5? As far as I can see, that one is archived due to TehNut not being interested in modding anymore.
If it is, an alternative to Hwyla is the fork of it called Jade. Though, that might be the one your mod has integration with for all I know :)
Also, sorry for messaging so quickly after the other.
Right, looks like it doesn't work with Jade. I'm assuming that is due to the internal namespace of it is both waila (like the Hwyla fork also had) as well as its own jade namespace?
True, it does still work with that one, but is it not better to use an updated and maintained fork that includes pull requests and bug fixes instead of an archived version?
Considering the dev has publicly added to the mod page that he's no longer interested in modding, archived all of his repositories and even edited the information on his GitHub account to mention that it is a graveyard and all but abandoned it completely, I'd say that is only a matter of time :) Jade also has a 1.17 update in the works.
Thank you :)
Also, #5 is not the same issue as this. I had a brainfart and forgot to change parts of the template I copied over. I've fixed that, but it'd be nice if you could re-open it and take a look at why grass does not colorize when faked.
It'd be far easier to simply re-open the issue, considering it'll be a complete copy-paste of issue #5... but alright.