If you ever encounter a bug in-game, the best way to let a coder know about it is with a bug report on our GitHub Issue Tracker.
(If you don't have an account, making a new one takes only one minute.)
When creating a new issue it is important to use the format displayed below so coders can easily identify the problem.
If you have difficulty, ask for help in #development-public.
Round ID: What is the round ID? This can be found in the status tab on the server. Test merges: Are there any test merges currently on the server? Type 'show-server-revision' ingame to find out. If there is, then comment on the pull request for the test merge if possible. Problem Description: What is the problem? What did you expect to happen: Why do you think this is a bug? What happened instead: How is what happened different from what you expected? Steps to reproduce the problem: The most important section. Review everything you did leading up to causing the issue. Current map: If it's a mapping issue, then mention what map the issue is on. This can be found in the status tab on the server. Possibly related stuff (which gamemode was it? What were you doing at the time? Was anything else out of the ordinary happening?): Anything else you can tell us. Thanks for helping us out!
|General||Hosting a server, Setting up git, Downloading the source code, Guide to contributing to the game, Reporting issues, Game resources category, Guide to changelogs|
|Database (MySQL)||Setting up the database, MySQL|
|Coding||Coding standards, Understanding SS13 code, SS13 for experienced programmers, Binary flags, Getting Your Pull Accepted, Guide to SNPC's, Text Formatting|
|Mapping||Guide to mapping, Room Structure, Map merger|
|Spriting||Guide to spriting|
|Wiki||Guide to contributing to the wiki, Wikicode|