Tags
Creators
Details
Licensed GPL-3.0-or-later
Published 5 months ago
Updated 6 days ago
All versions
1.1-beta
Beta
skript-variables 1.1-beta2 months ago 26
Compatibility
Minecraft: Java Edition
26.2
26.1.x
1.21.x
Platform
Paper
Changes
New Profiler tab at skript-variables.com showing which of your scripts, triggers and events cost the most server time
- Rank by script, by individual trigger, or by event, each with total time, share of the recorded window, run count, average and worst single run
- Spikes list: the 50 slowest individual trigger executions in the window, with a timestamp so you can line them up against lag reports
- Summary header with the recording duration, total measured time and the Skript version the profile was taken on
Commands
/skv profile start [seconds]: begins recording. Defaults to 60 seconds, maximum 600. Recording stops itself when the duration elapses/skv profile stop: stops early, then uploads the profile and gives you a clickable link that opens straight on the Profiler tab/skv profile status: shows how long the current recording has been going and how many trigger executions have been measured so far/skv profile upload: re-sends the last recorded profile. A failed upload no longer destroys the recording, and a profile cut short by a reload can still be sent- Starting a new recording cancels any pending auto stop from a previous one, so back to back recordings no longer stop each other early
/skv editornow attaches the last recorded profile to the session automatically, so the Profiler tab is populated without a second upload
Safety and correctness
- Recording stops automatically on
/sk reloadand/skript reloadbefore Skript can rebuild its triggers underneath the profiler - Recording stops automatically on plugin disable and server shutdown
- An early stop logs a console note telling you to run
/skv profile uploadto send the partial profile - If the trigger registry cannot be reached, the profiler still unwraps what it can and clears its own state instead of staying stuck in recording mode
Privacy
- Script source is never uploaded. The payload carries only script paths, line numbers, event descriptions and timings
- Profiles are deleted when their editor session expires
Notes
- New permission
skriptvariables.profile(default: op), separate fromskriptvariables.editor - Commands, functions and periodicals are not measured in this version. Only event triggers are
- Internals now covered by a JUnit 5 test suite
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:B9YXojvn:eM8ueM5Z"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:B9YXojvn:eM8ueM5Z"
}

