Tags
Creators
Details
0.2.0
Compatibility
Changes
We're finally releasing the 2nd beta version of Streamlabs Integration! This release contains a lot of new features, and will seamlessly migrate your old configuration file to the new systems introduced. Make sure to check out the documentation to see how to use the new additions!
Here's a full changelog of the features added:
- "messages" and "commands" have been replaced with a new, more powerful "steps" system
- A lot of steps have been added, allowing you to create way more complex and versatile logic. You can now create delays, loops, generate random items and players, extract data from messages, and much more!
- Placeholders now have different types, e.g. normal placeholder look like this:
{placeholder}and custom placeholders like this:{!placeholder} - Functions have been added, allowing you to create reusable step sequences
- Configurations can now be migrated when the plugin is updated
- Rate limiters can now have events that trigger when a rate-limit occurs
- Actions are now executed asynchronous from the server thread, meaning an action wont't freeze the server while e.g. running a delay step
- Reworked the default configuration with a lot more examples
- Improved issues and error handling
NOTE: If you've been using an experimental testing version adding support for the Streamlabs Loyalty Store, don't download the default release file, instead open the release page on modrinth and download the 2nd experimental jar file!
Supplementary resources
| File | Type | Size | |
|---|---|---|---|
| StreamlabsIntegration-0.2.0_experimental-loyalty-store.jar | Unknown | 1.35 MiB |
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:TJXZf39H:bQzpTk9C"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:TJXZf39H:bQzpTk9C"
}

