Timeline for Refining AI movement logic
Current License: CC BY-SA 3.0
12 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Sep 14, 2016 at 18:49 | history | edited | 200_success |
edited tags
|
|
| Apr 12, 2014 at 11:10 | history | tweeted | twitter.com/#!/StackCodeReview/status/454939589166514177 | ||
| Apr 11, 2014 at 13:51 | comment | added | coredump | I just noticed that the function is called "movePosistion"; I corrected it in my answer. Btw, thanks for accepting it. | |
| Apr 11, 2014 at 12:53 | vote | accept | DevWithZachary | ||
| Apr 11, 2014 at 8:03 | comment | added | coredump | I edited my answer to provide more explanations. | |
| Apr 10, 2014 at 21:29 | comment | added | coredump |
Is your position always "1 + 30x", for some x? I think this is a decision that could eventually lead to off-by-one errors; generally, if you have a width of 720 points, it is better to have coordinates ranging from 0 to 719; math operations then fit more naturally, without having to add or remove 1; for example, you could use the modulus operator : xpos = xpos % 720 in your last lines.
|
|
| Apr 10, 2014 at 20:54 | answer | added | coredump | timeline score: 16 | |
| Apr 10, 2014 at 20:22 | answer | added | toto2 | timeline score: 10 | |
| Apr 10, 2014 at 19:17 | answer | added | palacsint | timeline score: 11 | |
| Apr 10, 2014 at 18:44 | answer | added | rolfl | timeline score: 11 | |
| Apr 10, 2014 at 18:40 | review | First posts | |||
| Apr 10, 2014 at 18:48 | |||||
| Apr 10, 2014 at 18:18 | history | asked | DevWithZachary | CC BY-SA 3.0 |