General Attacked Wrong Camp

[Matchoow]

I just reached the point in the tutorial where you have to set up a Garrison and send your General into a new sector and attack a bandit camp. My Explorer had found a new sector to my east with an easy bandit camp, I instructed the General to attack the camp, but instead of travelling straight to the easy camp to the east (the one I clicked), he travelled into another sector to the north of the one I uncovered by exploring and attacked a totally different camp of harder bandits. The path I had chosen didn't cross into this undiscovered sector, so he wasn't intercepted. I lost all the recruits I'd trained and had nowhere near enough resources to train any more (the original resources for the first troops are provided by a previous quest reward).

Now I'm stuck with nothing to do for 4 hours till I can use the General again and there's no guarantee that he won't make the same mistake again. Plus, I have to wait for the resources for the lost recruits.

I understand that the game is in beta, but it's the kind of bug that could make me lose interest in the game while I'm waiting the 4 hours to be able to use the General again (if it wasn't in beta). If the bug repeats, then it's a definite loss. As it's in beta, I will be coming back, but I probably won't be able to attempt the quest again till tomorrow now... :-/

[PennyUK]

I too experienced that happen on the German server recently,no matter where I placed the garrison he automatically went to the one you pointed out,in the and I sent the explorer to uncover that area under cloud,and attacked the camp in there before trying the one you attempted to fight,and it worked

[SevenNin]

Well the path to the camp you want to attack goes trough the area of the camp from above because the general is being intercepted by them

[Matchoow]

Well the path to the camp you want to attack goes trough the area of the camp from above because the general is being intercepted by them

Oh yeah, now I see. The red area shows when you click the camp. I didn't realise that, so it's not a bug after all.