Browser games, ports & AI: what’s the difference?
A browser is where a game runs. It doesn’t tell you how that game was made.
A browser is a platform, not a production method.
A browser game runs through a web page. That tells you where you access it, but not whether it was made by a person, assisted by AI, ported from another platform, or streamed from a remote computer.
A port and a remake are different projects.
A port adapts a game or its engine to a different environment. A remake or fan project may recreate only part of an experience. A familiar title in a social post does not establish that the linked project contains the full original game.
WebAssembly can be part of the picture.
WebAssembly lets browsers execute compiled code, and is one technology used in browser engine projects. It does not automatically supply the original game’s graphics, audio, or other assets. A project may ask you to provide game data separately.
Read the WebAssembly documentationAI involvement needs its own evidence.
A browser project can be AI-assisted, but the ability to run in a tab does not prove that. We keep AI involvement unverified unless there is a clear source from the project. The Radiant Optimizer list is a discovery starting point, not a technical audit.
Follow the project, not just the name.
Look at the destination’s own title and instructions. During our link review, the list’s Unreal Tournament destination identified itself as Urban Terror. That is why each directory entry keeps both its original listing context and any known differences.