Paper/.github/ISSUE_TEMPLATE.md

2.2 KiB

The following are 'hard suggestions': if you have the information available to you, you really should put it in the report. Choose one of the following templates from below that best fits the issue you wish to report.

Performance issue

This section should be used for any report regarding performance issues

We ask that all timings/profiles are a link, not a screenshot. Screenshots inhibit our ability to figure out the real cause of the issue.

Description of issue:

If applicable

Plugin list:

bukkit.yml, spigot.yml, paper.yml, server.properties

Gist/pastebin/hastebin links

The more information we receive, the quicker and more effective we can be at finding the solution to the issue.

Paper build number:

This can be found by running /version on your server. latest is not a proper version number; we require the output of /version so we can properly track down the issue.

Incompatibility (Bug)

What behaviour is expected:

What you expected to see

What behaviour is observed:

What you actually saw

Steps/models to reproduce:

This may include a build schematic, a video, or detailed instructions to help reconstruct the issue

Plugin list:

A list of your plugins

Paper build number:

This can be found by running /version on your server. latest is not a proper version number; we require the output of /version so we can properly track down the issue.

Crash, Stacktrace

Link/paste of stack trace

You can also simply just use code formatting in markdown!

We need all of the stack trace! Do not cut off parts of it.

Plugin list:

A list of your plugins

Actions to reproduce (if known):

This may include a build schematic, a video, or detailed instructions to help reconstruct the issue

Paper build number:

This can be found by running /version on your server. latest is not a proper version number; we require the output of /version so we can properly track down the issue.

Suggestion

We love suggestions! Suggestions are fairly unstructured, and will be treated as such