Modification

This chapter focuses on the steps required to alter AT's souce code, e.g. for disabling specific features or implementing it into your project. If this is not what you want, consider checking out the Advanced section to learn more about changing the way AT works natively, without any changes.

Note: Changing AT's code without knowing what you are doing can seriously mess up your world and potentially break AT permanently! Please be advised to back up data that you care about before attempting any code modification.

Default configuration

Changing the default values is useful if you plan to use this timer on multiple (new) worlds. This will ensure that wherever you use this modified data pack, AT will always default to the settings you defined. On initialization, AT will always load its default configuration values:

• Render type: SAZ

• Style type: animated

• Animation: blue-pink

• Bold: true

• Italic: false

• ...

These values are sprad over three files and can be easily modifed, if you know where to look:

Path from AT root directory	Setting
/data/at-main/function/init.mcfunction	Render & style type
/data/at-misc/function/configuration/static.mcfunction	Colors, bold & italic style
/data/at-misc/function/configuration/animated.mcfunction	Animation, speed, directon ...

Often times, AT's configuration settings are not stored as strings, but rather as scoreboard values in the at_s_config objective. This includes the following config attributes:

Setting in at_s_state	Description & possible values
render	Render type: 0=CAZ, 1=SAZ, 2=SNZ
style	Style type: 0=static, 1=animated
static_bold1	Primary bold: 0=false, 1=true
static_bold2	Secondary bold: 0=false, 1=true
static_italic1	Primary italic: 0=false, 1=true
static_italic2	Secondary italic: 0=false, 1=true
animated_bold	Animation bold: 0=false, 1=true
animated_italic	Animation italic: 0=false, 1=true
animated_speed	Animation speed: tick count
animated_direction	Animation direction: 0=left-to-right, 1=right-to-left

If you look at the .mcfunction files mentioned above, most of the settings should be self-explanatory, as AT's code uses lots of comments to describe what things do. If you are still having troubles, take a look at the following examples.

Example 1: Default to statically pink

Result of change:

• Style type will always be static

• Pink color instead of white (default)

• Fully italic style, not bold

Steps to reproduce:

1. Open file: /data/at-main/function/init.mcfunction

2. Set style type - change line below "# Style type" to:

function at-misc:configuration/static

1. Open file: /data/at-misc/function/configuration/static.mcfunction

2. Set timer color primary & secondary - change lines below "# Colors" to:

data modify storage animated-timer:data at.configuration.style.color1 set value "#ff55ff"

data modify storage animated-timer:data at.configuration.style.color2 set value "#ff55ff"

1. Disable bold styles - change lines below "# Bold" to:

scoreboard players set static_bold1 at_s_config 0

scoreboard players set static_bold2 at_s_config 0

1. Enable italic styles - change lines below "# Italic" to:

scoreboard players set static_italic1 at_s_config 1

scoreboard players set static_italic2 at_s_config 1

Example 2: Default to green-fade animation

Result of change:

• Default animation will always be green-fade

Steps to reproduce:

1. Open file: /data/at-misc/function/configuration/animated.mcfunction

2. Set animation - change line below "# Animation" to:

data modify storage animated-timer:data at.configuration.style.animation set value "green-fade"

Example 3: Default to white-aqua animation

Result of change:

• Render type will always be CAZ

• Default animation: white-aqua

• Animation speed: 3 ticks

• Left-to-right instead of right-to-left direction

Steps to reproduce:

1. Open file: /data/at-main/function/init.mcfunction

2. Set render type - change line below "# Render type" to:

scoreboard players set render at_s_config 0

1. Open file: /data/at-misc/function/configuration/animated.mcfunction

2. Set animation - change line below "# Animation" to:

data modify storage animated-timer:data at.configuration.style.animation set value "white-aqua"

1. Decrease animation speed - change line below "# Speed" to:

scoreboard players set animated_speed at_s_config 3

1. Swap animation direction - change line below "# Direction" to:

scoreboard players set animated_direction at_s_config 0

Removing specific trigger scoreboards

Although you can easily remove all trigger scoreboards (see Triggers), you may only want to remove some of them. This usually involves editing three files:

Path from AT root directory	Purpose
/data/at-trig/function/add.mcfunction	Create all trigger scoreboards
/data/at-trig/function/remove.mcfunction	Delete all trigger scoreboards
/data/at-trig/function/dist.mcfunction	Tick every trigger function

Before any code modification happens, be sure to disable all trigger scoreboards:

/function at-dcfg:triggers/disabled

The following examples demonstrate how the removal can be accomplished. After that, reload your world to apply the code changes.

Example 1: Remove "mode" trigger

Steps to reproduce:

1. Open file: /data/at-trig/function/add.mcfunction

2. Search for line that contains "add mode trigger"

3. Comment it out:

#scoreboard objectives add mode trigger

1. Open file: /data/at-trig/function/remove.mcfunction

2. Search for line that contains "remove mode"

3. Comment it out:

#scoreboard objectives remove mode

1. Open file: /data/at-trig/function/dist.mcfunction

2. Search for line that contains "/mode"

3. Comment it out:

#function at-trig:conf/mode

Example 2: Remove animation-related triggers

Steps to reproduce:

1. Open file: /data/at-trig/function/add.mcfunction

2. Comment out lines below "# Scoreboards / Trigger / anim" section:

#scoreboard objectives add list-animations trigger

#scoreboard objectives add load-animation trigger

1. Open file: /data/at-trig/function/remove.mcfunction

2. Comment out lines below "# Scoreboards / Trigger / anim" section:

#scoreboard objectives remove list-animations

#scoreboard objectives remove load-animation

1. Open file: /data/at-trig/function/dist.mcfunction

2. Comment out lines below "# Anim" section:

#function at-trig:anim/list

#function at-trig:anim/load

Example 3: Remove profile-related triggers

Steps to reproduce:

1. Open file: /data/at-trig/function/add.mcfunction

2. Comment out lines below "# Scoreboards / Trigger / prof" section:

#scoreboard objectives add delete-profile trigger

#scoreboard objectives add list-profiles trigger

#scoreboard objectives add load-profile trigger

#scoreboard objectives add save-profile trigger

#scoreboard objectives add view-profile trigger

1. Open file: /data/at-trig/function/remove.mcfunction

2. Comment out lines below "# Scoreboards / Trigger / prof" section:

#scoreboard objectives remove delete-profile

#scoreboard objectives remove list-profiles

#scoreboard objectives remove load-profile

#scoreboard objectives remove save-profile

#scoreboard objectives remove view-profile

1. Open file: /data/at-trig/function/dist.mcfunction

2. Comment out lines below "# Prof" section:

#function at-trig:prof/delete

#function at-trig:prof/list

#function at-trig:prof/load

#function at-trig:prof/save

#function at-trig:prof/view

Custom animations

Before creating a custom animation, please take a look at the code in /data/at-misc/function/animation/load.mcfunction as this is the place where all animations are stored. Each animation (including your new one) must follow this NBT path scheme:

at.animations.<animation-name>

An animation generally consists of five NBT tags:

Name of NBT tag	Type	Description
id	Integer	Numeric ID; used for animation list command
count	Integer	Number of steps (colors) per animation
title_length	Integer	Length of animation title / name
rotation_type	Integer	Determines how to print animation (list command)
colors	List	Stores the HEX colors that make up the animation

The key is to find two (or more) colors that match and then generate a gradient between them. You can do this with an external tool.

Note: AT does not loop around automatically. Going just from color A to B isn’t sufficient - a full animation should look more like this: A > B > A.

The following example should serve as a guide on how to implement a new animation.

Example 1: Animation white-black

Steps to reproduce:

1. Generate a gradient using the tool mentioned above (A > B; 20 colors are recommended)

2. Copy the colors and reverse them to get your animation (A > B > A; at least 40 in total)

3. Determine animation ID: unique, used for output of animation list command

4. Determine colors count: 40 if you use the recommended values

5. Determine length of title: 11 for "white-black"

6. Determine rotation type: 0 when following A > B > A pattern

7. Put HEX colors into colors list

8. Paste complete animation into animation load file (mentioned above):

data modify storage animated-timer:data at.animations.white-black.id set value 100

data modify storage animated-timer:data at.animations.white-black.count set value 40

data modify storage animated-timer:data at.animations.white-black.title_length set value 11

data modify storage animated-timer:data at.animations.white-black.rotation_type set value 0

data modify storage animated-timer:data at.animations.white-black.colors set value ["#ffffff","#f0f0f0","#e1e1e1","#d2d2d2","#c3c3c3","#b5b5b5","#a7a7a7","#999999","#8b8b8b","#7e7e7e","#707070","#636363","#575757","#4a4a4a","#3e3e3e","#333333","#272727","#1d1d1d","#121212","#000000","#000000","#121212","#1d1d1d","#272727","#333333","#3e3e3e","#4a4a4a","#575757","#636363","#707070","#7e7e7e","#8b8b8b","#999999","#a7a7a7","#b5b5b5","#c3c3c3","#d2d2d2","#e1e1e1","#f0f0f0","#ffffff"]

1. Reload your world to apply the changes

Integration

Considerations to make when integrating AT in one of your projects:

• What kind of timer and style configuration do I need and how do I implement it?

• Do I want something to happen if the timer pauses / continues / reaches zero?

Configuration

Part of the configuration work for AT can be done via functions in at-conf. Although this just works, it can be tedious or inefficient to run the same command twice or in a specific order to get the style you prefer.

Depending on what you are trying to do, it may make sense to look at functions in at-dcfg namespace. Any command there just does what it’s named like and none of them give any output in form of tellraws.

Extraction

The namespace at-dext contains four functions that are automatically invoked when a specific action happens within the timer:

Function	Invoked at
at-dext:continue	Timer start or continue via /function at:continue or trigger
at-dext:pause	Timer pause via /function at:pause or trigger
at-dext:reset	Timer reset via /function at:reset or trigger Timer reboot via /function at:reboot or trigger
at-dext:zero	Timer in mode DOWN reaches zero