well, have a look at FfH_Continents, that is the simplest one. If you scroll down a little bit, you should see something like this:
Code:
##########################################################################
##########################################################################
##########################################################################
##########################################################################
##########################################################################
##########################################################################
########################### FfH part below ###############################
Well, that's supposed to mean that the FfH code I added starts below
Now, simply copypaste this and everything below at the end of the other script. Just make sure that the indentation is unchanged. This is part of the syntax (it can even make a difference if a tab or several blanks are used!).
As far as I can see there is only one thing that could go wrong. Basically, I redefine the civ normalizeStartingPlotLocations() function. Everything else is new helper functions (or even classes) that I added. Now, when the script you want to modify itself redefines this function, then these definitions clash.
As far as I remember this function is per civ default used to place team members close together, and only few map scripts redefine it (I only encountered it once. I think in some continents variant where the map script wanted to make sure that the team members are placed not only close together but also on the same landmass...).
Even if the map script uses that function, you could simply delete it and hope that whatever was implemented there was not important.
Only one thing I want to ask you: If you're going to redistribute it, make sure there are some (improvised if necessary) comments in the script that credit the original authors. I wouldn't mind some credit either, of course
. Then add yourself as the one who adapted that specific script, so that you are the one that gets blamed if something goes wrong
But, who knows, maybe I'll get to it this weekend. I mean, as you can see it isn't really much work. Most work for me would be to check if everything is still consistent with the new versions, if new script versions are out, see that everything is properly documented and so on...
EDIT: whoops too late
ok I re-added the original comments of the map makers and a slight note about you... have a look, if you're ok with that then I'll put it into the first post:
View attachment 147694
