How kyzaboy/azoth-launcher-releases works
This is a release-hosting repository, not the launcher’s source code. The documented workflow is: a user downloads and runs a Windows installer; the installed launcher checks projectazoth.com for updates, downloads an installer from GitHub Releases, verifies it against a server-published SHA-512, and installs it. Releases also publish SHA-256 sums for manual checks. The README notes that the launcher patches the game client in memory. No source excerpts or release files were provided, so relationships below are based only on the README.
Main entry points: README.md Launcher installer
Components 8
Other components
- Windows user
- GitHub Releases
- Launcher installer
README.md - Azoth Launcher
- Project Azoth server
- Per-user installation
- Game client
- SHA256SUMS.txt
README.md
Connections 11
- Windows user → GitHub Releases: gets latest
README.md - GitHub Releases → Launcher installer: provides download
README.md - Windows user → Launcher installer: runs
README.md - Launcher installer → Per-user installation: installs per-user
README.md - Azoth Launcher → Project Azoth server: checks version
README.md - Azoth Launcher → GitHub Releases: downloads installer
README.md - Project Azoth server → Azoth Launcher: publishes SHA-512
README.md - Azoth Launcher → Per-user installation: verifies then updates
README.md - GitHub Releases → SHA256SUMS.txt: lists SHA-256
README.md - Windows user → SHA256SUMS.txt: checks download
README.md - Azoth Launcher → Game client: patches in memory
README.md