#find not working on 2b
Some information
Operating system: windows 10 Java version: 17.0.11 Minecraft version: 1.21.4 & 1.20.1 Baritone version: 1.21.4 & 1.20.1 Other mods (if used): meteor
Running mc 1.21.4 connecting to 2b2t with viafabicplus set to connect as 1.20.1 to use ebounce. Running '#find chest' returns 'No positions known, are you sure the blocks are cached?'.
Going on my own server running 1.21.4 #find works as expected.
I downgraded everything to 1.20.1 took vaifabric plus out of mods folder and have the same result.
Final checklist
- [x] I know how to properly use check boxes
- [x ] I have included the version of Minecraft I'm running, baritone's version and forge mods (if used).
- [ x] I have included logs, exceptions and / or steps to reproduce the issue.
- [ x] I have not used any OwO's or UwU's in this issue.
Are you sure there are known chests within the loaded cache area? #find cannot distinguish between blocks not being cached and no blocks being nearby, all it sees is that there are none stored in cache.
There will be chests shown on meteor esp when I run the command. I assumed if there were chests within render distance they would be loaded into cache. I've also placed them myself then running #repack with the chest right in front of me then running #find with the same result.
Hm, that should work. Are you sure it only happens on 2b2t? That would be really annoying (a dozen hours per test is too much).
I've only tried it on my small private server and 2b. The one variable I can think of is my server is 21.4 and 2b is 20.1. I can check other servers and report back.