Barbarian tutorial 2, event with spotted tracks trigger too fast (again)

Exploring much deeper into the event i found out, that it is possible to play endlessly if nobody of your citizens explores the map!

I was able to play 100 min. without triggering the event - finally a Wood cutter reached far out east for a tree and triggered the event.

So this leads to the following fact:
In the first event (build some buildings...) there should be also the building of an sentry to force the conquering of the map.

I attached a second replay and savegame.

Thanks for checking this. No matter if regression or not, I do not want to push out b19 again - and this seems like a minor nuisance.

> Thanks for checking this. No matter if regression or not, I do not want to push out b19 again - and this seems like a minor > nuisance.

b19 ???
18-rc1, i hope!

But just my idea, cause to most players will play online or against AI.

.

IF an showstopper comes up, this could be fixed between rc11 and rc2... maybe...

sure, I meant not to push out b18rc1. When a showstopper comes up we will exactly only fix the showstopper and not introduce more moving parts by changing other bugs - that is too dangerous :).

Hello everybody,

playing this scenario with version

1:18-ppa0-bzr7319-201412120801~ubuntu14.04.1

he bug is *not* fixed!

I attached the save game just after triggering the event.
For me, there should be first an announcement that the player has to expand on the map - regardless the first event (build up economy) is finished or not.

Confirmed r7321, the event might trigger earlier after you have built a hunters hut, blocking access to small military buildings. Not sure what the current state is but according to comment #8 in bug 732806 the original behaviour was to trigger after some time if a hunter hut had been built.

I wonder whether this is a regression caused by the recent changes to the campaigns or whether we missed some edge case back in July.

Confirmed, that building a hunters hut triggers the event in r7331.

Ferdinand, are you still looking into this bug?

@SirVer Sorry it must be a year since I have contributed the last time.
I had a lot of other stuff to do, I removed me from "assigned to".
If nobody assigns himself the next month I can do it (will have more time again next month, so I can restart contributing ;-) ).

Thanks for the update. Let's see if somebody picks it up. We will be happy to have you back again :)

Fixed in build19-rc1.