I used a Windows 10 APP (9zip) to unpack the file. However, the Command Ops LnL version does not recognize the chinese lettering in the scenario file system. I changed the chinese lettering that shows up in the file system to "Nanking.cos" and was able to find the scenario with the CmdOps.exe New Game menu.Change the name of *.cos file in the /Scenarios/-Core Scenarios directory to ASCII letters, because currently it's not possible to unpack an archive.
I used a Windows 10 APP (9zip) to unpack the file. However, the Command Ops LnL version does not recognize the chinese lettering in the scenario file system. I changed the chinese lettering that shows up in the file system to "Nanking.cos" and was able to find the scenario with the CmdOps.exe New Game menu.
However, you need Version CmdOps.exe 5.1.31 to run the game, and that has not been released via LnL.
I wonder if there is any way to: export the "XML" file from "COE",XiYun,
I opened your scenario file, and fear you may create some confusion with the file naming conventions.
The BFTBEstab_Images file is a standard for the core game.
If you made alterations to that file and an unwary user unpacks it into the Estabs directory for the game, it changes the nature of the core file, leading to confusion in resolving problems they may encounter in the future.
In developing a scenario, you can use the images and information from BFTBEstab as a foundation, but when compiling the Estab, the XML and Estab.coe file should carry a new name to assure that any issues can be traced to the file which potentially caused the problem.
I'm sure as a skilled computer technician, you understand the critical nature of maintaining a standard to which the original developers can return for diagnosing issues versus trying to resolve issues from files that are duplicative of standard file names.
Unfortunately, I can't open the resulting scenario files using the current LnL version of the game. You have developed in the Steam Beta version, and that has not been officially released.
Again, as a skilled computer technician, I'm sure you understand the differences in performance in programs created under software versions. In doing full releases of software updates and patches, the Panther team has been careful to make software backward compatible in currently supported versions. Thus, if you had created your scenario in the officially released game version (currently designated 5.1.28) it would be playable using the currently available release, and would have been updated to include any refinements being tested under the 5.1.31 Beta testing release and any refinements from its feedback before the final release.
I don't think you can deconstruct a compiled (.COE) file into the data file from which it was constructed (.XML).I wonder if there is any way to: export the "XML" file from "COE",
I had a serious problem in the final stage of the script editing.
Sorry for the inconvenience that you can not open the script,
I originally thought that only non-steam users can normally update to 5.1.31.