Loading...
  OR  Zero-K Name:    Password:   

Post edit history

B1127276 10 on SandCastles2 (Multiplayer)

To display differences between versions, select one or more edits in the list using checkboxes and click "diff selected"
Post edit history
Date Editor Before After
6/4/2021 9:13:11 AMunknownrankShaman before revert after revert
Before After
1 I would wish more people would at least contribute to bug fixes with some basic information. Posts like "I so hate this piece of shit game" do not help us when you're facing an issue. So let's streamline this process and cut out the part where we dance in circles trying to telepathically communicate that there was a bug here. Telling us that you "hate our game" or crying about "bug-k" or whatever does [b]NOTHING[/b] to motivate us or assist us in tracking down issues. You want problems fixed here you go I wrote you a flow chart: 1 I would wish more people would at least contribute to bug fixes with some basic information. Posts like "I so hate this piece of shit game" do not help us when you're facing an issue. So let's streamline this process and cut out the part where we dance in circles trying to telepathically communicate that there was a bug here. Telling us that you "hate our game" or crying about "bug-k" or whatever does [b]NOTHING[/b] to motivate us or assist us in tracking down issues ( in fact, the only reason why we should engage with this behavior is because there is an underlying problem and that ignoring people who do this makes the rest of the population suffer because of your attitude problem) . You want problems fixed here you go I wrote you a flow chart:
2 \n 2 \n
3 \n 3 \n
4 1.) Press F8 in game (or whatever the debug console button is for you) 4 1.) Press F8 in game (or whatever the debug console button is for you)
5 2a.) IF YOU SEE LUA ERRORS open an issue on github or post something here. [color=red][b]DO NOT FORGET TO ADD AN INFOLOG. This saves us tons of time for most minor issues like this.[/b][/color] Click submit a bug report in lobby afterwards, tell people you'll brb bug report or whatever. 5 2a.) IF YOU SEE LUA ERRORS open an issue on github or post something here. [color=red][b]DO NOT FORGET TO ADD AN INFOLOG. This saves us tons of time for most minor issues like this.[/b][/color] Click submit a bug report in lobby afterwards, tell people you'll brb bug report or whatever.
6 2b.) IF YOU DO NOT SEE ANY LUA ERRORS either post here or use the CONTACT ADMINS page. [color=red]This is someone exploiting a lag generator and must be reviewed by humans[/color]. Make sure to include the link to the battle (not just B1127276) and a rough time estimate of when it occurred. 6 2b.) IF YOU DO NOT SEE ANY LUA ERRORS either post here or use the CONTACT ADMINS page. [color=red]This is someone exploiting a lag generator and must be reviewed by humans[/color]. Make sure to include the link to the battle (not just B1127276) and a rough time estimate of when it occurred.
7 \n 7 \n
8 This small effort by even one person can save us so much time tracking down issues. I personally put in around 3 hours of watching replays to ensure that there isn't someone exploiting something so far. 8 This small effort by even one person can save us so much time tracking down issues. I personally put in around 3 hours of watching replays to ensure that there isn't someone exploiting something so far.