Please include the full BYOND version.
In the "BYOND Version" field, beta bugs need to list both the major and minor build numbers, such as 513.1542 for example. Just including the major version isn't helpful enough when it comes to beta issues, and saying "Latest" is even worse. Choose Other... from the list and then enter the full version info.It is also often very helpful to know what specific version the bug started appearing in. This is usually what you want to post in the version field.
If the issue appears in the stable build, the post belongs in regular Bug Reports (except for webclient issues), but it helps to include info about which versions you've tested with.
Please include a test case.
Demos are almost always helpful for finding a bug. If you can distill the problem down to a simple test case, it usually greatly accelerates the process of fixing the problem. However, it is important that your demo includes full source, not just the .dmb and .rsc files. Also important is that any code you send should be ready to compile as-is after unzipping it, not requiring any additional build tools. (Please do not include extra .dll or .exe files; if calling an external .dll is critical to your test project, include the source for building that as well.)In some cases, a simple code snippet is enough to generate the issue. Those should be where you could paste the snippet into a literal blank project and it would work, not requiring any other files or anything special about your setup. Always test if that's the case rather than assuming; it will save a lot of time.
If you can't reduce your project to a test case, the next best thing you can do is strip out everything you can and send that over. (Obviously, your source will not be shared.) If at all possible, any stuff like character creation should be cut out and replaced with a quick entry into the game, at or near the point where the bug occurs.
Please select the best "Applies to" field.
For filling in the "Applies to" field, here's a quick checklist:- If this bug is in the compiler, it's a Dream Maker bug.
- Server-side issues, including running proc code, are all Dream Daemon.
- Client issues like display, gliding movement, visual glitches, are usually Dream Seeker bugs.
- If you're not sure if a BYOND bug is client or server, it's probably best to tag it as a Dream Daemon bug.
- Webclient issues, client or server, should be posted under Webclient.
- Is it something with the pager? Then it's a BYOND Pager bug.
- It's unlikely any bug could be filed under DM Language.
- Website bugs don't go in this forum; please post them in Bug Reports.