ORIGINAL: TheElf
Potential compromise. Not one to create more work for others [;)]I think I have a solution regarding Nik's A2A model. Before I present it however I think I have made a pretty good arguement as why we at the CHS should just flat out adopt his A2A work at a minimum, but.....
The compromise: If in fact we still have a large number of dissenters, I propose a CHS Ver. XX.Xb. "XX.X" of course being the standard CHS Mod as it is now. "b" being the sub-variant of the CHS which has the Nik mod incorporated. Given the CHS's exhustive OOB changes I think that it should be the platform from wich we all deviate or mod. At least all that OOB stuff will make it into whichever sub variant players choose to play. Theoretically we could have three parallel line of the CHS
Ver XX.X = the standard CHS
Ver XX.Xb = the CHS/Nik Mod
Ver XX.Xc = the CHS PRY mod
thoughts?
Well to be more specific, there are maybe two ways ( maybe more ) to do this.
(A) Base CHS database, with 3 scenarios.
(B) Base CHS database, with Nik variation database and Pry variation database.
There are problems with both and advantages of both ( of course)
(A) Problem with just one database is that we have to "merge" the differences between the databases, I think for the most part this would be fairly easy as regards Nik .. the changes Nik has made ( that I'm aware of anyway ) are heavy in the device area. And I'm not sure CHS has really been heavy here. CHS on the other hand has mostly changed OB and TOE and not sure Nik has made nearly as extensive a set of changes in the OB/TOE areas. On the other hand I know Pry has extensively changed ships at least in the tonnage area - but this change sounds good - and if it has been at all tested then I'd say we should try to pull that in as well. I'm not not as aware of what other changes Pry has made. Having three scenarios still allows some variation , though with the limits on slots it does really offer much. And finally after the merge, there is the overhead of coordinating changes between Pry, Nik CHS. The advantage is that we have one databaseand we can all benefit from having the good parts of all these mods in one system.
(B) The pro of multiple databases ( with CHS as base ) is that Nik and Pry are then free to make pretty much whatever changes they want, whenever they want. The downside is "sympathetic" upgrades. So when CHS changes, then Nik and Pry will be pressured to re-release there mods. Andrew knows something about this since he has to re-release the stock scenarios then run on his map periodically ( and I think he also was doing Pry scenarios ... the 130-139 series ... at one point ).
While Ideally I'd like the (A) solution. The (B) solution maybe more practical. But I'd try to get Nik, Pry and Andrew in a dialog about this - us "kibitzers" won't be able to resolve it for the principles.









