Implemented so far:

• Using the commit-hash for rough versioning of the .zip-files (info.txt)

Planned to implement:

• Generate a changelog and version number using commits and their messages.
  For version number:

  • Start at 0.0.0
  • For each build using this tool, count up the last decimal.
  • Adding any tag would count up the middle decimal.
  • Adding a "release" tag would count up the first decimal.

  For changelog:
  Could just use the plain commit-messages for regular (testing-friendly-)builds and filter with RegEx for customer-friendly-builds. (Split by lines in commits and look for a [CUSTOMER]-prefix, to qualify a line of commit-comment for the customer-friendly-build-log or something like that.)

Currently a mix between in credentials.dat

Configurable items:

• Path to engine-files
• Path to project-files
• Path to 7z-executable

Merge credentials.dat to said config-file and #2.

Ideas:
Shell based-wizard?

Assigned highest priority

Current steps:

• Do engines qualify?
  • Look up general cross-platform support of engines themselve
  • Find possible differences between CLI across different OSs.
• Implement into separate executables

Switch to cross-compiling C(++) for that. Would allow for easier distinction between "new features" and adding support for new engines/OSs.
Allow for easy downloading of binaries. (GitHub release-tags?)