Changing an estab in a scenario

[Lieste]

Strikes me as risky leaving the edit half-done without knowing what each entry does - if nothing else it is misleading for someone else trying to troubleshoot an Estab/Scenario mismatch later on.

[Arjuna]

The reason why we don't allow the change of an estab after a scenario has been created is that we would then need to go through every unit in the scenario and ensure it has a valid estab and if not we would have to replace it with a default estab, then we would have to notify the user of these changes and provide an interface for them to see the list of such units. It's do-able but it would take a fair amount of work. Is it worth it?

[Lieste]

As it stands, nothing stops the user breaking a scenario by just deleting a 'useful' entry from the Estab attached.

It would be a useful tool for troubleshooting Estab/Scn problems, but personally it is a fairly low priority - I only did (once) it to allow duplicating & renaming the linked Estab from within an unexpectedly large and complex test scn, not because I wanted to change the Estab used as such...

More immediately useful would be adding the name of item #2789 etc that has a problem within the Estab editor (or showing an index no. somewhere in the DB) - really worrying when you've got 50-100 changes committed and one of them throws up an error and all you have to go on is that it is a 'Weapon/Vehicle/Ammo/Force'
Doesn't even matter if the name isn't a unique identifier - I'm happier looking at two 88mm guns (say) than having to hunt through the whole list 'somewhere near the middle'.

[vandorenp]

Dave,

When I first started looking into this I found others had already been doing this with a byte editor. Do not know what motivated others but here is mine.

1. For KOAD I wanted to take existing scenario's and keep various aspects of objectives, reinforcement schedules, OB, etc. For instance recreating reinforcement schedules is a real hassle.

2. Needed to add to the estab

3. Thought the bftb estab I had ought to not be used for the additions since it was as of last summer and it seemed improvements to the bftb estab had been made or were in the works. I did not want an accidental confusion with the supplmented estab file.

Seems to me that entries into "the estab" ought to be like social security numbers and can't be deleted or reused. Maybe some sort of estab file central might be good. Work like a virus list updater.

[Arjuna]

ORIGINAL: Lieste
More immediately useful would be adding the name of item #2789 etc that has a problem within the Estab editor (or showing an index no. somewhere in the DB) - really worrying when you've got 50-100 changes committed and one of them throws up an error and all you have to go on is that it is a 'Weapon/Vehicle/Ammo/Force'
Doesn't even matter if the name isn't a unique identifier - I'm happier looking at two 88mm guns (say) than having to hunt through the whole list 'somewhere near the middle'.

Point taken. Keep in mind that this was originally designed as a developer only tool. You can view the xml version in a text editor, like Word, and do a search on the ID number to find the object. I'll see what we can do re adding the name to the error message.