Bug Report Guidelines    We appreciate your bug reports and we aim to collate and act upon them as efficiently as possible. In order to facilitate this further, we’ll be sharing some guidelines on how to how to make a clear bug report including information that is relevant to maximising the way in which we sort, investigate, and debug.   A bug is an error, flaw, failure or fault in a computer program or system that causes it to produce an incorrect or unexpected result, or to behave in unintended ways. If you would like to offer feedback or critique on intended gameplay and mechanics etc please do so in the Feedback and Suggestions sub-forum.   Repro: “repro” refers to reproducing a bug, glitch or error. The majority of the time we need to repro so that we can debug/track down the cause. If you have the repro steps and you can outline these in your report, we can get to bug squashing more quickly.   Preferred Format (not all of these fields will be applicable to every bug report): Network: Grid: Description of issue: Any screenshots or video demonstrating the bug: Repro steps if available/applicable: CCC (if location specific, please include the CCC with your report):   Thank you, Pathfinders!   🐞