Annoying bug

HaS bEeN rEpOrTeD aNd UsE ApProPrIaTe BuG ToPiC.

Faded line means move had been cancelled due to TB, target being out of range, etc.

Written by Amok, 11.11.2015 at 10:18

Faded line means move had been cancelled due to TB, target being out of range, etc.

so... is out of range determined by the point you clicked on or the middle of the wall? because i have noticed my wfs fail a ton when almost at end of range

Written by Amok, 11.11.2015 at 10:18

Faded line means move had been cancelled due to TB, target being out of range, etc.

if we zoom out and attack a wall like that (which couldn't be reached when it was zoomed in) it shows that the wall is attacked, but then next turn the attack cancelled and the unit stayed inside. How do we know when it's a good attack or when it's faulty?

Written by Dbacks, 11.11.2015 at 11:32

if we zoom out and attack a wall like that (which couldn't be reached when it was zoomed in) it shows that the wall is attacked, but then next turn the attack cancelled and the unit stayed inside.

Well-spotted!

Written by Amok, 11.11.2015 at 10:18

Faded line means move had been cancelled due to TB, target being out of range, etc.

But pink didnt even attack anything and warsaw was walled anyway, i honestly dont get how is that TB

Written by Dbacks, 11.11.2015 at 11:32

Written by Amok, 11.11.2015 at 10:18

Faded line means move had been cancelled due to TB, target being out of range, etc.

if we zoom out and attack a wall like that (which couldn't be reached when it was zoomed in) it shows that the wall is attacked, but then next turn the attack cancelled and the unit stayed inside. How do we know when it's a good attack or when it's faulty?

Thats exactly what i was thinking and what im getting...happened 5times in a row

Written by clovis1122, 11.11.2015 at 14:29

Written by Dbacks, 11.11.2015 at 11:32

if we zoom out and attack a wall like that (which couldn't be reached when it was zoomed in) it shows that the wall is attacked, but then next turn the attack cancelled and the unit stayed inside.

Well-spotted!

clovis 2.0 confirmed

Written by Dbacks, 11.11.2015 at 11:32

if we zoom out and attack a wall like that (which couldn't be reached when it was zoomed in) it shows that the wall is attacked, but then next turn the attack cancelled and the unit stayed inside. How do we know when it's a good attack or when it's faulty?

There is no way at the moment. If you use the zoom out trick, then it's risky by its nature.

Written by RP Pro, 11.11.2015 at 15:19

But pink didnt even attack anything and warsaw was walled anyway, i honestly dont get how is that TB

That lines belongs to yellow though.

Written by Amok, 12.11.2015 at 02:53

That lines belongs to yellow though.

I belive you missunderstood me.

If you look at SS again you will see that there is no attacks incoming from pink to either wroclaw or warsaw, if he didnt even attack how could he TB him?

Written by RP Pro, 12.11.2015 at 06:45

Written by Amok, 12.11.2015 at 02:53

That lines belongs to yellow though.

I belive you missunderstood me.

If you look at SS again you will see that there is no attacks incoming from pink to either wroclaw or warsaw, if he didnt even attack how could he TB him?

Dbacks already said how it happens.

Was not TB, just that the move didn't happened.Yellow probably tried to break the wall while zooming in.

Written by Dbacks, 11.11.2015 at 17:52

Written by clovis1122, 11.11.2015 at 14:29

Written by Dbacks, 11.11.2015 at 11:32

if we zoom out and attack a wall like that (which couldn't be reached when it was zoomed in) it shows that the wall is attacked, but then next turn the attack cancelled and the unit stayed inside.

Well-spotted!

clovis 2.0 confirmed

mmm..

I've made some tests with Laochra and it looks like the range isn't a factor on this issue.

It comes down to either the way in which the wall was made or another mechanics related to the moves made from that target. The second one is harder to investigate so I'll stick to the first one.

This link might be useful explaining how the walling order works.

http://atwar-game.com/forum/topic.php?topic_id=17714&topicsearch=&page=1#m230143

If anyone have any information about this bug that can be of relevance, please do post here.

[pr] ●clovis1122: this one http://atwar-game.com/forum/topic.php?topic_id=22813
[pr] ~Desu: ●clovis1122: I must have lost a comment when I refreshed, this one what?
[pr] ●clovis1122: there is a bug related to breaking walls going around... http://atwar-game.com/forum/topic.php?topic_id=22813
[pr] ~Desu: ●clovis1122: Ahh, kk. Yeah reading the comments.
[pr] ●clovis1122: I've got theses two screenshots..
[pr] ●clovis1122: http://i.imgur.com/2fASEFn.png
[pr] ●clovis1122: http://i.imgur.com/R31zP12.png
[pr] ●clovis1122: the unit had few range to reach the wall, so I had to zoom. As Dbacks posted it can be related to when you try to zoom in to break the wall
[pr] ●clovis1122: but I did several tests with lao, and this conjecture failed...
[pr] ●clovis1122: I wonder what else could be causing it
[pr] ~Desu: ●clovis1122: See the line on the first ss goes to the inf on the far side, away from the range.
[pr] ~Desu: ●clovis1122: It may have something to do with mixed stacks(variable ranges) and a random element where the battle takes place in one of either parts of a wall.
[pr] ~Desu: ●clovis1122: So, the move will work if the battle happens to take place on the first inf, but will not if it takes place on the far inf.
[pr] ~Desu: ●clovis1122: Does this concur with your testing, or have you just not looked at it that way?
[pr] ●clovis1122: Had only tested this once with laochra, and the initial though about not having enough range failed... or we were doing it wrong
[pr] ●clovis1122: haven't managed to reproduce it yet...
[pr] ~Desu: ●clovis1122: Maybe looking at it wrong then. Seems to me that there is a random element on where battles take place when attacking a wall.
[pr] ~Desu: ●clovis1122: One of either parts, or in the middle if there's already a confusing mess of walls and multiple attacks.
[pr] ●clovis1122: most likely, I'll try to test in that way. Thanks

Copying this here for convenience, in case others had thoughts on it.

Thanks Desu! I've managed to reproduce it consistently.

There are two conditions to make this bug happen: 1) You shouldn't have range to attack the wall completely. 2) The only side of the wall that you're attacking need to be the first unit of that wall.

The first unit of a wall is simply the unit that you placed first in the wall. The second unit is the one you've placed second, trust forming the wall line. The current mechanics works so the battle starts with the second unit of the wall (Hence why we could see a faded line in direction to the farthest unit of the wall).





I've only tested it enough to secure that the two conditions need to be met. I mean, the bug won't happen if:

1. You're trying to attack the second unit of the wall.
2. You need to have range only and only for attack the first unit of the wall. Haven't tested to see how much further into the wall line you can go and manage to reproduce it. If you have enough range to attack the second unit, then the bug won't happen.

Written by clovis1122, 21.12.2015 at 16:00

Thanks Desu! I've managed to reproduce it consistently.

Bravo, clovis, that was truly well done! Let's see if I could work it out.

This makes sense. Seems we have a winner.

Aaand it's fixed! Coming in tomorrow's update. It's a breeze to fix bugs when you have such clear steps to reproduce them. Thanks again!

Yeah clovis !