Corex
A high-performance, compiled scripting engine for Paper / Folia / Velocity. Simple, automated, convenient - meet Corex.
⚡ Compiled at startupScripts are parsed once. Every call runs prebuilt bytecode - performance does not depend on the number of scripts. |
🏷️ Tags instead of variables
|
💾 Persistent flagsA flag is written with a single command - on a player, a block, or globally. Survives restarts. Supports TTL: data deletes itself after a set time. |
🌿 Folia supportCorex tracks threads and switches between regions automatically. Scripts are written as usual - no special handling required. |
🌐 Velocity - same syntaxProxy scripts use the same language. Cross-server logic, global data, high performance. |
🔄 Hot reload
|
Script Queue
Every script runs in its own isolated queue. While one queue is waiting (for a delay, a command execution, or a region switch) - the others keep going. Each queue has its own variables and its own position in the code.
.jar lifecycle
One .jar file runs on Paper, Folia and Velocity. On load, the server detects the platform and reads the right config.
Command syntax
Every command starts with -, followed by the command name and arguments. Arguments come in two types: linear - passed as a plain value ("Some text"), and prefix - passed as key:value (targets:<player[_TIZIS_]>). Tags can be used in any argument - they are evaluated at the moment the command runs.
Tag syntax
A tag is a chain inside < >. Read left to right: player - who, .name - their name (string), .length - the length of that string (number), .isMoreThan[10] - whether it is greater than 10 (boolean). Each part receives the result of the previous one and returns a new value. The final result is substituted wherever the tag is written.
