All versions
2.0.0
Release
skript-db 2.0.0last month 254
Compatibility
Minecraft: Java Edition
26.3
26.2
26.1.x
1.21.x
Platforms
Bukkit
Folia
Paper
Spigot
Changes
Rewrite for Minecraft 1.21 to 26.x with Skript 2.14 and newer.
Added
transaction on {sql}:section: all statements inside run in one transaction, committed at the end, rolled back on the first error.with batch arguments {_rows::*}: runs a statement once per sub list in a single round trip.with arguments ...now also works with literal values,store the generated keys in {_id}returns the first generated key.- List expressions inside a statement expand to one parameter per value, for
IN (...). - Folia-safe scheduling and
folia-supported: truefor Folia based Skript forks.
Changed
- Result values are converted for Skript: timestamps become dates, decimals become numbers, UUIDs and binary data become text, SQL arrays become lists.
last sql erroris tracked per trigger, so concurrent queries no longer see each other's errors.- Result lists are emptied before a new result is stored.
- Effects that cannot run after a delay (such as
cancel event) are reported at parse time when they follow anexecute. - Runtime errors such as an unset data source are reported with script and line.
- New config keys
pool-size,connection-timeout,query-timeoutandtransaction-timeout; old config files keep working.
Fixed
max-connection-lifetimewas written into a comment and never read.- Connection pools were never closed on reload or shutdown.
- Data sources loaded from saved variables created a second, unconfigured pool.
- Generated keys were never returned for inserts.
- Placeholder counting for
with argumentscounted question marks inside strings and comments. - Wrong warning about expressions surrounded by quotes.
Removed
- The
complete of sql queryevent andsql queryexpression.
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:wQPcgT79:zodZNVNM"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:wQPcgT79:zodZNVNM"
}

