Introduction

Why learn Kether?Copy Anchor Link

You may have seen configuration like this in quest, skill or dungeon plugins:

tell "Welcome to the server!"
command inline "give {{ sender }} diamond 1"

Or something a little more involved:

if check money >= 100 then {
  take money 100
  command inline "give {{ sender }} diamond 1"
  tell inline "{{ sender }}, your exchange was successful"
} else {
  tell "Not enough money"
}

These lines are Kether statements.

In short: Kether makes logic configurableCopy Anchor Link

Giving a reward when a button is clicked, charging money when a condition is met, or taking different paths based on a player's level all require logic. When that logic is hard-coded into a plugin, changing it usually means waiting for the developer to update the plugin.

Kether turns that logic into statements you can write and edit in your configuration. Think of it as:

A small language for describing what to do and under which conditions to do it.

Where will you use it?Copy Anchor Link

If you regularly:

• Customize quest, dungeon or skill behavior.
• Edit plugin configuration rather than write plugin code.
• Copy someone else's scripts and adapt them to your server.

You may already be using Kether without knowing its name. Many plugins use it to configure rewards, conditions and workflows. Learning the basics helps you:

1. Read configurations and examples to understand what they do.
2. Customize rewards, conditions and messages for your own server.
3. Write your own logic wherever a plugin supports Kether.

Is it difficult to learn?Copy Anchor Link

No. Kether is designed to let people who are comfortable editing configuration also express logic. To get started, you only need to:

• Understand a simple instruction, such as giving a player a sword.
• Put steps in order: do A, then B.
• Follow an “if…otherwise…” condition.

The following tutorials start with the basics and show you how to read, change and combine Kether statements. You do not need programming experience or knowledge of the internals: just try the examples and make small changes.