Skip to content

Bug Reports

Found something broken? Great catch — you're helping make the project better. Please read these guidelines before posting in #bug-reports so we can investigate and fix issues as quickly as possible.

Before You Report

  • Search — Scroll through #bug-reports to check if the bug has already been reported. If it has, react with 👍 to show you're affected too — don't post a duplicate.
  • Update — Make sure you're on the latest version before reporting. The bug may already be fixed.
  • Reproduce — If you can only make it happen once and never again, hold off until you can reproduce it consistently.

How to Write a Good Report

When posting in #bug-reports, include the following:

1. What happened A short, clear description of the bug. What went wrong?

2. Steps to reproduce Walk us through exactly how to trigger the bug, step by step. Be specific — assume the reader knows nothing about what you were doing.

1. Go to ...
2. Click on ...
3. See error

3. Expected behavior What should have happened instead?

4. Actual behavior What actually happened?

5. Environment

  • Game and plugin version (e.g. ETS2 1.54, MotionCab v0.34)

6. Attachments Videos and logs are extremely helpful. Please include them when you can.

Report Template

Copy and paste this into Discord when submitting a report:

**Bug:** [Short description]

**Steps to reproduce:**
1.
2.
3.

**Expected:**
**Actual:**

**Environment:** OS / Version / Browser (if applicable)

**Attachments:** [video, logs, etc.]

After You Report

An admin/developer will acknowledge your report and may follow up with questions. Please keep an eye on the thread and respond promptly — reports that go unanswered often get stale and harder to debug.

Thanks for taking the time to report — every bug you catch makes the project better for everyone.