Failed to load mods: OldAbandonedSettlements/settings.lua:1: attempt to index field 'AbandonedRuins-set' (a nil value)
stack traceback:
OldAbandonedSettlements/settings.lua:1: in main chunk

Mods to be disabled:
• OldAbandonedSettlements (1.0.2)

That can be quickly fixed:

local constants = require("__AbandondedRuins_updated_fork__/lua/constants")

Now just use constants.CURRENT_RUIN_SET_KEY instead of hard-coded value.

That was fixed a while ago. Probably in 1.0.3

The mod is still using "current-ruin-set" directly. When I maybe want to rename it one day, it will break again this mod. Plus I noticed that this mod references to far out-dated mod versions: 1.2.0 is to very old for AbandonedRuins_updated_fork and 0.0.2 for AbandonedRuins-base. This need a small bump so this mod's users are forced to have up-to-date versions. Otherwise people might come to my mod's forums and complain about bugs that are already solved.

And it still forbids ANY ruins on Fulgora, etc. by using exclude_surface. Please stop abusing these functions!

exclude_surface used to be the only way to exclude a surface prior to any changes you made to the mod and I was instructed by the mod creator (Bilka) to use this function to exclude surfaces in this way, now that you have changed the mod I can use the new features when I next update this mod! It is not abuse it is old code from older versions!

Yes, okay. Then "misuse" is the proper word. It was exactly that reason what you say here why I added spawn_exclusively_on to the mod as excluded_surface is to drastic, other mods might want to spawn ruins on Fulgora and then with your mod installed, they won't spawn anymore.

Thank you for wanting to include these changes in your next update.