These projects provide a browser engine or interface, not the complete commercial game data. Each card leads to the exact file boundary and current source evidence.
“Needs Files” means the project says visitors must provide some form of game data from a copy they own. The expected input is not universal: one project may request a disc image, another a folder, MPQ file, or prepared archive. Read the individual guide and current project documentation before selecting anything from your device.
Do not replace missing files with an unknown mirror or prepacked download. Preserve your originals outside browser storage, and stop if a site unexpectedly asks for an executable or extension.
Status, requirements, evidence scope, and review date stay visible on every entry.
Source 07Needs FilesProject interface · Oct 10, 2026A fan browser project that explicitly depends on data converted from a copy of Skate 3 you own.
Source 10Needs FilesProject interface · Oct 10, 2026A community Halo CE browser engine that requires game data prepared from an original Xbox copy you own.
Source 11Needs FilesProject interface · Oct 10, 2026A mobile-oriented Halo CE browser project that still requires owned Xbox game data and capable hardware.
Source 14Needs FilesProject interface · Oct 11, 2026A WebAssembly engine project that imports Vice City data from a game.tar.gz you prepare from your own legal copy.
Source 22Needs FilesProject interface · Oct 11, 2026A WebXash browser engine that loads valve or cstrike folders from a copy you own and is intended for keyboard-and-mouse desktops.
Source 23Needs FilesProject interface · Oct 10, 2026A WebAssembly Diablo project with a limited shareware path and a full-game path that requires your own DIABDAT.MPQ.
The local browser check can show whether common APIs are exposed on this device. It cannot validate your game data or prove a project will work. For import errors, use the missing-files checklist; for the complete source list, return to all entries.
