SeventhSentinel
In charge of way less than you might think
Administrator
Sonic Team Junior
Kart Krew™️
Welcome to Bug Reports! If you think you've found a problem with the game, you can report it here on the forums or on our GitLab. This post will focus on reporting bugs by using this subforum. Please note that this subforum is only for reporting bugs in the latest official build of SRB2. If you want to report a bug in SRB2Kart, please make a post in the Kart bug reports thread instead!
To report your bug, create a new thread. The title of your thread should contain a brief summary of the bug. The body of your post should include as much information as possible about the bug, including a description of what behavior you expected, what happened instead, and how others can reproduce the bug (if possible). Please upload any screenshots, logs, or addon files that may help us identify and solve the issue. (You do not need to enable DEVMODE for any screenshots you take; important information such as location, info, map name, and map number is automatically stored inside every screenshot.) Sometime after your thread is created, a member of our volunteer development team will look into your issue. In the meantime, feel free to add additional useful information to other users' bug reports by replying in their threads.
Please make one thread for each bug you find. Grouping multiple bugs together in a single thread makes it much harder for us to track what bugs have been fixed. Any thread that groups unrelated bugs together will be marked as Invalid and locked.
What do the thread prefixes mean?
(No prefix): The bug has yet to be confirmed by a member of the development team.
Confirmed: The bug has been verified to exist in the game, but nobody is working on fixing it at the moment.
Assigned: The bug has been verified to exist in the game, and a developer is currently fixing it (or planning to fix it shortly). Smaller bugs that take a short amount of time to fix may skip this step.
Fixed: The bug has been fixed for the next version of SRB2. Yay! Threads for fixed issues will be locked.
Invalid: The bug report is not valid. This is often due to the reported behavior being intended by developers or not being present in an official release of SRB2. These threads may be locked at a developer's discretion.
Duplicate: The bug has already been reported. A developer will reply with a link to an earlier report before closing the thread. (It's good practice to search the Bug Reports subforum and see if your bug has already been reported -- it saves us time!)
Isolated Case: The development team is unable to reproduce the bug. These threads will remain open so that others may provide additional information or clarification.
Won't Fix: The bug will not be fixed. Either the bug is too trivial to fix, or the development team has decided to keep the behavior as an intended feature. These threads may be locked at a developer's discretion.
Thanks for helping us improve SRB2! We wouldn't have made it this far without you.
To report your bug, create a new thread. The title of your thread should contain a brief summary of the bug. The body of your post should include as much information as possible about the bug, including a description of what behavior you expected, what happened instead, and how others can reproduce the bug (if possible). Please upload any screenshots, logs, or addon files that may help us identify and solve the issue. (You do not need to enable DEVMODE for any screenshots you take; important information such as location, info, map name, and map number is automatically stored inside every screenshot.) Sometime after your thread is created, a member of our volunteer development team will look into your issue. In the meantime, feel free to add additional useful information to other users' bug reports by replying in their threads.
Please make one thread for each bug you find. Grouping multiple bugs together in a single thread makes it much harder for us to track what bugs have been fixed. Any thread that groups unrelated bugs together will be marked as Invalid and locked.
What do the thread prefixes mean?
(No prefix): The bug has yet to be confirmed by a member of the development team.
Confirmed: The bug has been verified to exist in the game, but nobody is working on fixing it at the moment.
Assigned: The bug has been verified to exist in the game, and a developer is currently fixing it (or planning to fix it shortly). Smaller bugs that take a short amount of time to fix may skip this step.
Fixed: The bug has been fixed for the next version of SRB2. Yay! Threads for fixed issues will be locked.
Invalid: The bug report is not valid. This is often due to the reported behavior being intended by developers or not being present in an official release of SRB2. These threads may be locked at a developer's discretion.
Duplicate: The bug has already been reported. A developer will reply with a link to an earlier report before closing the thread. (It's good practice to search the Bug Reports subforum and see if your bug has already been reported -- it saves us time!)
Isolated Case: The development team is unable to reproduce the bug. These threads will remain open so that others may provide additional information or clarification.
Won't Fix: The bug will not be fixed. Either the bug is too trivial to fix, or the development team has decided to keep the behavior as an intended feature. These threads may be locked at a developer's discretion.
Thanks for helping us improve SRB2! We wouldn't have made it this far without you.