CMT comes with an extensive API to integrate other plugins within CommandTimer

This documentation is still in progress and far from done. If you need help, ask help on the Discord server

Extensions always start with one simple class which needs to extend ConditionExtension. This will be the base for your extension and the place where all the conditions will be registered.

You will see that a few fields need to be defined:
conditionGroupName: This is basically the name for your extension, try to find something unique that won't conflict with someone else
description: This is a simple description of the extension. Each entry in the array represents a line in the CommandTimer GUI
author: This is your name. Separate with comma's if there are multiple authors (e.g. PlayBossWar, Vertex)
version: This is the current version of your extension
rules: There are your conditions, more on this later
Interacting with the core API

Directly interacting with the core of CommandTimer is not very common but can be used to create interesting behavior. The recommended way remains using extensions.

A full documentation about this is not available yet, but you should be able to get the CommandTimer instance with
CommandTimerPlugin cmtInstance = Bukkit.getServer().getServicesManager().load(CommandTimerPlugin.class)

CommandTimerPlugin cmtInstance = Bukkit.getServer().getServicesManager().load(CommandTimerPlugin.class)

Don't forget to add CommandTimer as a dependency in your plugin.yml to prevent your plugin from loading before CommandTimer does

Interacting with the core API and using the extension is not possible in the same way you can with a plugin. You can however use getCommandTimerPlugin() (available in ConditionExtension) to get the current CommandTimer instance and start from there.

Use the paper in your task detail to change the name.
The name should never include spaces
Never manually change the file names in the folders

Each task should have an interval or a specific time. Interval and specific time are 2 very different things so you should understand what the differences are.

An interval is a set value (x days, x hours, x minutes, x seconds) after which the commands will be executed. This interval never changes, so if you set the interval to 4 minutes, it will execute the commands you configured every 4 minutes. The image below shows you what the interval menu looks like:

Specific time simply represents a point in time, a specific time of the day, or a specific time of the day on Tuesday, or during the weekend.
You can have as many specific times as you want, there is no limit to it.
You can also create ranges if you want for example a command to execute between 13:00:00 and 15:00:00 every 5 minutes.

Use the /cmt command to create a new task. A GUI will open that looks like this:

Click on the paper. You will now see a list of all your created tasks. If you just installed CommandTimer this will be empty.

Click on the anvil to create a fresh new task.

If you didn't create a task yet, create one first by following these steps.

Open your list of tasks again (/cmt -> paper) and left-click on the task you want to edit. You will see this menu:

Here is an overview of what all the items do: