True Sight Staff does not find new Iesnium Ore
Describe the bug The True Sight Staff, after searching and locating Iesnium Ore, does not then search for a new location. It will continue to direct me to the first Iesnium Ore that it found, even after I have mined the block(s). I can fly several hundred blocks away from the first located Iesnium Ore, and the True Sight Staff will still direct me to go back to it.
To Reproduce Steps to reproduce the behavior:
- Acquire True Sight Staff
- Attune to netherrack in order to find Iesnium Ore
- Follow purple orb to Iesnium Ore and harvest
- Use True Sight Staff to attempt to find more Iesnium Ore. It will direct the purple orb to the Iesnium Ore you just harvested
Expected behavior I expected it to work like the Divination Rod, and search for a new Iesnium Ore after harvesting, or after moving far enough away.
Screenshots If applicable, add screenshots to help explain your problem.
System (please complete the following information):
- Occultism Version:
- OS: Windows
- Minecraft Version:
- All The Mods 10 Version 4.0
Additional context Don't know if this is relevant, but in the Dictionary of Spirits, under the listing for True Sight Staff, some minor grammar inconsistencies are present, such as "now is possible locate any block" Given the lack of any such inconsistencies in the rest of the Dictionary of Spirits (that I've noticed), that makes me question if there is any information missing from this entry. And, if so, if that means it is just user error with the True Sight Staff resulting in my issue.
Thank you for any help you can provide, and I hope this bug report finds you well!
Hiya, as an user that has used the True Sight Staff recently, do you remember if you tried to use it on your offhand instead of your main hand? It seemed to me that using it in the main hand locates a new ore properly, but not on the offhand.
It works exactly like the divination rod (same code) You need to hold the right button to do a new scan (when I created it and testing it now, work in any hand)
I believe this is resolved and was simply user error?