Caching and updates
During connection, the server sends a manifest describing client files and their content hashes. The client compares it with its cache, downloads changed content, verifies it, and prepares the package before client scripts run.
Keep resource paths stable between releases. Renaming large files forces a new download even when their content is unchanged. Remove obsolete files from the server tree so they disappear from the next manifest rather than remaining part of the package.
Mounted GTA data
GTA streaming and data-file registrations live for the game process. VIMP can reuse an already mounted package when its package hash matches. If the requested package differs, connection stops with a restart message instead of mixing two sets of model metadata.
After changing a vehicle, map, MLO, YTYP, or metadata file:
- Restart the game server so it publishes the new manifest.
- Fully exit GTA on the test client.
- Start VIMP and reconnect.
- Confirm the new download and mount in client logs.
Ordinary CEF or script iteration may not require the same GTA data reset, but a full restart is the reliable test path for release candidates.