Tags
Creators
Details
2.0.0
Compatibility
Changes
This is a major release. If you find any bugs, report them in the issue tracker or on the Discord Server
☁️ Information 🚩:
- You will need a Redis Database
- You will only receive support if you are using the latest versions of Minecraft, Skript, and SkRedis. Additionally, you must have a basic understanding of Redis. I will not provide assistance with Redis in any way.
🍽️ Patches & Fixes 🧑🏼🍳:
If you want to suggest a feature, let me know that in the issue tracker!
-
Updated dependencies
-
Now enforcing 1.21.8 with changing the api-version from
1.21to1.21.8because we are using 1.21.8 only features (https://github.com/byPixelTV/SkRedis/commit/da94eac9fdc7c0d9793b9c86fb43294a8fd72d40) -
Switch from Jedis to Lettuce (https://github.com/byPixelTV/SkRedis/commit/da94eac9fdc7c0d9793b9c86fb43294a8fd72d40)
-
Add
custom redis messageevent andsend custom redis messageeffect (https://github.com/byPixelTV/SkRedis/commit/da94eac9fdc7c0d9793b9c86fb43294a8fd72d40) -
improved performance because we are now using Lettuce and their reactive coroutines api for pub/sub (https://github.com/byPixelTV/SkRedis/commit/da94eac9fdc7c0d9793b9c86fb43294a8fd72d40)
-
Full Changelog: https://github.com/byPixelTV/skRedis/compare/v1.2.3...v2.0.0
⛏️ Minecraft Support 🎮:
- SkRedis is only compatible with Minecraft version 1.21.8
- I will only support the latest release of Minecraft, this mean that 1.21.8 is supported, but 1.21.1 isn't! If you want to get official support, you have to use the latest version of Skript, SkRedis and Minecraft!
📝 Skript Support 📑:
- This version requires Skript 2.12+ to correctly run on your server
🔥 Other stuff 🎉:
- If you find any bugs tell me on Discord or use the GitHub issue tracker. Cheers! 🥂
💻 Development Builds 🌐:
- Development Builds: https://ci.bypixel.dev/job/skredis/
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:3R33dfbs:tHMk2vNq"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:3R33dfbs:tHMk2vNq"
}


