@dyiing
Muchly appreciated, I see some GUI changes in the update log today.
Can confirm, problem fixed.
Many thanks for your time.
@dyiing
Muchly appreciated, I see some GUI changes in the update log today.
Can confirm, problem fixed.
Many thanks for your time.
Further update - it appears I had indeed been busted back to standard version.
I re-downloaded the donor version, and all is well, will copy across my settings.
I made an additional donation to help you continue your work, as I've been using this for a couple of years, and figure it's about time I donate again.
Further update - it appears I had indeed been busted back to standard version.
I re-downloaded the donor version, and all is well, will copy across my settings.
I made an additional donation to help you continue your work, as I've been using this for a couple of years, and figure it's about time I donate again.
I just loaded up 1.20.4 aristois this morning
went to my usual server, and multiaura does not appear to be on the list anymore.
My inital thoughts are:
1: has my donor status been revoked?
2: has it been removed or failed?
Normally I have this set to a shortcut key, I went to reassign
and could not find it in the list anywhere.
@dyiing
Muchly appreciated, I see some GUI changes in the update log today.
Can confirm, problem fixed.
Many thanks for your time.
@dyiing I have attemped at all GUI scales, fullscreen and windowed, I'll attempt to get video for you shortly.
It behaves as though the button is not there - and is clicking the element behind.
In prepping to make the video I backed up my waypoints and cleared them, I can add waypoints, provided there is not a full screen listed.
Link to video:
https://youtu.be/mLKNvS83n3Y
I don't seem to be able to add waypoints in 1.20.4 version.
It just selects the last waypoint a few lines down, possibly a scaling issue maybe?
Mods in use:
Baritone 1.20.4 (fabric)
Fabric-api
Litematica-Fabric-1.20.4 0.17.0
malilib-fabric-1.20.4 0.18.0
Other notes - I can see old waypoints, as I copied over the json from my previous install - unsure if that can cause this issue.
For now a notepad and pen will suffice, but would be nice to work this one out when you have a few minutes spare.
Just a minor issue that caused some confusion when I was trying to cover some terrain while afk.
When setting up looklock, the movementinfo mod seems to show only north or south, despite my player clearly facing another direction.
Happened when setting loolock to -180, -90, 90, and 0 in the yaw setting with pitch disabled.
not the biggest issue, but took me a few minutes to work out what was happening.
@omyl
A suggested workaround, using autoeject set to sugarcane, and make your farming area surrounded by hoppers or water conveyors.
You could use autocommand at a set interval to re-execute the .b farm (radius) command.
After accidentally clearing all my waypoints yet again,
I am shocked that there is no "are you sure" prompt before doing so.
Also the function to do that is in the traditional location of a close window "x"
This is what has led to multiple mistakes.
I have learnt to keep backups now, but I keep loosing stashes.
Last time I got lost 4 million blocks from home on an anarchy server.
I find some hacks on some servers will do this, try disabling everything, and re-enable one at a time till it crashes.
I have had a look and can't seem to find a similar suggestion.
I have the donor version.
Having just lost another full set of netherite gear to a lava pool in the nether, and this is about the 3rd time in 6 months - it would be really useful if Aristois could TP me out of there when my health hits a preset level.
As an amateur programmer, my brain suggests that it shouldn't be too hard to implement an "execute command when HP at X value" feature.
Autodisconnect also failed me, but it's a bit of an issue when one logs back in on top of lava again.
In terms of autocommand, I'm yet to figure out how to get commands to execute in a sequential order, so that I can cycle between locations such as from my mob farm, to my afk location.
I managed a workaround for this though, using /back.