| 1 |
Not sure to be honest, I will try to generate a replay with excessive description as soon as I have time. My problems are:
|
1 |
Not sure to be honest, I will try to generate a replay with excessive description as soon as I have time. My problems are:
|
|
|
2 |
\n
|
| 2 |
1. I don`t know what is engine-behaviour.
|
3 |
1. I don`t know what is engine-behaviour.
|
|
|
4 |
\n
|
| 3 |
2. I don`t know what is intended behaviour and what is not.
|
5 |
2. I don`t know what is intended behaviour and what is not.
|
|
|
6 |
\n
|
|
|
7 |
BUT:
|
|
|
8 |
some time ago you made a "fix", "change" or whatever to fight command and it worked brilliant for a while before it borked out again. So i am assuming "intended" bahvious is what units showed after said fix.
|
|
|
9 |
\n
|
|
|
10 |
\n
|
| 4 |
3. What "new"? As you see, the thread is quite old already. But the problem is older, I noticed it 3 month ago already.
|
11 |
3. What "new"? As you see, the thread is quite old already. But the problem is older, I noticed it 3 month ago already.
|
| 5 |
https://zero-k.info/Battles/Detail/972663
|
12 |
https://zero-k.info/Battles/Detail/972663
|
|
|
13 |
\n
|
| 6 |
I know the forum is not a good way to report bugs and I should use GitHub, but I was under the impression that it would generate more attention and at least someone would bring it to GitHub.
|
14 |
I know the forum is not a good way to report bugs and I should use GitHub, but I was under the impression that it would generate more attention and at least someone would bring it to GitHub.
|
| 7 |
\n
|
15 |
\n
|
| 8 |
BUT:
|
|
|
| 9 |
some time ago you made a "fix", "change" or whatever to fight command and it worked brilliant for a while before it borked out again. So i am assuming "intended" bahvious is what units showed after said fix.
|
|
|
Fight move is completely broken right now