@drtbkj @Tomcattwo nailed the answer!
I would add that there has been some talk going to all .zip.acmi format to use TacView exclusively and BMS leaving the antiquated ACMI viewer and its .vhs format since 4.37 (not even U1) hence why they added the config line edit we have to use to turn back on the .vhs. LSOBot in its current state will only work as long as the .vhs is an option. Either LSOBot would have to be updated to the new BMS .zip.acmi or whatever is being removed by BMS’s file added back in so that LSOBot recognizes passes. Updating LSOBot could potentially allow .zip.acmi support so no TacView conversion necessary. But eeven if that is still necessary to go from .zip.acmi to .txt.acmu, you would save the .vhs conversion that you need to do now.
The .vhs format is a Falcon 4.0 only file extension and only a handful of converters like TacView and flt2vhs exist as well. TacView is definitely the modern standard as @Tyrant was trying to embrace anyway when he made LSOBot. The .vhs format can also be quite large and can take a lot of time to compile on 3d world exit. If you ever had a really long hang after exiting a campaign mission that you recorded pre 4.37, that’s why. Also Falcon 4.0 and most versions of BMS have a file size limit to .vhs as well. There are many reasons as I and I think BMS sees it to leave it behind.
Honestly, I like the post 4.37 ways of doing things that I will only enable .vhs for grading passes since I like to record full missions and have recording turned on by default.