Issue, Suggestion & Translation Guidelines

[petrolpark]

Issue, Suggestion 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 Petrol's Parts.
• If you suspect the bug may be due to the library, submit the report there.
• 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.

Suggestions

Before making a suggestion...

• Check if your suggestion already exists – if it does, comment on that post; don't make a new one. Don't replicate denied posts unless you have something new to add.
• The best suggestions are small - e.g. add this tag to this item, or this compatibility recipe for this mod.
• Do not submit lists of suggestions - it's fine to put them in separate posts, even if there are lots.
• Porting is not a suggestion. Do not ask for ports to other versions (old or new), or to other modloaders like Fabric. They will come if and when they come.

Once you have thoroughly read and understood these guidelines, you can make suggestions and 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.
• Translators are encouraged to make up their own puns.
• 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.