S32Core

A framework datapack that allows in-game configuration, the ability to change the colour of your name from a chat-based menu, and holds tags and other code that can be used by my other datapacks. It's free to use for other datapack creators to steal code from, add as a requirement, or just include it in their datapacks for ease of setup.

Operators:

• As there's no way to specify operators in commands, the scoreboard s32_op is added to send reload and config messages to players marked with s32_op=1.

• This can be accessed with the command /function s32:op, which requires Minecraft operator status to do.

Namecolor:

• When a player does not have the score s32_init=1 (all new players), they will receive the namecolor message in chat. By setting this score to zero, they can get the message again.

• By clicking the [here] button, a name color picker menu will appear in chat.

• Alternatively, the command /trigger s32_namecolor set 100 will open the menu.

• The menu will allow a player to join a team for one of all of the available team colors.

• This will conflict with any datapack that adds players to teams, for example a greyed out AFK name, which would move the player to an active-player team or just make them leave the AFK team as of returning from AFK. As such, their name color would be reset.

Datapack Setup:

• #s32:tick (s32/functions/tick.json) adds functions to the Minecraft tick event. As with tick, this can allow you to develop your datapack without having to include S32Core until the end, or add it as a requirement separately. It also means that you can stick to the S32 json files without having to go back and forth, meaning generally simpler ease of use

• #s32:tick (s32/functions/load.json) adds functions to the Minecraft load event

• #s32:config (s32/functions/config.json) adds a global chat-based configuration menu accessible via command and at reload to players marked as operator. Add your config tellraw function to the end of this list (see s32:config as an example)

• #s32:loop (s32/functions/loop.json) runs commands every second. Add your function to the end of this list.

Notes:

• This datapack runs some commands every second. This may, but is highly unlikely to, have an effect on TPS (ticks per second), particularly in multiplayer servers.