Matrix Games Forums

Would it be possible to have some way of dumping the estabs at the end of a game? It'd be useful for analysis.

It'd also be a nice start down the campaign trail.

Hi,

I assume you really mean dump the forces at the end of the Scenario?

Its an interesting idea, we have a force list importer/exporter in the ScenMaker.

A lot of the code is shared between the ScenMaker and the game, hmmm, if we used the export code in the game, accessed from the AAR(?), then maybe you could import it back into a new scenario? And use this to string a campaign together, it would be manual of course, but might work!

Interesting.

Also, you'd need to find a way to capture the final disposition and VP totals to use for determining the makeup of the follow-on scenario. e.g if the Germans need to fulfill an exit objective and they succeed, then the next scenario would take place on another map (presumeably), but if the defence is successfull, there'd have to be a way to revisit the same map, but with a different scenario VP allotment/mission, oob, and starting locations. I suppose if we accept some distortion/abstraction of this process then implementation would be easier.

You also would need a better breakdown of casualties- many of the 'kills' in the game now would be troops that were scattered, lightly wounded and returned to duty, many other possible fates whereby the troop strength would need to be ajusted. Same thing for vehicle/equipment 'kills'. Many may be repaired (IF you can recover them- ie occupy the prior battlefield).

ORIGINAL: DanO

Would it be possible to have some way of dumping the estabs at the end of a game? It'd be useful for analysis.

It'd also be a nice start down the campaign trail.

This has been an item on many a wishlist for these games. I simply want to know what happened at the end of the operation. At this point, it has yet to emerge as a feature in AA games.

Yes, sorry, I meant forces not estabs.

I was thinking as a first step it would be possible to link scenarios together using the forces output of one as the forces input into another. It'd have to be a manual process to begin with, but I can't imagine it'd be too tricky to cobble something together to automate it. I might have a go at it myself, as I've just noticed that the force lists are xml. I'd have to use fake data, but it'd interesting to test the principle. [:)]

However, as Franklin Nimitz says, it'd be much more useful if there was some extra data in there and if the process of connecting one scenario's output to another's input was a little more complicated than a simple pass-through. The amount of extra data might not even have to be that great; for example, the breakdown of casualties could be effectively random, with some influence given to the set up of the campaign, e.g. in campaign X the Allies are over-extended and so not many casualties are recovered or reservists moved forward.

As for the flow of the campaign, that'd have to be part of the external app, and there'd need to be a system for configuring campaign logic. Not a perfect solution, but certainly better than nothing. There would be no harm in folding it into the main game in a later release. [;)] It's not a trivial problem, though, so a better first step would simple be connecting one scenario to another.