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.