• We have updated our Community Code of Conduct. Please read through the new rules for the forum that are an integral part of Paradox Interactive’s User Agreement.

Madranis

Corporal
14 Badges
Jun 7, 2018
25
0
  • Stellaris
  • Hearts of Iron IV: Cadet
  • Tyranny: Archon Edition
  • Stellaris: Leviathans Story Pack
  • Stellaris - Path to Destruction bundle
  • BATTLETECH
  • Stellaris: Synthetic Dawn
  • Age of Wonders III
  • BATTLETECH - Digital Deluxe Edition
  • Shadowrun: Dragonfall
  • BATTLETECH: Flashpoint
  • BATTLETECH: Heavy Metal
  • Crusader Kings II
  • BATTLETECH: Season pass
The existence of of the mod CBTMovementCore is an example of the motivational power of blazing through a mission only to be annoyed when it can't be finished due to a mod issue.

CBTMovementCore is a fork of the awesome CBTMovement mod. Like CBTMovement, it allows shooting after sprinting and adds ToHit penalties for the various forms of movement.

Unlike the original CBTMovement, CBTMovementCore doesn't add permanent evasion. Instead, that feature can be added with one of the quality mods which changes evasion removal if desired.

And most importantly, CBTMovementCore does not force missions to always be in interleaved combat mode. Not only does forcing interleaved combat mode slow down your ability to move about when out of sight of enemies but it also is responsible for making the Locura story mission unfinishable when using mods. The Locura story mission is finishable with CBTMovementCore in place of CBTMovement.

Note that starting the Locura mission with CBTMovement seems to render its state uncompleteable. You have to restart the mission if it's in uncompleteable state. Just removing CBTMovement and continuing the mission isn't enough.

If CBTMovementCore would be useful to anyone else, it's available on nexusmods or github.

The current version is 0.5.2 and is 1.6 compatible.
 
Last edited:
Just saw it on Nexus and immediately proceeded to the download. Haven't even tried it yet, but from the description this is just what BT needed.

In fact, I think that your mod will replace CBTMovement in the list of recommended mods for XLRP from 1.4 onward.


Also major kudos for figuring out what was breaking the Locura mission - I got at least half a dozen reports about it and and never quite figured out what the cause was.
 
The timing is a bit terrible with 1.6 just around the corner, but with me not being the only one getting burned try the Locura incompatibility I figured best to get it out so others can use it.

Hope it works well for you. Let me know if you find any problems.
 
The timing is a bit terrible with 1.6 just around the corner, but with me not being the only one getting burned try the Locura incompatibility I figured best to get it out so others can use it.

Hope it works well for you. Let me know if you find any problems.

Yeah, I'm curious to see how 1.6 will break stuff. :D

Just played a quick skirmish match with the mod and it works. Also quite a nice change of pace to have non-permanent evasion again after using CBTMovement for so long. :)
Think I'll have a look at semi-permanent evasion later, see how that works.

The only thing that I was surprised about is that units during the out of combat phase can't move simultaneously; meaning I can't select the next unit as long as the current one is still moving (even when sprinting). But I assume that's a limitation of how the system works.
 
The only thing that I was surprised about is that units during the out of combat phase can't move simultaneously; meaning I can't select the next unit as long as the current one is still moving (even when sprinting). But I assume that's a limitation of how the system works.

Odd. I wonder what is different. On my game with CBTMovementCore once you tell a mechwarrior to move the next is auto selected and can have its movement chosen even while the other is still in motion.
 
Odd. I wonder what is different. On my game with CBTMovementCore once you tell a mechwarrior to move the next is auto selected and can have its movement chosen even while the other is still in motion.

In that case it's possibly one of the many other mods I'm running on my end. Maybe I'll do a bit of trial and error to find out which if I get around to it.
 
By the way, is it allowed to re-distribute this mod as part of a mod package? I am looking to make getting the recommended XLRP experience a whole lot easier for users, and being able to include an (IMHO) essential mod such as this would tremendously help with this. There wouldn't be any changes to this particular mod, and I would of course include a license.txt if required.
 
Feel free to take it and use it however you want. I have no problem with it being included as part of a mod pack. I'm not concerned with how people acquire it so long as people can get a better BATTLETECH experience from it.
 
Feel free to take it and use it however you want. I have no problem with it being included as part of a mod pack. I'm not concerned with how people acquire it so long as people can get a better BATTLETECH experience from it.

Thank you!

By the way, I found out why I couldn't select the next Mech in simultaneous mode if the current one is still moving; I still need to hit the brace key to end it's turn (even when sprinting). I if do, the game automatically selects the next Mech as expected.
 
The timing is a bit terrible with 1.6 just around the corner, but with me not being the only one getting burned try the Locura incompatibility I figured best to get it out so others can use it.

Hope it works well for you. Let me know if you find any problems.

Glad to know that I am not the only one suffering from the Locura syndrome......
 
So far I haven't found any issues with CBTMovementCore and 1.6. I've done various skirmish and career missions without issue.

No idea why you'd need to push the brace button. I don't in 1.5 or 1.6. Once I click on a spot and facing the mech moves and the next pilot is selected to choose its movement in my game. I do wonder what's causing the divergence in behavior.
 
Version 0.5.2 is out on nexusmods and on github.

Release 0.5.2 fixes a bug when loading a save in the middle of combat. Version 0.5.1 would not correctly detect if combat on load of a save file was in interleaved mode, preventing being able to shoot after sprinting until leaving and re-entering interleaved combat mode. With 0.5.2, shooting after sprinting will work as intended even after loading a save file taken in the middle of combat.