Legacy Scenarios and Transport Values

[Von Earlmann]

That's a good point VE.

I had an in-depth look at a manual a while ago as I was struggling with the objective hexes. I can't find my Talonsoft manuals anywhere, but this is what the current manual has to say on editing existing scenarios:

13.1
[...]
Note 2: You can even use (import) any of the pre-existing maps or org files in scenarios you create. However, it is imperative that you DO NOT edit any of these files (or any of the scn files), as doing so may result in any scenario using such an altered file not opening properly or an upgrade not installing properly. If you do want to make changes to one of the pre-existing scenario files, be sure to first rename that file using the “Save As” command from the “File” pop-down menu.


I intpret this as Talonsoft / Matrix does not mind anyone editing existing scenarios, just gives a warning as what problems might arise from a technical point of view.

Having said that, I agree that designer's copyright needs be acknowledged, so definitively with any add-on scenarios a proper way to proceed would be to ask the designer's permission to make any changes.

However, as what the manual says, I do not see any issues should Rod wish to create a separate set of modified stock scenarios. I am a glass-always-half-full type of a guy, so I would agree with Hawk that either way, we will benefit from the effort Rod puts in, either on existing stock scenarios, or by creating new ones :)

I guess I was just trying to point out that there is a difference between a right and a privilege....no offense intended.........just polite to ask someone before changing a creative effort.........I have no problem with anyone using any f my OOBs and maps to create something new.......in fact I encourage it as using existing stuff saves a huge amount of work.

VE