Please add a brief but descriptive title
moonies44 opened this issue · 14 comments
Hello. i hope im in the right place.
Baritone , which is being used from the client METEOR (newest version is in that client im told by developers) when turning off "assumewalkonlava" and "assumewalkonwater" , baritone fails to know this and continue's to walk into lava , and water to path. i have turned this off in the module , and also by doing #modified , and then clicking the assume , and turning to false
I have also disabled "jesus" incase this was making baritone walk on water and lava on it own will. to no avail. baritone will continue to walk on water and lava , despite modules being disabled , and jesus being turned off. ultimately leading to "swimming in lava" and drowning.
Some information
Operating system: windows 10
Minecraft version: 1.16.4
Baritone version: Latest commit as of 06/02/2021
Forge mods (if used): Meteor client
Exception, error or logs
No logs indicate .
How to reproduce
turn off assumewalkonlava and assumewalkonwater
Final checklist
- I know how to properly use check boxes
- I have included the version of Minecraft I'm running, baritone's version and forge mods (if used).
- I have included logs, exceptions and / or steps to reproduce the issue.
- I have not used any OwO's or UwU's in this issue.
I can't reproduce this issue. Please provide alternate steps to reproduce it or more information such as a video. Also make sure you are using the latest version.
Alright please leave open I’ll be able to get a video in here tomorrow thank you
Runtime.2021.02.07.-.23.04.34.05.DVR.mp4
dispite turning off "assume walk on lava , and assumewalk on water" , it still walks on water
Your video shows Baritone swimming in water, not walking on water.
But shouldn't these settings be avoiding water , not going into it. lets say it was lava , is baritone supposed to walk me straight into lava then?
No. Normal behaviour (with assumeWalkOnWater and assumeWalkOnLava set to false) Baritone will act like a player and swim in water while avoiding lava.
If you set assumeWalkOnWater to true, Baritone will assume that you have jesus enabled and try to walk on water.
If you set assumeWalkOnLava to true, Baritone will assume that you have jesus enabled and fireresistance and try to walk on lava.
I'm not sure whether assumeWalkOnLava works without assumeWalkOnWater.
Okay so if im understanding .. assumewalkonwater and assumewalkonlava both set to true will then allow you to walk on water , and lava , with jesus on (or swim if jesus if disabled)
But with both turned off it will try to swim in water / lava anyways ? i remember using this a way back and it was able to avoid lava entirely ( weather is go around it , build over it ) is this no longer possible at all?
What is so difficult about this?
I said it acts like a player would, and I hope you don't jump into lava just because some Baritone setting is set to false.
These settings tell Baritone that jesus is enabled and to walk on the respective liquid instead of swimming in water and avoiding lava, yes that means bridging where necessary
Enabling either of them while jesus is disabled will likely fail because it's impossible to follow a path over water by moving in water.
Both Settings are completely independent
| jesus\setting | asummeWalkOnWater true | assumeWalkOnWater false | assumeWalkOnLava true | assumeWalkOnLava false |
|---|---|---|---|---|
| jesus on | walk on water | user error | walk on lava | avoid lava |
| jesus off | user error | swim in water | user error | avoid lava |
Someone close this please, it is caused by the user misunderstanding the documentation as well as Baritones behaviour and not a bug.
Someone close this please, it is caused by the user misunderstanding the documentation as well as Baritones behaviour and not a bug.
assumewalkonlava is false , and it walks in lava , though in the chart you state it "avoids lava" ok
Then upload a video showing how it walks into lava with assumeWakOnLava and jesus turned off.
You only showed intended behaviour.
i know this is closed, but i have the same thing happening to me, and i recorded it happening with lava unlike the OP. i'll attach the video below (at the end you can also see that it actually toggles the setting back on once i reconnect to the server).
i am only using meteor client's (0.4.1, latest) built-in baritone integration, on fabric 1.16.5 (loader 0.11.2). let me know if i should open an issue on meteor's github page instead, or if any more info is needed.
here is the video, i make sure the setting is turned off multiple times and yet it immediately goes over lava when mining.
https://cdn.discordapp.com/attachments/454378929113792512/818390656199950376/2021-03-08_02-36-56.mp4 (too big for github)
edit: also thought i should mention, i do not believe i have any meteor modules enabled that could modify such settings. infinity miner is disabled.