Skip to content
Flint
Dokumentation
Going further

Coming from Skript

How Skript concepts and popular addons map to Flint.

Flint is a new language, so Skript .sk files do not run on it. The concepts carry over, though, and most things that need a Skript addon are built into Flint.

Side by side

on join:
    if {joins::%player's uuid%} is not set:
        set {joins::%player's uuid%} to 0
    add 1 to {joins::%player's uuid%}
    send "Welcome back, %player%!" to player
persist joins = {}

on player.join:
    joins[player.uuid] = (joins[player.uuid] or 0) + 1
    send "Welcome back, {player.name}!" to player

Concepts

Skript Flint
{coins::%player's uuid%} persist coins = {} then coins[player.uuid]
{_local} any variable assigned inside a block
%player% in text {player.name}
wait 5 seconds wait 5 seconds (pauses only this script)
every 5 minutes: every 5 minutes:
command /heal <player>: command heal(target: player):
cooldown: 30 seconds cooldown 30 seconds
executable by: players executor "player"
function f(x: number) :: number: fn f(x):
cancel event cancel
loop all players: for p in players.all():

Addons you no longer need

Skript addon Flint
skript-reflect on event "ClassName":, value.any_java_method(), java.type(...) (Java access)
skript-gui, TuSKe import menus (Menus and UI)
skript-yaml, file addons import files (JSON), import storage, import db
skript-db import db with connection pooling, never blocking
SkBee (boss bars, scoreboards, recipes, NBT) bossbars, sidebar, recipes, item.set_tag(...)
Vault hooks import economy
PlaceholderAPI hooks import placeholders
SkQuery (regex, misc) import regex, built-in format() and sum()
region addons location.within(corner1, corner2)

What is different

  • Indentation and syntax follow Python, not English sentences. Expressions are short and unambiguous: player.health, items.of("diamond", 3).
  • Imports. Functionality is grouped in modules you import. Nothing is loaded that no script uses.
  • Errors are found at load. A typo in an event, a module or a variable name is reported by /flint reload (and by the editor), not when the code finally runs.
  • Performance. Scripts are compiled to bytecode; wait and database calls do not reschedule the whole trigger.