1.1-SNAPSHOT
Compatibility
Changes
YuPay Changelog
[1.1]
โจ New Feature: Dynamic Command Registration
You can now customize the main names and aliases of all commands through commands.names and commands.aliases in config.yml, without modifying plugin.yml.
- Main Name Customization: For example, change
/payto/donateby simply settingpay: "donate"in the configuration. - Alias Extension: Add multiple additional aliases for each command, making it easier for players to remember and use.
- Hot Reload Support: After executing
/yupay reload, new command names and aliases take effect immediately without restarting the server.
โจ New Feature: Automatic Configuration File Update (Multi-language Support)
The plugin now automatically detects the versions of config.yml and messages.yml on startup and intelligently merges newly added configuration items while preserving all your custom settings.
- Version Control: New
config-version/messages-versionfields have been added at the top of configuration files. The plugin determines whether an update is needed based on these version numbers. - Dynamic Messages: Log prompts during the update process have been changed from hardcoded text to being read from
messages.yml. You can now freely modify these prompt texts to achieve multi-language adaptation.
๐ Bug Fixes
- Fixed an issue where some aliases were not properly refreshed after reloading commands, ensuring the reliability of dynamic command registration.
โ ๏ธ Upgrade Notice
This update involves changes to configuration file versions. The plugin will automatically merge newly added items and update version numbers on first startup. We recommend backing up your original configuration files before upgrading, just in case.
Thank you for using YuPay! If you have any questions or suggestions, please join our QQ group: 1080918424.
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:ND76NcgJ:dflLwXps"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:ND76NcgJ:dflLwXps"
}

