Issues

This is a public issue tracker for bugs and feature suggestions related to the MC³ Network.

Important:

If you find an exploit or vulnerability in our system, please follow these steps:

1. Privately contact our staff team about the problem.
2. Do not publicly release information about the issue immediately. Give us time to respond and address the issue before you spread said vulnerability publicly.

Submitting

Issues can be submitted at the issue tracker.

Do:

• Follow the formatting guide below.
• Check that your issue is not a duplicate of an existing issue.
• Verify your issue as an actual issue.
• Take advantage of GitHub's markdown, it makes it easier to read your message.

Do not:

• Bump issues to receive a response.
• Argue unproductively, always be reasonable.
• Re-create an issue you feel was closed incorrectly.
• Add useless comments like 👍, +1 or "I like this idea"
• Create disrespectful or provocative comments.

Formatting

It is highly suggested that issues are formatting using the following conventions for clarity and readability:

Title

Provide a short and simple summary of the issue. Your title should make it easy for other users to find it when searching for duplicate issues.

Example:

Arcade Rage not ending

Description

Try to separate your description into two sections (if applicable):

1. The issue

   This section should provide a detailed explanation of the issue.

2. Steps to reproduce

   This section should provide a list of steps needed to reproduce the issue. If applicable, videos or screenshots are encouraged.