Skip to content

replaced naive trapdoor interact with baritone pathing and interaction to keep rotations correct when interacting.#17

Open
CrisisSheep wants to merge 5 commits into
leonetics:mainfrom
CrisisSheep:main
Open

replaced naive trapdoor interact with baritone pathing and interaction to keep rotations correct when interacting.#17
CrisisSheep wants to merge 5 commits into
leonetics:mainfrom
CrisisSheep:main

Conversation

@CrisisSheep

Copy link
Copy Markdown
Contributor

the bot now uses baritone pathing and interaction which keeps the look rotations correct so that there are less false pulls that are reported as working.

still use the old interact system for offline pulling to keep delay from login to pull as low as possible, instead we just update the look rotation every tick to keep the bot looking at the trapdoor until the owner logs on.

fixed the bot saying that it has pulled successfully when it hadnt (only for online pulls), now it will notify the player the pull failed if its 3s of reattempts also fail.

fireClick previously sent the interact packet and unconditionally declared
the pull successful, with no rotation toward the trapdoor and no check that
the click actually landed - it could silently miss and still whisper
'Pulled'.

Splits into two paths depending on whether the owner was already online
when positioning finished:
- Already online: uses Baritone's rightClickBlock, which reaches the block
  correctly regardless of intervening blocks, rotates and clicks atomically
  at a priority that beats Spook, and verifies the interact resolved against
  the right block via ClickResult before declaring success. Bounded by a 3s
  confirmation timeout since Baritone's own retry limit only covers path
  calculation failures, not stuck interact attempts. On a confirmed miss or
  timeout, reports failure and tells the player to re-request rather than
  retrying automatically.
- Owner comes online after waiting: kept as the raw, zero-latency packet
  send (unverified) since routing this through rightClickBlock's InputManager
  round-trip would cost at least one extra tick right when responsiveness
  matters most. Correctness instead comes from continuously re-facing the
  trapdoor every tick for the whole wait, so the bot is already aimed
  correctly the instant the owner logs in instead of wherever Spook or idle
  behavior last left it pointed.
@CrisisSheep

Copy link
Copy Markdown
Contributor Author

fixed race condition causing pearl chambers to be mis-counted for whispers. also increased antispam length to stop antispam catching it

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant