Gurken Khan

@chrstgtr If you can't produce units house/pop cap don't matter either. As I can't think of a way a unit not being able to build or capture bringing up a civ again, I'm fine with healers etc. not counting towards the defeated status.

The basics of climate change were known in the 60s/70s, so it's more half a century of wasted potential. And all the money grabbing/corrupt people responsible for keeping destroying our planet will never be hold accountable.

But if they're technically dead by conquest they at least shouldn't have a temple to train new healers, right?

@wowgetoffyourcellphone Yeah, I thought priests might be like fishing boats or merchants regarding that aspect, I just wanted to make sure.

@Stan` It was Conquest = kill all units.

This priest lost his team affiliation the moment I killed the rest of his people; is that intended behavior? (Like fishing boats.)

@Ceres I always un-installed the old version and then installed the new; settings and saved games are still there (Windows). Don't know what extra steps you would do.

Well, that sucks. I also believe the name is deceiving then.

Manned turrets don't shoot arrows anymore? (Build 25848)

It's in the tooltip for The Loom and it's also shown when you look at the unit info.

Are skirmishers battle-bots? ;p

@Simon Morales adjunta crashlog.txt y crashlog.dmp archivos: C:\Users\SimonMorales\AppData\Roaming\0ad\logs

Here's another example of woodcutters making sub-optimal decisions. Even if they take the top corner of the harbor as reference point, the woman on the very right really needs to squeeze by some trees to get to her preferred location.

Solution: just kill it! Sometimes I miss a woman standing around somewhere, but that's still less hassle than back in the day when I had to hunt down every last orphaned fishing boat (although I got pretty good at guessing where they're at) or checking every puddle on the map because as a last resort the AI would put down a foundation of a harbor...

If we're using AE the loading screen quote about 'no end to labours...' should have fewer 'u's.

Yeah, I know. But it's a bit less painful now with the push mechanics. Before, watching my >100 army including pedestrians trying to wrap around a CC, constantly blocking each other in the process, was a real exercise in zen...

@FreagarachAh, thx. Didn't find the styleguide when I looked for it in the wiki. So it is defined which version to use. Bummer it's the wrong one.

Is there any rule which version of a name should be used? Eg I like 'Marcus Antonius' better than 'Mark Anthony' (loading screen tip).

Right. I believe that's what I wanted to say from the beginning. And I totally don't know which reaction button to hit for your post...

Hola. Yo no hablo español adjunta crashlog.txt y crashlog.dmp archivos Puede encontrar rutas a estos archivos en https://trac.wildfiregames.com/wiki/GameDataPaths (with google translate)

I only noticed it with that game on Ngorongoro so far, where the shuffling of positions happens quite consistently when starting the replay. The next game/map that wasn't the case. I will look out for that effect in my next games.

When my CC is in a different position, I have a different resource distribution, build in different locations and have different neighbors that is only a matter of the camera?

Personally I find it disturbing that something as fundamental as the starting position gets messed up, since the resulting 'replay' can only be complete garbage.

@Stan`Sorry for not being clear: I meant the starting positions, lol. (SP, game time is 0:00.) I hope the pics are clear enough to see that my supposed starting position jumps all over the map every time I open the replay. Edit: I started a new game, loaded, quit and watched the replay a couple of times and my starting position stays true. Doing the same with the above Ngorongoro save again and my supposed starting position is jumping all over again.

I start at ~6: I open the replay and I'm at 11: Or at 6 again, or at ~5: Build 25842, logs got nothing. savegame-5460.0adsave