Contributing

uSkyBlock is open source and relies on community contributions.

Everyone can contribute in their own way, whether they write code or not. If you care about the plugin and want to help improve it, your contribution is welcome :)

Ideas, bugs, and suggestions

If you have an idea, found a bug, or want to improve the default experience, start by opening an issue:

• Issues
• New bug report
• New feature request

Good issues are concrete. Explain what is wrong, what you expected instead, and who it affects.

Translations

Translations are managed on Crowdin.

Translation help is always appreciated! High-value contributions include:

• adding missing translations
• verifying existing translations
• improving wording, consistency, and Minecraft-specific terminology
• checking placeholders and formatting tags carefully

For details on how the translation system works internally, see Translation system.

Challenge ideas

Challenge contributions do not have to start as code.

Challenge ideas are very welcome! Useful contributions include:

• proposing new default challenges
• improving rewards
• smoothing difficulty ramps
• improving progression between ranks

If you have a challenge idea, open a new feature request.

Docs

Docs improvements are always welcome too.

The quickest way is to edit files under docs/ on GitHub and open a pull request. For a local preview, see Previewing docs locally.

Code contributions

Code contributions are appreciated too, whether they are small fixes or larger improvements.

Keep it simple:

• one problem per pull request
• add or update tests when behavior changes
• keep user-facing messages and config keys backward-compatible where practical
• describe the operational impact, not just the code change

Public API changes need clear migration notes. When in doubt, open an issue first.