Updated to work with version 1.202

The BlockDefinitionExtractor now works correctly as of game version 1.202 (it previously crashed due to not recognizing the new SabiroidPlushie component).

Added support to the "Most Wanted" update

The BlockDefinitionExtractor should now work properly after the "Most Wanted" update (the previous version crashed due to not recognizing the new "Engineer Plushie" component).

Fixed crash in BlockDefinitionExtractor when Steam is not installed

The BlockDefinitionExtractor should now work with Space Engineer servers where Steam is not installed. Game and mod paths have to be input manually.

Fixed crash during automatic detection of Steam library paths

• Fixed a crash during the automatic Steam libraries' path detection due to changes to internal Steam configuration files.

Fixed serious bug with some mod formats

• Fixed a bug that prevented the BlockDefinitionExtractor from reading the correct block files for mods with legacy folder structure.

Script now works with scenario saves and new mod folder/structure

• Fixed script not working with scenario save subfolders.
• Fixed script not finding mod folder, since it has been moved from previous location.
• Script now correctly examines *_legacy.bin packed mod files.

Updated to work with SE Economy update (1.192)

The script is now compatibile with Space Engineers' Economy update (version 1.192), since the folder structure of the main game has changed.

Added error message when trying to using the tool with unsupported mods

Added and error message when tying to generate block descriptions with mods that add new building components. Such mods are not currently supported.

Fixed crash in BlockDefinitionExtractor

This release of BlockDefinitionExtractor fixes an issue when a mod with no Data folder is installed.

BlockDefinitionExtractor - Initial release

Initial release of BlockDefinitionExtractor.

No dependency should be needed to run the exe version on Windows 10.
For older versions of Windows, Visual C++ Redistributable for Visual Studio 2015 might be needed.

Alternatively, you can run the .py script using Python on the command line.