Firstly you find and log all differences between the 1500 AD mod-scenario and the previous version of RFC. Use WinMerge to get a visual representation of any change in any of the files.
Then you add all those changes to the latest version of RFC, one at a time, file by file. Don't make any mistakes and hope that the changes are compatible with the latest version.
WinMerge can - just hit merge down or merge all or something - but the point is that you don't want that. Because then you end up with an invalid mod.No program can magically merge files for you.
This is my point exactly.WinMerge just helps you to find out where the two different versions differ; you have to decide what part of which version you want to use for your merged version.
And this is why you firstly log all the changes between the 1500 AD scenario and the previous version of RFC that it is based upon. There should be numerous changes, but chances are that not all of those can be applied directly on the latest version of RFC. So the "merge" still needs to be done with care.Practically I suggest using the current version of RFC as base and merging everything in that obviously looks like it's connected to the new scenario (units and technologies and the like).
Yes he can. He just needs to do the same as above with the SDK and compile a new custom DLL.Mind that you can't do that if the 1500 AD scenario uses a custom DLL.
Of course, but setting up an SDK was a barrier he was not willing to take before, so I figured it's better to not consider it yet.
If the creator of the modmod didn't leave comments, it's your educated guess to decide what belongs to it. Obvious aspects would seem to be starting dates, granted techs, granted units ...
I'm sorry, The Turk, but making new starting dates for RFC scenarios is awfully difficult. The mod was never built for this in mind. So the creator of the 1500 AD scenario had the right idea. If I had the time I'd gladly update it myself, because I'd like to make a Moscovy scenario based on it.![]()