while both the issues i mentioned happen quite frequently while using mod packs (bex ce is the only one that uses the ISM)
remember these mods existed before 1.8....without these issues....
1.8 caused these issues....seems like that it is something HBS did then
and besides that...these issues first appeared for me ( though they were as frequent ) while playing a mod-free Vanilla Campaign run.
i wouldnt expect HBS to fix things cuased by the mods themselves.
but when an issue exists in VANILLA and happens more often with mods telss us there is a underlying issue with code HBS wrote,.
my expectations are exactly where they should be.
HBS created code that breaks the game in vanilla and with mods
i expect them to fix it.
hopefully 1.9 does so.
We’ve already got an excellent case in point, in order to best address Convoy AI, HBS is reaching back to a legacy build where the Long Range Pathing Algorithm as it turned out, substantially outperformed what HBS has used in 1.8
Code does not always move forward.
In this case HBS has now developed a new Short Range Pathing Algorithm that in-house dovetails nicely with the legacy Long Range Pathing Algorithm.
But yes, the return of legacy code could unhinge this or that mod and reintroduce conditions that may or may not drive a return of this or that big.
What I am driving at here is that with Update 1.9 the Onus for moving BATTLETECH forward will shift enormously to our Modding Community....
...and yes, it’ll be our Baby and it may sometimes be an ugly Baby as individual Modders prove to be TOO aggressive and demanding of code that was only written to support four Mechs and what? ...170 Star Systems.
Modding will move our Community forward, but it will not be without its firs and starts.
I believe we mustn’t go into this with a Glass Half Empty Attitude of “HBS left some bugs in the game.”
Be use in all reality tens of thousands of Bugs have been annihilated since the times of “Refrigerator” Mechs back in early 2016.
Let’s accept the Onus to make the most of BATTLETECH moving forward and as a Community own the fact that just about EVERY SINGLE Mod asked more of the BATTLETECH code than it was ever meant to give.
HBS has crafted a remarkably docile and malleable game game, but it ain’t meant to give what we will ask of it.
Let’s celebrate the success sure to come, but not blame HBS for the upcoming challenges, rather instead let’s back that various Patreon accounts of
@CWolfs,
@bloodydoves,
@LadyAlekto,
@Amechwarrior and so very many others so that our Modding community has the wherewithal to dedicate the time and talent needed to successfully craft the BATTLETECH Mods we want to see.
Because In so many ways that matter, we will get out of Modded BATTLETECH what we put into it.
And as a Community, we’ll soon have no one to blame but ourselves if in 6-months or a year, we don’t have the make and manner of BATTLETECH game that we want to see... want to play... want to share with one another.
:bow: