A Call of Duty Map Has Moved Beyond the Minecraft Screen
A Minecraft player looking at a tiny computer screen that contains another game is a familiar kind of technical stunt. Luckey Faraday’s latest Black Ops 2 experiment takes a much bigger step. The developer says the Hijacked multiplayer map from Call of Duty: Black Ops II has been rebuilt to run directly inside Minecraft, with the map, collision, bots, navigation, weapons, and rendering operating as a Fabric mod. The September 2026 demonstration was reported by Tom’s Hardware, which describes footage running at about 45 frames per second through Minecraft’s OpenGL context.
That distinction is the story. The earlier version displayed a playable browser build on an in-game computer, so the FPS remained a separate application rendered as a surface inside Minecraft. In the newer version, the Minecraft game itself hosts the Java implementation and its graphics. The demo is an experimental recreation of a recognizable multiplayer map, not a way to launch the original Black Ops II executable, transfer its full codebase, or turn Minecraft into an official Call of Duty release. Understanding that boundary makes the project more impressive, because it shows the actual engineering problem the creator tried to solve.
What “Running Natively” Means in This Demo
In the creator’s public description, “natively” means that the port draws into Minecraft’s own OpenGL rendering context rather than sitting in a browser window or on a virtual monitor. The separate FPS simulation has been rewritten in Java and packaged as a Fabric mod. Minecraft supplies the host process and graphics environment, while the mod supplies the shooter’s map and game logic. That is a meaningful integration: the player can see the map as the main 3D scene, not as a screen embedded in a Minecraft room.
The word should not be mistaken for a complete conversion of Black Ops II. A map can be recreated from geometry and assets, and familiar interactions can be reimplemented, without carrying over the original game engine or every multiplayer system. The published description names key subsystems—collision, bots, navigation, weapons, and rendering—but does not establish feature parity with the commercial game. Nor does one short video prove that the code has the same stability, responsiveness, or network behavior as Treyarch’s original. It is best described as a playable Java recreation of one map running within Minecraft.
Hijacked Is a Compact but Demanding Test Space
Hijacked is a small yacht map from 2012’s Call of Duty: Black Ops II, built around tight interior routes and exposed decks. That layout is a practical choice for a first port. Players can recognize the central lanes and cover quickly, and the relatively bounded space is easier to rebuild than a large open-world level. Yet a compact map still tests more than scenery. A shooter environment needs reliable walls, walkable floors, doorways, stairs, sightlines, and cover that behave predictably when a character moves and aims.
Its scale also makes imperfections visible. If a corridor is too wide, a staircase catches the player, or a piece of cover does not block incoming fire, the map immediately feels different from the original. A successful recreation therefore depends on matching spatial relationships, not merely placing yacht-shaped blocks. The creator’s claim that collision and bot navigation are part of the mod points to these less photogenic details. Those systems determine whether the space supports play rather than only looking familiar in a fly-through.
The AI-Assisted Rebuild Came After a Browser Prototype
The project developed in stages. According to Faraday’s account quoted by Tom’s Hardware, the first experiment was a browser-based port of Black Ops II that could be displayed on a computer screen inside Minecraft. The creator then used GPT-6 Astra to rebuild that project in Java so it could run in Minecraft’s own graphics context. This sequence matters because the AI-assisted work did not begin from a blank prompt: a working browser prototype already expressed the target map and gameplay, and the developer had a concrete result to recreate.
That makes the story a useful example of AI as a coding aid in an iterative project. The model was assigned a substantial rewrite, but the human chose the target, supplied the existing implementation and constraints, integrated the output as a mod, and evaluated whether the result worked. The public report does not provide a full development log or independent code audit, so it cannot tell us which individual functions were generated, revised, or hand-written. What it does support is a narrower claim: AI was used in rebuilding a browser-based experiment into a Java/Fabric demonstration.
A Shooter Needs More Than a Map and a Camera
The feature list is notable because it reaches beyond rendering. Collision handling lets a player move through a level without passing through walls or falling through floors. Navigation data gives computer-controlled opponents a representation of where they can travel and how to move between areas. Bots require decision logic to choose movement and attacks. Weapons add firing behavior and feedback. Rendering turns the scene into visible geometry and effects. If these systems work together, the result feels closer to a game than to a static import.
There are still unanswered gameplay questions. The available demonstration and reporting do not specify how many bot behaviors are implemented, how weapon balance compares with Black Ops II, whether objectives or round rules are present, or how well the port handles repeated matches. A system can contain bots without reproducing the original artificial intelligence, and a weapon can fire without matching its source game’s recoil, timing, or damage. Those details are normal unfinished work for a proof of concept. They simply mean that “all running inside Minecraft” describes the port’s location, not the completeness of its mechanics.
The 45 FPS Figure Is a Snapshot, Not a Benchmark
Tom’s Hardware describes the video as running at roughly 45 FPS. That is useful context: the scene was moving at a playable-looking rate in the shown capture, rather than appearing as a sequence of still images. But a single reported frame rate cannot establish how the mod performs on other computers or under different conditions. The article does not give a standardized test setup with processor, graphics card, render resolution, frame-time chart, or a repeatable benchmark route.
Minecraft and a custom shooter renderer also share the same host environment, so performance depends on how the mod uses the game’s rendering pipeline and how much work is done each frame. A smooth segment may not represent busy scenes, long sessions, or larger maps. Until the developer publishes repeatable measurements, the responsible reading is straightforward: the demo reportedly reaches about 45 FPS in the shown setup. It is evidence that the approach can render a real-time scene, not a guarantee that every player can expect that number.
What Players Can—and Cannot—Assume They Can Download
The coverage establishes that a working demonstration exists, but it does not provide a verified public release page for the Minecraft Fabric port, installation instructions, supported Minecraft version, or a list of required assets. The earlier browser project has a public GitHub repository, but that repository should not be confused with a downloadable build of this later native mod. Readers should follow the creator’s original post and linked project pages for any release announcement, and check that a page specifically refers to the Fabric implementation before installing files.
That caution is especially useful for projects described as AI-built. Short clips and reposts can spread faster than the source code, and a filename or screenshot is not proof that a download is authentic. Do not run an unknown executable just because a social post says it is needed to play the port. If the creator later shares source or a packaged mod, check the documented Minecraft and Fabric versions, inspect the installation steps, and preserve backups of existing worlds. At the time of the cited report, the developer still described the work as having more to do.
Why This Crossover Is Different From Minecraft Ring
Minecraft Ring, another recent experiment, brings Minecraft-style actions into Elden Ring by connecting two separate games. The Hijacked port takes the opposite route: it recreates a slice of a shooter inside Minecraft’s modding environment. One project bridges live game processes so one game’s character and actions appear in another game’s world; the other ports a map and shooter systems into the sandbox host. Both are mashups, but their architecture and the questions players should ask are different.
The comparison also helps explain what “AI-assisted crossover” can mean. These projects are not evidence that a model has merged two commercial games automatically. They are human-directed prototypes that use code generation alongside game-specific decisions, debugging, integration, and testing. In the Hijacked case, the visible result is particularly clear: a familiar Call of Duty map appearing as an FPS scene within Minecraft. The technically important part is the implementation boundary—Java mod, host rendering context, and recreated gameplay systems—not a claim that the original game has somehow been absorbed wholesale.
A Promising Proof of Concept With Clear Next Questions
The next useful milestone would be documentation that lets other developers reproduce the demo: a public Fabric mod repository, exact game and loader versions, build instructions, and an honest list of known limitations. For players, the most informative updates would show longer gameplay sequences, more bot behavior, a full match loop, and performance across more than one machine. Multiplayer, additional maps, and expanded weapon options are possibilities mentioned in coverage, but they should be treated as future ambitions rather than existing features.
For now, this AI-assisted Black Ops II experiment is worth attention because it crosses a visible technical threshold. The Hijacked map is not merely shown on a Minecraft screen; its Java recreation is described as rendering directly in Minecraft, with several core shooter systems present in the mod. The creator and reporting still frame it as unfinished, and the public evidence does not establish a consumer-ready release. That measured conclusion preserves both sides of the story: the demo is a striking example of what a determined modder and AI coding tools can prototype, and it still has a distance to travel before it becomes an easy, complete way to play.