Tags
Creators
Details
All versions
0.9.1
Release
PySpigot 0.9.1last year 266
Compatibility
Minecraft: Java Edition
1.21–1.21.8
1.20.x
1.19.x
1.18.x
1.17.x
1.16.x
Platform
BungeeCord
Changes
Additions in this version:
- Added a new
PluginMessageManagerto interface with Spigot's plugin messaging framework and send/listen for plugin messages - A notification is now sent when using a SNAPSHOT version as opposed to a release version
- A warning message is now displayed if a tab complete function returns something other than a list
Changes in this version:
- PySpigot is now compiled with Java 21. From this version onwards, PySpigot will only work on Java 21+
- PySpigot now uses the Kyori Adventure API for messaging
- Improved the information displayed in the
/pyspigot infocommand - Logging improvements
- A lot of code cleanup, reorganization, and improvements
- JavaDocs improvements
Bugs fixed in this version:
- Fixed an issue where duplicate scripts/project could be loaded, or the same script/project could be loaded more than once, if case-variant names were passed
- Fixed an issue where the
script_options.ymlfile was never loaded on the BungeeCord platform - Fixed an error that occurred when listeners, commands, etc. were registered from a utility module or a non-main project file
- The main script displayed in the
/pyspigot infocommand now show the correct script file for single-file scripts - Fixed a memory leak associated with fetching the latest plugin version from Spigot
- Fixed issue where command registration parameters were not recognized
- Fixed an issue where the configuration files were saved before the plugin folder was initialized/created
- The version checking system now evaluates SNAPSHOT versions as older than release versions of the same number
Supplementary resources
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:G91y7RYh:CZVFOBOR"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:G91y7RYh:CZVFOBOR"
}

