Results 1 to 1 of 1

Thread: A solution to sieges crashing in custom battles

  1. #1

    Default A solution to sieges crashing in custom battles

    This topic was covered in the v.2.3 release, but as few people anymore check the text of that release, here is some info about this bug and how you can get around it and play sieges in custom battles.

    What is this bug?
    If you want to play a custom battle and try to select a settlement, so that you can play a siege battle, the mod crashes and you have to restart it. It does not matter which settlement it is except for "fort". If you select "fort" the game will not crash.

    What causes it?
    All mods that have stone forts on the campaign map, including the original Crusades and Britannia, have issues with custom battles of settlements. From my messing around with the error logs, it appears that the engine has a hard-coded definition of a fort as being a wooden fort of a particular type. Even in Crusades and Britannia that have stone forts on the campaign map, if you select a fort in a custom battle, it will be a Roman-style fort with a wooden palisade around it, rather than a small stone castle. So mods like Stainless Steel and other mods that use the stone forts had to disable custom battles or disable certain types of settlements. It is simply not possible to play a siege of a stone fort in custom battles. For some reason, however, this bug only appears to be a problem for custom battles and to not affect campaign battles. To any of you interested in modding, adding too many types of stone forts may also lead to your mod crashing, so it may be that there is a slot for fort styles that has a max cap to it and the error logs seem to dislike, among else, having different numbers of forts specified in different areas of the code (one of these areas being the engine itself, that cannot be read by modders).

    Is it at all possible to play custom siege battles?
    Yes, there is a workaround: First select a fort as your settlement, no matter which settlement you would like to use in your battle. After that, select another settlement, and proceed as usual, selecting the culture, etc.

    Is there a permanent solution?
    No one has found a solution to this bug - unless stone forts are completely removed. The bug appears to have a bigger effect in Broken Crescent custom battles because of the way the Mesoamerican culture is being used, i.e. the Mesoamerican settlements have also been replaced by modded settlements to represent the Hindu culture and this worsens the problem with the settlement selection in custom battles, because Mesoamericans not only did not have forts, they did not have castles, fortresses, etc - so presumably some bits of code in the engine can be violated by selecting settlements not specified for some cultures in the engine.
    Last edited by Geoffrey of Villehardouin; June 05, 2018 at 07:43 AM.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •