To be honest, this took a bit longer to write than I expected. I guess I'm a bit rusty with Kotlin lol
I feel like this isn't the end game in terms of possibilities, and we can expand on this in the future, but I think it's also a solid start. For example, in the future we could also add an adventurer's log on the website using this very same data if we wanted to.
This feature is nice because it adds much more replay value with the additional commands and NPC kill data tracking.
This PR adds an NPC killcount system backed by a Map and three commands (::bosskc ::slayerkc ::kc), two are an interface display similar to our beloved ::players command and one is a search command that displays results in the chat.
Here is ::bosskc
Here is ::slayerkc
You can also search your KC per NPC by NPC ID or NPC name.
Here is ::kc goblin
What has been done?
Added an NPC kill count system, complete with 3 additional commands.
To be honest, this took a bit longer to write than I expected. I guess I'm a bit rusty with Kotlin lol
I feel like this isn't the end game in terms of possibilities, and we can expand on this in the future, but I think it's also a solid start. For example, in the future we could also add an adventurer's log on the website using this very same data if we wanted to.
This feature is nice because it adds much more replay value with the additional commands and NPC kill data tracking.
This PR adds an NPC killcount system backed by a Map and three commands (::bosskc ::slayerkc ::kc), two are an interface display similar to our beloved ::players command and one is a search command that displays results in the chat.
Here is ::bosskc
Here is ::slayerkc
You can also search your KC per NPC by NPC ID or NPC name.
Here is ::kc goblin![](https://i.imgur.com/MHHewpn.png)
What has been done?
Added an NPC kill count system, complete with 3 additional commands.
Has your code been documented?
Yes, of course.