[0.951] Editing Pioneers and why it is bugging out

from Elemental Forums

I am currently able to edit my pioneers in the unit design window. This allows me to create all sorts of odd machinations.

Side effects include:
- units with no wages
- units that are hardlocked to group-sized units (3 members)
- units that are able to produce outposts and settlements

 

The problem is this piece of xml

<CanBeDesigned>1</CanBeDesigned>
End of quote

which makes them trainable but also "designable". To remove the ability of designing them, you need to add

<IsUniqueButBuildable>1</IsUniqueButBuildable>
End of quote

to each pioneer. This removes them from the design menu but keeps them in the training menu.

If you are purposefully keeping them in the unit designer so people can produce riding pioneers and so on, you should consider giving them their own modeltype so the player cannot equip them with armor or weaponry. Another option would be to automatically unlock a "stronger" pioneer when mounts are unlocked.

12,991 views 12 replies +1 Loading…
Reply #1 from Elemental Forums Top


I am currently able to edit my pioneers in the unit design window. This allows me to create all sorts of odd machinations.

Side effects include:
- units with no wages
- units that are hardlocked to group-sized units (3 members)
- units that are able to produce outposts and settlements

 

The problem is this piece of xml


<CanBeDesigned>1</CanBeDesigned>

which makes them trainable but also "designable". To remove the ability of designing them, you need to add


<IsUniqueButBuildable>1</IsUniqueButBuildable>

to each pioneer. This removes them from the design menu but keeps them in the training menu.


If you are purposefully keeping them in the unit designer so people can produce riding pioneers and so on, you should consider giving them their own modeltype so the player cannot equip them with armor or weaponry. Another option would be to automatically unlock a "stronger" pioneer when mounts are unlocked.

End of quote

Good point! Where do you find this file I would love to tone down the AI spam of these and settlers!

Reply #2 from Elemental Forums Top

I'm not sure how to accomplish that.

Ashes of the Singularity II
Reply #3 from Elemental Forums Top

If you are purposefully keeping them in the unit designer so people can produce riding pioneers and so on, you should consider giving them their own modeltype so the player cannot equip them with armor or weaponry. Another option would be to automatically unlock a "stronger" pioneer when mounts are unlocked.
End of quote

I'd rather see 'Settler' (or what-have-you) become a trait.  If you want to spend your resource on a heavily armed pioneer unit, so be it.

Reply #4 from Elemental Forums Top

 

Fixed as you suggested, thanks Heavenfall

Reply #5 from Elemental Forums Top


I am currently able to edit my pioneers in the unit design window. This allows me to create all sorts of odd machinations.

Side effects include:
- units with no wages
- units that are hardlocked to group-sized units (3 members)
- units that are able to produce outposts and settlements

 

The problem is this piece of xml


<CanBeDesigned>1</CanBeDesigned>

which makes them trainable but also "designable". To remove the ability of designing them, you need to add


<IsUniqueButBuildable>1</IsUniqueButBuildable>

to each pioneer. This removes them from the design menu but keeps them in the training menu.


If you are purposefully keeping them in the unit designer so people can produce riding pioneers and so on, you should consider giving them their own modeltype so the player cannot equip them with armor or weaponry. Another option would be to automatically unlock a "stronger" pioneer when mounts are unlocked.

End of quote

Sean I tried to edit the unit core xml this way but it does not work for me in game. I added <IsUniqueButBuildable>1</IsUniqueButBuildable> to each pioneer but they are still able to be designed. What am I missing?

Reply #6 from Elemental Forums Top

auboy105 when editing core installation files, please be aware

1) unless you restore the file before patching to a new version, the patch will fail to update your file

2) During beta, to have edits in your installation directory work, you must start the game using a shortcut with -localdataonly

"C:\Program Files\Stardock Games\FallenEnchantress\FallenEnchantress.exe" -localdataonly
End of quote

Reply #7 from Elemental Forums Top

Quoting Heavenfall, reply 7
auboy105 when editing core installation files, please be aware

1) unless you restore the file before patching to a new version, the patch will fail to update your file

2) During beta, to have edits in your installation directory work, you must start the game using a shortcut with -localdataonly


"C:\Program Files\Stardock Games\FallenEnchantress\FallenEnchantress.exe" -localdataonly
End of Heavenfall's quote

 

Thanks so much for the tips!

Reply #8 from Elemental Forums Top

Quoting Heavenfall, reply 7
auboy105 when editing core installation files, please be aware

1) unless you restore the file before patching to a new version, the patch will fail to update your file

2) During beta, to have edits in your installation directory work, you must start the game using a shortcut with -localdataonly


"C:\Program Files\Stardock Games\FallenEnchantress\FallenEnchantress.exe" -localdataonly
End of Heavenfall's quote

Is this no longer working or changed? I tried to mod with the recent patch and this command does not apply any changes?

Reply #9 from Elemental Forums Top


You have to probably run it as admin mode.

edit: we are only seeing local data now so no need for the shortcut.

Reply #10 from Elemental Forums Top

Quoting parrottmath, reply 10

You have to probably run it as admin mode.

edit: we are only seeing local data now so no need for the shortcut.
End of parrottmath's quote

Hmm. I added this command to pioneers in the coreunits file to make them have an upfront gold cost but it does not change in game?

<ProductionRequirement>
<Type>Resource</Type>
<Attribute>Gold</Attribute>
<Value>100</Value>
</ProductionRequirement>

 

Edit: Your were right just ran in admin mode and it works thanks!

Reply #11 from Elemental Forums Top

Note you just need to run admin once for it to record the change.

Reply #12 from Elemental Forums Top

Quoting parrottmath, reply 12
Note you just need to run admin once for it to record the change.
End of parrottmath's quote

Ha thanks I was doing it every time doh!