Please check the description page for the patch notes, version compatibility, and known issues.
An incomplete bug report is better than no bug report! I sometimes break unrelated features when I add new ones, and I can't test all combinations again and again. Game patches can also do that. If you think something isn't working correctly just drop a message and I'll check it out.
good afternoon, the mod is good, all the mechanics work, especially the repulsion and overturning of enemies pleases. BUT there is a problem in my version of RMB and game 1.1.2, I noticed that horse damage is dealt in proportion to the damage dealt by the enemy... and I can't change this with a setting! maybe someone faced the problem?
This caused my self-created lance to not have cou-chable and bracing properties. Is there any workaround to this? I've just made the switch from e.1.8.0 to v1.0.3 of the game after a long break from the game.
DSMN doesn't directly read XML files but instead hooks deserialization methods, so it's directly "fed" with what the base game reads and any manual change made to those files should be seen and added to "WeaponProperties_Default.yaml" every time a save is loaded or a new game started (at least that's the intend, if your custom changes can't be found in this file then something's wrong). That file is then copied to "WeaponProperties.yaml" if it's missing, and it's this file that tells which crafting pieces / weapons should receive dismount flags and couchable / braceable properties.
What it means is if you've loaded a save or started a new game with DSMN installed but without your custom changes, then left the game and modified the game's XML files, then your changes won't be applied to "WeaponProperties.yaml" (because it's only generated if it's missing). In this case, deleting "WeaponProperties.yaml" or renaming "WeaponProperties_Default.yaml" to "WeaponProperties.yaml" should work (you can access the mod's folder easily from MCM's menu).
If your changes are completely absent from "WeaponProperties_Default.yaml", I'll need to have a look at your XML files.
I'm not sure if there's a way for me to tell the difference between actual default values and manual changes to the XML files, so yeah, that means you have to delete / regenerate "WeaponProperties.yaml" every time you change something in the XML files. I would probably be smart to warn the user if "WeaponProperties_Default.yaml" appears outdated though.
As what you've suggested, by deleting "WeaponProperties.yaml" and the loading a save file, the weapon properties such as couchable is applied to the weapon which I edited in the xml file. Thanks for the solution.
Give Feedback
256 comments
Please check the description page for the patch notes, version compatibility, and known issues.
An incomplete bug report is better than no bug report! I sometimes break unrelated features when I add new ones, and I can't test all combinations again and again. Game patches can also do that. If you think something isn't working correctly just drop a message and I'll check it out.
A mod translation file wouldn't hurt here...
If it was working on 1.1.2 I suppose it's likely it'll work on 1.1.3 based on how short the patch notes are.
[Native] folder
crafting_pieces.xml
crafting_templates.xml
weapon_descriptions.xml
[SandBoxCore] folder:
weapons.xml
This caused my self-created lance to not have cou-chable and bracing properties. Is there any workaround to this? I've just made the switch from e.1.8.0 to v1.0.3 of the game after a long break from the game.
What it means is if you've loaded a save or started a new game with DSMN installed but without your custom changes, then left the game and modified the game's XML files, then your changes won't be applied to "WeaponProperties.yaml" (because it's only generated if it's missing). In this case, deleting "WeaponProperties.yaml" or renaming "WeaponProperties_Default.yaml" to "WeaponProperties.yaml" should work (you can access the mod's folder easily from MCM's menu).
If your changes are completely absent from "WeaponProperties_Default.yaml", I'll need to have a look at your XML files.
I'm not sure if there's a way for me to tell the difference between actual default values and manual changes to the XML files, so yeah, that means you have to delete / regenerate "WeaponProperties.yaml" every time you change something in the XML files. I would probably be smart to warn the user if "WeaponProperties_Default.yaml" appears outdated though.