Issue and Translation Guidelines #10
Description
Issue and Translation Guidelines
Before submitting a bug report, carefully read these rules and guidelines. This keeps the number of bug reports and submissions low and easy to moderate.
Bugs
Before submitting a bug report...
- Check if the bug has already been reported.
- If you observe a bug with add-ons installed, remove them and try to replicate the bug. Only submit a bug report if you are sure it is with this library.
- Never submit a bug report with Optifine installed.
- Never submit a bug report with any MCreator mods installed.
- Do not bother coding changes for a PR without first making a bug report (the exception is for obvious changes like typos).
- If you do make a PR, preceed merge messages with an emoji. It doesn't matter which one and this is not essential, but it makes it easy at a glance to see which merge a change came from.
Once you have thoroughly read and understood these guidelines, you can make bug reports.
Bear in mind that comments on closed issues are unlikely to be read.
Translations
Some information for translators:
- A Crowdin will be made sometime soon. For now, submit translations as PRs.
- If you are interested in the Cunning Linguist Badge, include your Minecraft username in your PR.
- Preceed merges with an emoji. It doesn't matter which one and this is not essential, but it makes it easy at a glance to see which merge a change came from.