Problem with Planet Access Researches

Adding one new planet access research (as for gasgiants) to a mod is quite simple:

Make a research for each race with

researchModifier
    modifierType "PlanetIsColonizable"
    linkedPlanetType "GasGiant"

and replace these lines in the planets entity

isColonizable TRUE
planetTypeForResearch "GasGiant"

 

But now i added a second research for a new planet type i called "AncientRelic".

Now if i researched one of the two types i can colonized both the gas giants and the relics.

I get only this error messages (several times):

Failed to convert 'GasGiant' to an enum value.
Failed to convert 'AncientRelic' to an enum value.

I got the gas giant message before, but it worked ingame. Its now a big problem since i can't differentiate between both researches.

Has anyone a idea how to solve this??

 

 

6,595 views 8 replies
Reply #1 Top

Have you looked at how Sins Plus did it? Because I seem to remember it had more than one planet type unlock added..

Reply #2 Top

I looked into Distant Stars and 7Deadly Sins (which contains sins plus as i remember):

7DS contains only the gas giant as new type, the other new planets are linked to existing types.

and DS contains more but all researches are linked to "invalid" type and used only for the special abilities each planet has in this mod. cause a grass planet is linked to "terran" and a ocean planet is linked to ice and so on, similiar to 7DS.

 

Reply #3 Top

Ahh.. well, then I'm thinking you might've found another engine quirk. Does AncientRelic colonization work on its own if you take out GasGiant?

Reply #4 Top

yes it does! it seems to me that if you add only one new colonizable planet type the engine can handle it, but 2 or more not, cause they were thrown together and handled as one type.

Reply #5 Top

Yep, definitely don't think there's anything wrong on your end. Could do the same thing and email them and make it as quick as possible to demo it, maybe they'll squeeze in another ninja fix in a patch or something :P

Reply #6 Top

yeah maybe iam lucky again!

thanks for your help.

 

Reply #7 Top

Wasn't much help, but you're welcome :P

Reply #8 Top

This problem as far as I can tell is that it is hardcoded to:

Asteroid
Ice
Volcanic
Terran
Invalid

You cant actually add to them, you'll notice also that if you convert a file into Binary with an invalid type in it, it will automatically be converted to "Invalid". To get around this with distant stars I have used Invalid as a type of planet, and re-categorized the planets under these names to get the effect I wanted.

I have to admit it is an annoyance but as far as im aware it requires the dev's to fix this issue and there isnt a work around :(