PROJECT: To Do List for Patch v1.2

[Gilgamensch]

Question: How is the status of a veteran unit after the upgrade? Shall it keep it's veteran status or not? Or shall we leave it to the moders?

[Pedrunn]

Locutus, you forgot the sea city bug

[Locutus]

I think the veteran effects should be discussed elsewhere, that's not what this thread is for. Whatever the outcome, it currently works so there's no immediate need to change it further for the first patch (if it's done in time it'll be included, if it isn't it won't).

Pedrunn,
That's already been fixed, so no point in listing it here (obviously it will be in the first patch).

Martin,
I absolutely agree that's one of the first things about the AI that needs to be fixed, but is it important enough to delay the release of the first patch for, if it comes down to that? I mean, it's not like the AI is *completely* useless now. But I'd like to hear opinions on this, if others agree with you I'll gladly add it to the list.

[Solver]

I would think that yes, if the delay is reasonable, then it's worth to fix the pathfinder in the first patch...

[Gilgamensch]

If it doesn't take to long, and by the sound of it, it is worthwhile waiting

[Tamerlin]

I agree, there are a few things that need to be addressed before a patch is released and the AI path finding is important as far as I am concerned.

[Myrddin]

I too would like the pathfinding fixed IF it does not delay the release unduly

[epeterson]

Could someone please figure out a way to differentiate between a veteran unit and a green unit when they are stacked? I like to use the green troops to guard a newly captured city and use the veterans for continued assimilation. It would be nice if they had mini-tags in the 'army manager' screen.

[Aias]

I'd be willing to wait if that's what it took to improve the AI's pathfinding.

[Flinx]

Originally posted by Locutus
Pedrunn,
That's already been fixed, so no point in listing it here (obviously it will be in the first patch).

For those of you who are involved with re-writing the code it may be obvious what changes you have already made, but for us sitting on the sidelines eagerly awaiting the fruits of your hard labour, it might be nice to have a complete list of changes and fixes.

…On the other hand, fixing things is more important than updating a list of things fixed…

[Locutus]

Ok, I'll add the pathfinding issue then.

Flinx,
If you download the latest playtest version, the readme includes a full list of fixes done so far (and the same info can also be found in the 'altered source code' thread, but that one might provide a bit more details than you'd like).

[Martin Gühmann]

Well I used the edit button to rip of the html code of Locutus' table and started to add all the stuff from the playtest readme to it. While I was doing it, I also added issures to be done that crossed my mind. Unfortunatly it isn't finished yet.

-Martin

[Martin Gühmann]

Fixed crash bug caused by launching editor, generating goods, exiting, and moving a unit.

I just tried this and I wasn't able to recreate this bug with the debug version. In general that looks odd, I have to do three things to cause a crash and with the inibility to recreate it, I guess it was caused by an memory leak. Of course it would be good if someone else could confirm it.

-Martin

[Locutus]

I was able to recreate the bug: start a new game with 'launch editor' (rather than 'launch'), click 'agree to terms', click on 'gerenate goods', confirm with 'OK', click on 'exit', and finally click on the move-units button on the control panel. It has to happen exactly in this order for the crash to take place.

If you don't 'launch editor' or if you just drag the unit to move it, the crash won't occur.

This was with the latest playtest build BTW.

[Aias]

Thanks for adding the pathfinding into the next patch!