Links
Tags
Creators
Details
0.2-SNAPSHOT
Compatibility
Changes
Fabric.SK 0.2-SNAPSHOT allows Minecraft servers and clients running Fabric to load and execute Skript-style scripts without requiring Bukkit, Paper, Spigot, or any Bukkit-based API.
Features
Script Support
.skscripts.heavyskpackages
Heavy Skript
A .heavysk file is simply a renamed ZIP archive.
Example:
Economy.heavysk
Contents:
manifest.json
main.sk
commands.sk
events.sk
Supported manifests:
manifest.jsonpackage.skmeta(JSON5)manifest.sk.toml
Commands
Main Command
/fabricskript
Aliases:
/skript
/fsk
/sk
Script Management
/fsk load <script>
/fsk unload <script>
/fsk reload <script>
/fsk reloadall
Examples:
/fsk load welcome.sk
/fsk reload economy.heavysk
Information
/fsk list
/fsk info <script>
/fsk version
/fsk help
Validation
/fsk validate <script>
Example:
/fsk validate welcome.sk
Errors
/fsk errors
Displays recent parser and runtime errors.
Syntax Correction
/fsk toggle syntaxcorrect auto <script>
/fsk toggle syntaxcorrect partial <script>
Modes:
| Mode | Description |
|---|---|
| auto | Automatically fixes simple syntax issues |
| partial | Suggests fixes only |
Script Folder
Fabric.SK automatically creates:
.minecraft/fabricsk/scripts/
Example:
fabricsk/
└── scripts/
├── welcome.sk
├── admin.sk
└── economy.heavysk
Example Script
command /hello:
trigger:
send "Hello World!"
Example Event
on join:
send "Welcome!"
Error Reporting
Fabric.SK includes:
- Line mapping
- Error codes
- Context display
- Error logs
Example:
[Fabric.SK] FSK001
File: welcome.sk
Line: 14
sends "Hello"
^
Unknown syntax
Error logs are stored in:
.minecraft/fabricsk/logs/script-errors.log
Configuration
Config file:
.minecraft/config/fabricsk.json
Example:
{
"version": "0.2-SNAPSHOT",
"autoLoadScripts": true,
"enableHeavySk": true,
"enableErrorLogging": true
}
WARNING Fabric.SK 0.2-SNAPSHOT is an experimental development build. APIs, script syntax, and package formats may change before the 0.2.0 release. Please report any bugs at https://github.com/DemoDev-Original/Fabric.SK/issues.
Projects on Modrinth are automatically available through a Maven repository for use with JVM build tools such as Gradle. To learn more about the Modrinth Maven API, click here.
Note: When available, you should use the creator's maven repo instead as it will have transitive dependency information that the Modrinth Maven API does not. You may also end up with duplicate dependencies if you use a mix of Modrinth and non-Modrinth Maven repositories for your dependencies, because the group identifier will be different when served through the Modrinth Maven API.
Maven coordinates:
Version ID:
build.gradle:
repositories {
exclusiveContent {
forRepository {
maven {
name = "Modrinth"
url = "https://api.modrinth.com/maven"
}
}
// forRepositories(fg.repository) // Uncomment when using ForgeGradle
filter {
includeGroup "maven.modrinth"
}
}
}
// Standard Gradle dependency
dependencies {
implementation "maven.modrinth:f4UIvepu:G6b1dWeK"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:f4UIvepu:G6b1dWeK"
}

