- Bug A Bug is a low-level problem with a specific component of the game. Bugs occur when the intended functionality is functioning incorrectly. Not every problem is a Bug. Bugs are generally pretty specific, such as
I ran to <this> and clicked <this>, and instead of seeing <this> I saw <this>. Bugs are measured against expected results. When you know what should happen, and it doesnt happen that way, that is a Bug.
- Issue An Issue is a high-level problem with the intended functionality of a general system of the game. Issues are usually more vague than Bugs. Issues relate to things like frustrations with the UI, poor user feedback during an event, a lack of understanding about how to do something, balancing concerns, or game behaviors that you know are working correctly but do not make sense to you. You know for sure that you have an Issue when it makes the game more difficult to grasp or play but you know its not a Bug.
- Sug A Sug [short for Suggestion] is a personal idea about how to improve something about the game. Sugs are usually related to small tweaks to current functionality. Within the context of Beta Testing, Sugs are most useful when you are looking for ways to make gameplay smoother and more fun. The best games are made in the details, and coming up with ideas to tweak those details can be extremely beneficial.
Later this week [hopefully tomorrow] we will be making a Bug database available to the Insiders to allow you guys to enter your Bugs into a centralized location that makes it easy for Tilted Mill to fix them. This database will be for Bugs only. Issues and Sugs require some amount of discussion, and therefore they fit the features of a forum quite well. Bugs do not require any discussion. The game component is either broken or it isnt. Reporting a Bug on the forum is not recommended, but expect to be asked to bug it if you end up doing so. For now, until the database goes live, please just take notes about the Bugs you are finding so you can enter them all into the database at once.
When reporting your findings, please keep each problem exclusive to its own thread. Take a few moments searching the database before digging into a Bug to find out if it was reported earlier, so that you do not spend a bunch of time duplicating someone elses efforts. Dupes can be an incredible waste of time for anyone involved with the record. All of this holds true for Issues and Sugs on the forums, as well. Take it from me, its very frustrating to spend 20 minutes tracking down a Bug and 10 minutes on reporting it only to find out someone else reported it earlier and your effort was wasted. Ohhh thats maddening! So save yourself a little stress by confirming that the problem you found is unique and unreported. If you do find that someone else has already reported the problem, its extremely helpful to take a few moments and see if you have any new information to add to the thread or Bug record.
For each thread, use the type of problem as a prefix to the post title. For example, Bug: Game launches even when Steam is closed. Another example would be, Issue: There is no feedback given to the player when monsters attack the town. If you are not sure about which prefix to use, post with a ???: as your prefix. This will indicate to me that the problem is up in the air and you arent sure about whats going on. It will allow me to quickly address points of confusion. The title can always be edited to reflect the problem type if it is later deduced. I will likely be passing over any thread that does not have a prefix, so if you posted and are not getting any feedback about it, that is likely the reason.
Last, but certainly not least, there will be a number of habitual responses you may see me post. These are quick responses that help me handle a thread efficiently. The more efficiently I handle a thread, the more threads I can handle!
- Here is the reference table for what you will see:
NYI Not Yet Implemented. This ones pretty self-explanatory.
BOB Bug Of A Bug. The Bug is a result of another Bug happening first, and wont happen when the original Bug is fixed.
CAA Confirmed And Added. The problem is confirmed and has been added to the internal database.
KIP Known In Progress. The Devs are already aware of the problem and are working on a fix.
FIL Fixed In Latest. The Devs have already fixed the problem internally, but you will not see the fix until a new build is released.
CNR Cannot Reproduce. We cant seem to make it happen internally, and need more information [i.e., clearer descriptions, more research, etcetera].
NBA Not Being Addressed. The Producers have decided that the problem is valid, but not worth the time [and cost] to fix.
WAD Working As Designed. The Designers have determined the problem is not valid because its how they want it to work.
If anything is unclear, please feel free to let me know!