i can't stress enough the importance of properly well written description in report
of problem, issue, incident, bug, crash or any other hick-up You have with our game(s)
not to mention all the files needed for complete reports are hosted as part of such report at same place
one of best ways to get things fixed is usage of public bug tracking system
so let me re-introduce CIT (Community Issue Tracker)
to understood how important role is played by such bug tracking solution
please see ROADMAP - future, present and history tracking here (each version vs reports)
url to create new ticket
which e.g. leads to instructions about crash files (where find them, how compress and upload and so on)
and best is this system is not useful just for bug tracking but can be used to track suggestions / wishes / feature requests from users / community
sure it needs registration and email but that's little cost for chance get issue solved, obtain community help or even figure workaround till issue is resolved or else ...
NEW : OpenID login is supported (easier for lazier ones)
one of best ways how get things involved is take part (even just by reporting some glitch) ...
old thread Spoiler: