SEV 1.38 - new combat log!

[se5a]

We've been nagging Aaron for a better combat newslog for months, finaly he's come through! kudos go to SJ for comming up with the design and creating the initial mockup screenshots to get this.


Version 1.38:
1. Fixed - If you accepted treaty changes with an empire where you had an existing treaty which
did not allow treaties, the existing treaty would be set to None.
2. Added - A text warning to the Research window if research is not allowed by a treaty.
3. Added - A text warning to the Intelligence window if intelligence is not allowed by a treaty.
4. Fixed - Script Parser was erroring when loading data files.
5. Changed - Changed default strategies to not retreat until 90% of force lost.
6. Fixed - Ships were retreating when they shouldn't.
7. Fixed - For an Alliance proposal, if the total number of yes votes equaled the number needed
to pass, the proposal would fail.
8. Fixed - In Ground Combat, the Change View Mode button would cause a crash.
9. Changed - The combat log report is now more of a summary of the combat. A new button "Details"
will let you view the specifics of the combat. Instead of two lists of starting forces and
ending forces, there is now just one list with a "Start Dmg" and "End Dmg". The status column
now shows the following states:
Undamaged - Vehicle took no damage in combat.
Operational - Vehicle took non-critical damage in combat.
Captured - Vehicle was captured by another player.
Retreated - Vehicle retreated from combat.
Disabled - Vehicle had all weapons and engines destroyed.
Disarmed - Vehicle had all weapons destroyed.
Immobilized - Vehicle has all engines destroyed.
Destroyed - Vehicle has been destroyed.
(Thanks go to SJ for the design)

[Raapys]

Sounds great!

Does point #6 mean that weaponless ships wont automatically retreat, regardless of strategy, anymore?

[Captain Kwok]

No, there was a bug introduced in v1.37 that made all ships retreat in combat. However, the retreat setting were made smarter in that version, so it should be more intelligent with the next patch.

[Ed Kolis]

Hmm, I wonder what comes up in the combat details view?

[se5a]

combat details window is kind of like the current one, but only half the length, since the pre battle and post battle are on the same line. also there's the cool info like disabled, imobilzed disarmed etc.

[Randallw]

I'm interested if somehow it fixes a problem with combat replays through PBW, that they don't work sometimes. I realise it's probably a PBW thing but maybe it is caused by having such a long report section. We'll see.

[AgentZero]

This sounds most good to me. Sure, combat reports where you had a couple hundred fighters mixing it up will still be stupidly long, but now they'll be half as stupidly long!

[se5a]

nonono. you just get a SMALL note in the news log, with a DETAILS button. clicking THIS button will give you a DETALED list which is half as long.

[Romulus68]

In our PBW game we has some combat log issues where our combat files got scrambled. You would see battles that were not the ones you were involved in. Though, that is not my point I want to make.

My point:

We deleted the combat and movement logs in our game two turns ago. The turn we deleted the logs it came through with no replay options for combat along with no recorded movement logs. The turn after that it ran smooth and the logs loaded for both combat and movement.

My key point about all this is that the turn files went from 18 megs to the past turn at 6 megs. I think we should write into the PBW code to periodically erase the combat logs on the PBW server. Yes, we will have a turn of no reports, but then after the file decreases in size by a huge margin, plus the turn ran smooth as silk.

Try (test) that in a few of your games and see what results we get. It may be worth it to sorta clean out (reboot) the combat/movement logs.

[Ed Kolis]

How do you delete the logs in a game if you are not a PBW admin? That might be what is holding up my latest KOTH game... if Parabolize knew about this he might be able to fix it!