what is godot-secure-templater fr?

Godot Secure Templater, called gst for short, is a command line tool that solves a specific problem for people making games with the Godot game engine. Normally, if you want to encrypt the scripts and resources inside your exported game so other people cannot easily read them, you need to set up a full C++ compiler toolchain by hand, wrestle with Python dependencies, and configure a build system called SCons. This tool removes that manual setup entirely. With a single command, gst create, the tool downloads and sets up everything it needs, including Python, a compiler, SCons, and the Godot source code, inside an isolated folder within your own project. It then generates an encryption key for your project and compiles Godot's export templates with that key built in. Once it finishes, it prints out the exact steps you need to follow inside the Godot editor to plug those templates and the key into your export settings, so your final game binary ships with its scripts and resources encrypted. The tool is smart about not repeating work: it remembers a fingerprint of the build inputs and skips recompiling if nothing has changed, though you can force a rebuild if needed. It also cleans up the downloaded toolchain after building, unless you ask it to keep things around for debugging. Right now, full support covers building Windows templates from a Windows machine and Linux templates from a Linux machine, with support for Android and Web export templates still planned but not yet implemented. You can install gst by downloading a ready made binary for your operating system and CPU type from the project's GitHub releases page, or by building it from source if you have Go installed. Getting started involves creating an export preset inside your Godot project, running gst create in your project folder, then following the printed instructions to finish exporting your game. The first run downloads roughly one gigabyte of toolchain files and needs about five gigabytes of free disk space. The team behind the project asks that the encryption key generated by the tool be treated as a secret and shared only through secure channels such as a secret manager or continuous integration system, rather than committed to source control.