Created my bot. I learnt how to use Sqlite, Typescript, and Discord.js today.

DEVLOG #8: Ouch, that hurts!

I added a Roles system (PARTICIPANT, SPECTATOR, STAFF, ADMIN) as well as setRole(Player player, Role role), getPlayers(Role role) and updateState(Player player) You now automatically get assigned spectator on death and participant on event start. This system is still very primative and I will adjust how roles are managed in the future as required.

Challenges:

I spent 10 minutes debugging because of a typo in my messages.yml causing the showTitle() to fail because of an invalid message. I’m going to add null saftey to my MessageManager to return some error if a configuration value is null, to help me catch these earlier in the future.

Todo:

• Role Displaynames
  • Add displaynames to the roles in the config (For use in chat formatting. This will be difficult as I will need a raw text as well as a stylised one)
• Update Chat Formatting to use actual roles
• Setup staff role permissions

DEVLOG #7: OOOO Shiny

I’ve added a lot of stuff in one hour!

MESSAGES UPDATE

You can now use predefined placeholders in the messages.yml in the format of {index}. These are replaced by predetermined variables.

CHAT FORMATTING

Chat formatting has been added! I plan to implement a placeholder for the users role soon, right now it’s just hard-coded in the messages file as PARTICIPANT <username> ▶ <message>

SUBCOMMANDS: EXTENDED

Added tab completion to the subcommand’s subcommands! More specifically the kit actions are auto completed now.

ROLES PREP

Began preparation for event roles (Participant, Spectator, Staff, Admin). All this means so far is adding an enum

BUG FIXES

Fixed some bugs, most notably where my messages file would take two restarts to overwrite the updated version due to me initializing my file too soon.

DEVLOG #6: Kits II

Implemented tab completion for the kits sub commands sub commands. Added kit deletion and kit listing as well. Next steps are recoding the Tab Completer in preperation for the phase management system

DEVLOG #5: Hey, where are my items?

I’ve added a functioning kits system to the plugin! You can now save your inventory including armor and offhand slot as a kit by using /event kit save <name>, and load a kit by using /event kit get <name>. Kits are saved to /kits/<kit>.yml in my plugins data folder. It has support for enchants, custom display names, and persistent data container data.

DEVLOG #4: %placeholders%

I’ve implemented a PlaceholderAPI integration to the project, with current expansions containing %event_state%, and `%event_version%. I plan to implement placeholders for things such as border sizes, times, etc.

DEVLOG #3: Messages, messages, and more messages

Implemented a messages.yml for storing the messages used in the plugin, as well as a /event reload subcommand to reload the configuration. I will eventually move MessagesManager.java to a dedicated ConfigurationManager when I require more files, but for now it works fine. I also tidied up the formatting and pushed my changes to the github.

DEVLOG #2: Commands!

I created a BaseCommand.java to contain the code for the base /event command, as well as a simple tab completer for the arguments. I also started work on the EventManager which will hold values such as the event state.

DEVLOG #1: Event State

I’ve added an enum to store all of the event states. I had to learn how to use and create enums in Java for this, and they will be very useful in future development.

DEVLOG #0: Setup

Setup the initial plugin using the Paper template and shared the project on GitHub