"Move To Reserve" Siege Equipment Deployment Broken

[Lt. Nate Drake]

On latest update, If you move the siege engine to reserve, the defender's siege equipment will still target the empty space, fire and destroy your engine (which was in reserve).
Doesn't happen on 1.2.10

[elysebluemoon]

Do you have any mods installed? Can you send us your save file via our ticketing system? Please don't forget to include your thread's link in your ticket. You can find a guide on how to open a ticket and send files below:
https://steamcommunity.com/app/261550/discussions/17/3086646248532468263/

(BSS-6442)

[elysebluemoon]

Forwarding this issue to the QA team for further investigation. Thanks for reporting.
(BES-9324)

[EmotionallyBroken]

Originally posted by Lt. Drake:

On latest update, If you move the siege engine to reserve, the defender's siege equipment will still target the empty space, fire and destroy your engine (which was in reserve).
Doesn't happen on 1.2.10

Ive noticed this as well, however I also notice that it is only one shot (Which doesnt usually destroy mangonels , but does catapults and ballistae ) It seems to check for the presence of the siege engine before shooting and not after, which logically makes no sense game design wise, and realistically no one owuld build a siege engine on wheels under fire when they can just build it out of range with a bunch of other ones and then roll into position when ready)

So what I do as a "work around" is to make two mangonels or more first, then deploy them as the 3rd engine finishes.

I am using mods though none related to sieges in their intended function.
If this is a rare issue and not an "everyone has it" issue please respond with a mod list and maybe we can narrow it down in its cause. :)

[elysebluemoon]

The QA team could not reproduce this issue on our current build and determined that this occurs due to mods.
Unfortunately, we cannot offer technical support for modded games and I cannot forward this to the developers without first making sure that mods aren't causing the problems. Please read our full statement regarding modding related issues.
https://steamcommunity.com/app/261550/discussions/17/2968397584539419311/
Can you try removing all of your mods by performing a clean install following the instructions on the below article and try to recreate this on an unmodded new campaign?
https://steamcommunity.com/app/261550/discussions/17/2968397584539744282/
As save files remain altered and some leftover mod files remain even after deleting the mods, a clean install and creating a new campaign is necessary to see if the problem is isolated to the modded game or if it's a problem from our end.
Alternatively, I can move this thread to the General Discussions board where the community might help with which mod is or isn't compatible with the game's current version, or you can contact the mod developers.

[Lt. Nate Drake]

@elysebluemoon_TW Thank you for the help.
Upon verification of mods through process of elimination, I've found out that RBM (Realistic Battle Mod) is the culprit. It works fine in 1.2.10 but in 1.2.11 , perhaps the rate of fire and chance to hit of the siege engines are not compatible or messing up with the latest build.

Either go back to 1.2.10 for RBM to work properly until the mod gets an update and fix.
Try Range reload from vanilla to semi-realistic

OR

A temp little fix messing with xml of the mod:
1) Go in Mount & Blade II Bannerlord\Modules\RBM\ModuleData
2) Backup the xml file "RBMCombat_siege_engines"
3) Open and Edit the xml file "RBMCombat_siege_engines"
4) Decrease the hit_chance and anti_personnel_hit_chance of all the engine types (except towers , ladders) from 1 to 0.5 (or less).
5) You can also edit the damage and hitpoints. (haven't tested stability yet)
6) If the game crashes, use the xml backup "RBMCombat_siege_engines".

I really hope we will get a good siege prep-phase rebalance one day.

[elysebluemoon]

Glad to hear the issue is resolved for you! :)