Tags
Creators
Details
0.9.0
Compatibility
Changes
This update contains some major additions (including support for projects), as well as some key bug fixes.
Additions in this version:
- Added support for multi-file script projects! For more information, see the documentation.
- Calling
sys.exitfrom within a script now works as intended.
Changes in this version:
- Added back the option to specify default permissions in
script-option-defaultsin theconfig.yml - Major improvements to exception throwing and handling, including delegation of most exception handling to Jython
- Miscellaneous code and JavaDocs improvements
- Updated many dependencies to their latest versions
Bugs fixed in this version:
- Fixed a bug where PySpigot would not load if the optional dependencies ProtocolLib and/or PlaceholderAPI were not running on the server
- Fixed a bug where color codes were not printing correctly for
/pyspigot listscriptscommand messages - Fixed a bug where scripts could desync from their own PySystemState when calling script code at a later time, such as event listeners, tasks, commands, etc.
- Fixed a bug where PySpigot would attempt to shutdown before it was initialized
- Fixed a bug where a script could access a manager before it was initialized
- Fixed a bug where the main server thread would hang on script unload if the script accessed the
threadingmodule from an asynchronous context by patching the threading module on script unload. This can be disabled by settingdebug-options.patch-threadingtofalsein theconfig.yml
This release also contains a preliminary release for a BungeeCord-compatible version of PySpigot. This is not an official release because I have not comprehensively tested it. Download it here. Feel free to download, test it out, and report any issues here on GitHub or on Discord.
See the complete change log for this update here: https://github.com/magicmq/pyspigot/releases/tag/v0.9.0
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:43VZj9o6"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:G91y7RYh:43VZj9o6"
}

