Physics
Milestone on deck per feature roadmap
- [ ] Basic physics C interface
- [ ] Python plugin
- [ ] Walk
- [ ] Fall
- [ ] Jump
- [ ] Sprint
- [ ] Swim
If the ticker Plugin from SpockBot were ported to Rikerbot, how much of this would be appropriate to port from the SpockBot implementation of physics?
The SpockBot implementation is kinda a mess, and very slow even after considering its in pure Python. The timer/ticker plugins are trivial to write and I should have C++&Python versions of them in today. I was busy getting cpp-nbt fully unit tested because I never want to deal with a crap bug like #20 again.
The ground work for getting collision working is already here in the vec3.hpp and aabb.hpp, just getting the bot to fall to the ground won't be too hard. After that I think I intend to copy the behavior out of mineflayer, because understanding the MC physics code even with mappings is non-trivial.