Restore archive first modern client asset installation
This commit reworks the modern client asset auto installation flow so the normal path is based on downloading and extracting the GitHub release or source ZIP instead of relying on the manifest flow as the primary installer.
The installer now keeps the final runtime files in the same locations already expected by OTClient. Asset files are installed under data things version, sound files are installed under data sounds version, and configured runtime extras are installed into their expected runtime locations such as bin.
The manifest based path is still kept as a compatibility fallback, but it is no longer the preferred installation path for modern client assets. This restores the archive first behavior and makes the install result match the standard runtime loader layout more directly.
For client versions 1281 and newer, OTClient now checks the existing files under data things version before attempting installation. When auto install is enabled and the required files are missing, the client prompts the user, downloads the configured release or source ZIP, extracts the assets folder into data things version, extracts the sounds folder into data sounds version, and installs configured runtime extras into their target runtime paths.
If Services clientAssets enabled is false, OTClient now skips the asset ensure download flow during login. This avoids recursive login attempts caused by the installer prompt and keeps manual or custom asset folders usable. In that mode, OTClient proceeds with the provided local files and lets the normal runtime loader report missing or invalid assets when appropriate.
The archive extraction support was also expanded. ZIP extraction now works through the vendored minizip fallback when libarchive is not available. Visual Studio project configuration was updated to enable libarchive so Windows builds can handle ZIP and RAR archive extraction. Android builds remain safe because unsupported libarchive linkage is not required there.
Main changes included in this commit
• Restores archive first installation for modern client assets
• Keeps the manifest path only as a compatibility fallback
• Downloads the GitHub release or source ZIP as the normal install path
• Extracts assets into data things version
• Extracts sounds into data sounds version
• Installs runtime extras into their expected runtime locations such as bin
• Keeps final installed files in the same OTClient runtime paths already used by the loader
• Adds ZIP extraction support through the vendored minizip fallback
• Enables libarchive in the Visual Studio project for Windows archive extraction
• Allows Windows builds to handle ZIP and RAR extraction through libarchive
• Preserves Android build safety by not requiring unsupported libarchive linkage
• Skips asset ensure and download prompts when Services clientAssets enabled is false
• Avoids recursive login attempts when asset auto install is disabled
• Keeps manual and custom asset folders usable
• Lets the normal runtime loader report actual missing or invalid files when auto install is disabled
• Documents the archive first flow fallback behavior install paths and troubleshooting notes
Runtime behavior
For modern client versions 1281 and newer, OTClient first checks the existing files under data things version. If the files are already present, login continues without triggering the installer.
If files are missing and auto install is enabled, OTClient prompts the user and installs assets from the configured GitHub release or source archive. The archive folders are mapped into the runtime locations expected by the client.
The assets folder is installed into data things version. The sounds folder is installed into data sounds version. Runtime extras such as bin files are installed into their configured runtime destinations.
If auto install is disabled, the installer is not called during login. The client continues with the manually provided files and the regular loader remains responsible for reporting any actual asset problems.
Verification performed
• luac p modules client assets client assets lua init lua
• luac p modules client entergame entergame lua
• git diff check
• Local Windows build using vc18 otclient sln OpenGL x64 Build
• GitHub Actions fast checks passed on the PR branch
• GitHub Actions Lua syntax checks passed on the PR branch
Overall this commit restores the expected archive based installation flow for modern client assets while preserving compatibility fallback behavior. It keeps installed files aligned with the existing OTClient runtime layout improves archive extraction support across build targets and avoids unwanted installer prompts when automatic asset installation is disabled.
Add spdlog as the new logging backend and refactor the codebase to use the centralized g_logger interface instead of direct stdout and stderr output.
Main changes:
- Add spdlog-based logger implementation.
- Replace direct std::cout, std::clog, std::cerr, and std::endl usage with g_logger calls.
- Add log level support for debug, warning, error, and related output paths.
- Add consistent console and file logging through spdlog sinks.
- Add custom log formatting and startup timestamp logging.
- Add dynamic sink management for logger output.
- Refactor HTTP and proxy logging to use g_logger with appropriate log levels.
- Add sanitization and redaction for HTTP request and response logs.
- Improve log consistency so output can be filtered and managed from one logging path.
Build changes:
- Add find_package(spdlog CONFIG REQUIRED).
- Link spdlog::spdlog_header_only in the CMake build.
- Ensure the logging dependency is available across supported platforms.
Cleanup:
- Remove unnecessary iostream includes from files that no longer use direct stream logging.
- Remove unused logging-related includes from the precompiled header.
- Adjust output formatting, newline handling, and flush behavior around the centralized logger.
This modernizes the logging infrastructure, reduces ad-hoc console output, and prepares the client for cleaner log filtering, file logging, and safer HTTP diagnostics.
Add automatic client-asset installation for modern Tibia versions in OTC, with the UI and runtime support needed for a safe download-and-install flow.
Main changes:
- Add modules/client_assets to orchestrate descriptor and release resolution, downloads, retries, cancellation, archive extraction, optional LZMA handling, and SHA-256 integrity checks.
- Add richer install logs in the console, including download phases, install phases, and final install paths.
- Add support for packaged runtime files, including large DLLs distributed through archives.
- Make client_entergame depend on client_assets.
- Check required assets during login for modern clients version 1281 and newer.
- Prompt the user to download missing modern assets instead of requiring manual setup.
- Allow the client list and version selection to work with installed modern asset sets.
Install layout:
- Install things assets under data/things/<version>.
- Install sound assets under data/sounds/<version>.
- Keep extra runtime files in the existing client root/bin flow.
- Preserve the existing OTC asset layout as the source of truth instead of introducing a separate permanent path.
UI improvements:
- Improve missing-assets and progress dialog sizing and text wrapping.
- Improve progress behavior for downloads without Content-Length.
- Add indeterminate progress behavior for unknown-length phases.
- Add an hourglass busy indicator for indeterminate phases.
- Reduce the perception that the installer is stuck during long extraction steps.
Runtime and build support:
- Add libarchive usage and linking for archive extraction.
- Add SHA-256 helpers and Lua bindings used by client_assets.
- Add safer extraction and path normalization in ResourceManager.
- Adjust the Emscripten HTTP login path to follow the same HTTP/HTTPS fallback behavior used by native login.
Security and integrity:
- Enable strictManifestSha256 by default.
- Disable raw fallback on hash mismatch by default.
- Key releasesCache per source URL and repository to avoid stale cross-source cache reuse.
- Add an LZMA decompression output cap to reduce memory-exhaustion risk.
Compatibility:
- Keep existing classic asset behavior unchanged.
- Use the new auto-install flow only for modern versions when required assets are missing.
- Keep the scope limited to client-side asset automation and required runtime support.
- No server-side Canary behavior is changed by this PR.
This makes modern client setup safer and more automatic by downloading, validating, extracting, and installing missing assets directly from OTC while preserving the existing classic asset flow.
- Introduced a new miniwindow header image for UI.
- Created a new style file for the miniwindow battle interface, defining layout, buttons, and scrollable content.
- Configured button states for close, minimize, and toggle filter functionalities.
- Established visual elements such as borders, backgrounds, and dimensions for a cohesive design.
- Multi-Instance battle list feature.
- Filters and Orderings for each instance.
- Lock buttons specific to each instance.
- Keep open/re-launch when relog/exit game.
- On close, it destroys the instance, cleaning up its settings.
- A bunch of safety checks and locks to ensure they are working properly, and update all windows accordingly.
* All modules are sandboxed now
* All images,sounds,fonts,translations and styles were moved to "data" folder
* Reorganize image files folders
* Remove unmaintained modules: client_particles, client_shaders
* Implement new automatic way to load styles and fonts
* Add hide/show offline option in VipList
* Add invite/exclude to/from private channel in players menus
* Many other minor changes
Lots of chagnes to add multi protocol flexibility, not really
completed yet, still have to rework text messages opcodes and other stuff,
so this still a working in progress feature
* Rework dat reader, the dat reader can now
* dinamically detect dat version
* Split game into gamelib and game_interface
* Lots of other minor changes
When otclient initializes it tries to find all .otpkg files inside the
current search paths (./ ./modules ./addons) and then add them
to the front of current search paths. This way .otpkg can contains
many modules/addons and modifications in a single file that otclient
can recognize.
otpkg files can be compressed files supported by PhysFS, which
are ZIP (.zip) and LZMA (.7z).
