LS 25 Default Types v1.0.0.5

LS 25 Other



LS 25 Default Types v1.0.0.5

v1.0.0.5:

  • Updated the way defaults are loaded, should be more efficient now
  • Added a check for double registered fill types
  • Minor bug fixes

This is a little addon that changes the way fill types and fruit types are loaded. Normally, xml files from the game install folders load first, then the map information is loaded and added to those existing entries.

This allows map makers to make their map configurations the base configuration, bypassing the game install files altogether. This allows for more flexibility and control when setting up map types, and also resolves some issues that can come from appending to existing entries.

Activating is as simple as copying the xml file(s) you want to use as the new base into your map, and use the thDefaultTypes key in your map.xml file. Examples are included in the sdk folder of this mod.

Currently supported:

  • maps_fillTypes.xml (fill type configuration)
  • maps_fruitTypes.xml (fruit type configuration)

Activating is as simple as copying the configuration xml file(s) from your game install folder to your map, then using the thDefaultTypes key in your map.xml file. Examples are included in the sdk folder of this mod.

Examples:
<fruitTypes filename=”path/to/maps_fruitTypes.xml” thDefaultTypes=”true”/>
<fillTypes filename=”path/to/maps_fillTypes.xml” thDefaultTypes=”true”/>

Also, and this is just the vanilla load process, when you specify an external filename (i.e. maps_fruitTypes.xml or maps_fillTypes.xml”) you also have to copy all related information from your map.xml to the file you specified as well. The game, by default, loads from either the file you specify -or- the map.xml not both.

For example, everything in the <fruitTypes> section (other than the filename pointer and thDefaultTypes key) would need to be copied to your map embedded maps_fruitTypes.xml file. In addition, things normally found in maps_fruitTypes.xml like <fruitTypeCategories> would need to be copied from your map.xml to your maps_fruitTypes.xml as well.

Finally, the $data filename constant does continue to work as far as I can tell. You don’t have to copy over all foliage and textures files or anything like that. Just the main configuration xml(s) and go from there.

Note: This also addresses the current fruit type double registration issue when trying to change vanilla fruit/fill type values. Double registrations will show a warning and try to self correct if this mod is enabled. You do NOT need to edit a map for this functionality. This is enabled just by activating the mod.

Credits:
ThundRFS
1 Star2 Stars3 Stars4 Stars5 Stars (No Ratings Yet)


Why to use Farming Simulator 19 mods | Farming Simulator 22 mods?
Even though Farming Simulator 2019 / Farming Simulator 2022 is a great game, you can make it even more astonishing by installing Farming Simulator 19 mods / Farming Simulator 22 mods. There are plenty of mods for every part of the game so you can change or integrate whatever you like. All the FS 19 mods / FS 22 mods are absolutely costless, so you won’t spend anything trying to change the game according to your own wishes. Our main goal is to keep Farming Simulator 19 / Farming Simulator 22 community happy where everyone has a possibility to implement their ideas and enjoy playing a perfect game. If something looks disturbing, bothers you or maybe you just need to integrate more tools and supplements, simply use FS 2019 mods / FS 2022 mods. Not many games provide an opportunity to change it by individual needs, but Farming Simulator is different. You can do whatever you want just by installing LS 19 mods/ LS22 mods so it’s time for you to take action and fulfill even craziest ideas!



You may also like...

Leave a Reply

Your email address will not be published. Required fields are marked *