cabaletta / cabaletta/baritone
Persistence through disconnect
Open
- Dominant language
- Java
- Stars
- 9.2k
- Forks
- 2.1k
- Avg merge
- 4d 3h
- Merged PRs (30d)
- 3
Description
I think we can just filter out TickEvents with Type.OUT in PathingControlManager actually? Or does it have to be higher up, in PathingBehavior? I really don't know which is better. I tried both a while back and they both caused really strange issues on rejoin.
and i know for a fuckin fact that some people will demand that baritone resume on rejoin but nOT while in 2b queue ONLY when spawned back in, so it has to be even more complicated and detect that in order to be useful at all
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.