MekHQ - Allow access to log during Resolving Battles

[Kendricke]

I'm not sure if this counts as a bug or an enhancement request, but I've had several occasions where I'm resolving a battle and need to assign kills, but can't access the logs of the battle to identify who actually killed what till after I complete resolving the battle as the log is simply not available/created/complete yet.

Because of this, I've taken to writing down kills as they occur so that I can assign kills better after the battle.

[gsparks3]

Interesting. I've always been able to go to \logs\ and open gamelog.html, which has the log of the most recent battle (i.e., the one I'm currently in the middle of resolving). If your gamelog.html does not have the correct data after closing the MM window (and thus moving to the MekHQ scenario resolution screen), that might be an actual bug.

[Windchild292]

Implementation Format Idea: The Round Report is transferred into MekHQ for scenario resolution, accessible from a button there that loads it in a separate dialog, and then dumped immediately after. This transfer will be enabled based on a MekHQ option.

This will not be loaded if the scenario is resolved from MUL nor manually, just the automatic game resolution.

How does that implementation format sound @Kendricke ?

[gsparks3]

Jumping in again to comment: my primary use of the log post-battle is to assign kills for units that weren't automatically assigned (e.g. ejected mechs and vehicles, by seeing who blew the legs off / immobilized the vehicle, and so on). If you could include a way to highlight/isolate the combat log text relevant to a specific unit that would be a big help. CTRL+F works in the HTML log file, but not in the Round Report during Megamek, so if it just clones the RR functionality that wouldn't help as much.

[Kendricke]

My use case is basically the same as gsparks.

To be specific, right now I track kills in a notepad I keep at the desk, with both the unit number of the killed mech and my own mech listed. I might do this for mechs that are destroyed or abandoned due to falling damage which was directly caused by one of my units (I imagine that if you kick a mech and it loses a leg, then falls over, then either explodes or the mechwarrior ejects shortly thereafter, you'd count that as a kill...just as a pilot who shoots down a fighter and observes it crashing into the ground would count that as a kill, even though it was technically the crash that destroyed the plane).

Anyway, sometimes I just want to play through the match (or the match takes a very long time or whatever) and I either don't track it or miss some kills and then want to confirm if the kill came from one of my mechs (as opposed to a liason officer or ally or some enemy just literally running through a building and dropping into a hidden basement) so I pull up the log and then do a CNTRL+F to find the mech or unit number and go from the bottom up till I find the line that shows the mech was last damaged prior to destruction/abandonment.

This is...a pain.

Obviously, I'd prefer a more robust automated kill/damage tracking system, but in the immediate short term, I just want the right log available after each battle when the kill assignment screen comes up. As of now, this is not consistently the case.

[Kendricke]

Still happening.

[Kendricke]

Note that in above screenshot, the current time was 1:48 PM, but latest gamelog is 90 minutes old at 12:14 PM. Note also that the most recent 3 gamelog files ONLY showed the following line when opened: "Log file opened 2020-10-11"

I have to go back to the 12:07 PM log to find ACTUAL in-game logs.

Is there a setting I need to select to make sure my gamelog is up to date?