A browser engine is not the game-data package
Browser ports move an engine into a web page, often through WebAssembly. That does not automatically provide the original maps, textures, audio or campaign data. Before trying an unfamiliar archive, check exactly what the maintainer requests and whether you are entitled to use those files.
In this collection, the file formats are not interchangeable. An Xbox Halo disc image, a Vice City archive and a Diablo MPQ each belong to a different engine and import flow. A successful upload to one project says nothing about another project’s compatibility.
Desktop Halo: an owned Xbox XISO
Mitchell Hynes’s Halo page displays a Choose your Halo XISO dialog. It explains that the site does not provide game data and asks for an XISO made from your own Xbox Halo: Combat Evolved copy. The page links its community for disc-ripping instructions; this directory does not replace that process with a file mirror.
After the engine accepts compatible data, its Focus game button or canvas click captures mouse input. The on-page Duke diagram maps movement to WASD, aiming to the mouse, A to Space and B to F. This interface evidence is useful setup information, even though we did not complete campaign gameplay.
HCEMobile: maps copied to private browser storage
HCEMobile describes accepting .iso or .xiso, extracting the maps folder and retaining it in private browser storage. Its current guide estimates that folder at up to 1.8 GB. The site says nothing is uploaded from the selected image and that the disc image can be removed after the map copy completes.
Its alternative URL import needs a direct download link to your own disc image. A sharing page is different from a direct file URL; the source specifically says Google Drive and ordinary sharing pages do not work. Do not confuse the desktop Halo loader with this separate mobile-oriented import flow.
Vice City: game.tar.gz, saves and skins are separate
The joncodeofficial port has a game.tar.gz import screen and describes storing imported data through OPFS and a Service Worker. Wait for the import and local-storage confirmation before pressing Start to play. Clearing data for that original host may require importing again.
PC saves in .b or .zip format and player skins have separate controls. A skin import is not a game-data import, and the source says skins change the street outfit rather than cutscenes. Keeping those operations distinct avoids diagnosing the wrong missing resource.
Diablo: a demo path versus the full-game MPQ
Diablo Web explicitly describes a shareware demo and a full-game option using an owned DIABDAT.MPQ. The existence of the demo does not make all entries in the Radiant list asset-free. Choose the path you actually have the requirements for.
Game progress and exports belong to the original host. Read its save instructions before clearing browser storage, moving to another device, or assuming a browser refresh will preserve everything. Favorites saved by our directory are only a list of links, not your game saves.
A short pre-launch checklist
Confirm the project name, supported file format and edition. Check available device storage before a large import. Keep the tab open until the host completes its own resource stage. If the loader reports an unsupported archive, return to the maintainer’s instructions rather than repeatedly renaming a different file.
Our guides link the exact source hosts so that changed requirements are easy to verify. File behavior described here was reviewed on October 10, 2026; the original project’s current documentation takes precedence.
