Skip to content

Conversation

@Testure
Copy link
Contributor

@Testure Testure commented Sep 2, 2025

What:
This section describes what is this PR about. It should be clear and concise description why is this PR needed and why it should be accepted. Section name should be changed to appropriate one based on what this PR tries to solve.
Link to explanation from issue this PR is solving can be used instead of copping same text here.

How solved:
This section describes how was problem solved/feature implemented/change made if it is not possible to pick up from first look at code. Or if code requires additional explanation why it was done in that way.

Outcome:
This section is used mostly for sharing information in changelog and there should be shortly described what this PR added/fixed/changed/removed.
For correct linking of issues please use any of Closes/Fixes/Resolves keywords.Example: When PR is fixing bug use "Fixes: #number-of-bug"

Additional info:
This section is for screenshots which are required for any GUI, rendering or recipe changes. Or any additional info that reviewers should be aware of.

Possible compatibility issue:
This section is for defining possible compatibility issues. It must be used when there were API changes, item/block removal or recipe changes.

Please fill in as much useful information as possible. Also please remove all unused sections.

what do you mean i'm supposed to edit the description? it already has plenty of text :clueless:

@Exaxxion Exaxxion self-assigned this Sep 2, 2025
@Exaxxion Exaxxion added the enhancement New feature or request label Sep 2, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement New feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants