NitoriBot
 | |
| Name | NitoriBot |
|---|---|
| Main Developers | Parker2991 |
| Other Contributors | _ChipMC_ (v3.0.9 - v4.0.0), chayapak (v4.0.0-alpha - 4.0.0), _yfd (v4.2.3), aaa/ImFloriz (v6.0.3), PloatnO (v6.0.x), TurtleKid (v6.0.x) |
| Date Created | 22 November 2022 |
| Currently Maintained | yes |
| Project Details | |
| Library | MCProtocolLib for v9.x and above node-minecraft-protocol for v4 and above Mineflayer for v3.x and below |
| Language | Node.js (Java for v9.x) |
| Source Code | code.chipmunk.land |
| Version | v8.0.0-Reignite |
NitoriBot is a Kaboom/Savage Friends bot made by Parker2991. It might be the oldest still maintained node-minecraft-protocol bot.
It was originally written for fun but it was gradually maintained more and more, it was originally designed for Ayunboom before Creayun but development paused, until the developer recalled Chipmunk telling him about Kaboom.
History
Versions before v7 featured numerous contributions from other people, but at the beginning of v7's development cycle Parker2991 decided to minimize the amount of outside contributions.
Naming
A lot of names were considered in pre-release versions:
- ParkerBot
- DemonBot
- WoomyBot
- BoyfriendBot
Eventually, Parker2991 would settle on using FNFBoyfriendBot until v9.0.0, where it was renamed to NitoriBot in light of his newfound enjoyment of the Touhou Project. Additionally, the Touhou character it is named after enjoys tinkering with technology, and is one of Parker2991's favorite Touhou characters).
Development
v10 (Ironmouse)
Future release.
v9 (Night of Nights)
In this release, Parker2991 attempted to rewrite it in 2 different programming languages. At first, he attempted to rewrite it in TypeScript 5 times, but was not happy with the result and is now rewriting it in Java.
v8 (Reignite)
This release reintroduced some missing features (like command categories in the help command) not present in v7. It also featured some code cleanup.
v7 (Game Theory)
A lot of stuff was removed from this release, but not much else is currently known about it.
this version was named specifically after the Game Theory series on youtube due to Matpat leaving the series.
v6 (Graffiti Groovin')
A code cleanup.
v5 (KB QT Termination)
Ill-fated optimization and code clean-up.
v4 (FNFBoyfriendBotX Ultimate)
During the development of the v4.x series, several revisions of the source code were lost due to _yfd doxxing an admin of AMCForum who provided the hosting for the bot.
This was the first revision of the bot not to be based on ManBot v2.
Parker2991 attempted to warn the administrators of AMCForum that adding an IRC bridge to the Discord server could lead to doxxing, however his warnings fell on deaf ears.
He was blamed for the doxxing, and as such he lost access to AMCForum's hosting, along with revisions v4.0.1-v4.1.9.
cxvqo is apparently attempting to rekindle this drama as he apparently has created an account on AMCForum, but their alias is unknown at this time.
This was a complete rewrite of the entire bot from mineflayer to node-minecraft-protocol.
v3 (Sky Remanifested/Blue Balled Corruption)
This release added self-care and some other features that were deemed by Parker2991 to be "useless" in retrospect.
Originally, this release was supposed to include v4's node-minecraft-protocol rewrite, however the rewrite was not done before the deadline.
v2
Added miscellaneous features and commands to the bot which were deemed to be bloat, in retrospect, by Parker2991.
v1 (FNFBoyfriendBot)
Console-only.
v0 (Prototype)
this was the prototypes based on ManBot made by Logintimedout which is where the names parkerbot, demonbot, woomybot, and boyfriendbot came from.
Versioning
Parker2991 creates a major release of the bot whenever he feels it's ready, which is usually every few months during active development.
The minor version is incremented every time an additional feature is added, and the patch version is incremented every time a bug is fixed.
New major versions also feature codenames.
Known bugs
The bot has a lot of memory leaks, causing memory usage to balloon to ~2-3GB. According to Parker2991, this is because the codebase is almost 3 years old.
