Our sandbox built 2010-rust-rewrite-mashup in 628 seconds, but its successful test command reported zero tests. Try it if shooting through a Minecraft world and skating around MW2 maps sounds worth some troubleshooting. Skip it if you want a dependable replacement for any of the original games.
The project combines IW4L, a Rust runtime for Modern Warfare 2, with Skate 3 mechanics and a Minecraft world. The interesting question is whether those systems work together well enough for the session you want to have. Our source build, community reports and current release notes answer different parts of that question.
What people use 2010-rust-rewrite-mashup for
People have used the crossover for Minecraft combat demonstrations, skating on MW2 maps and compatibility experiments, with quite different outcomes.
| Who tried it | What they did | What the source supports |
|---|---|---|
| Chasm, described in a reposted demonstration | Demonstrated Minecraft terrain generation, damage and crafting | The repost describes those interactions and explicitly attributes parity claims to the author. |
| Mudahar, according to a third-party video summary | Shot Minecraft animals, collected drops and broke blocks | The summary reports working interactions alongside reloading, skating and building problems. |
| GitHub commenter pubert69 in issue #29 | Skated on Terminal and dropped down ramps | They reported stable frame rates but no skating controls until switching from a PS5 Edge controller to Xbox. |
| GitHub commenter Zebratic in issue #23 | Ran it on Linux through Proton Experimental | They reported success and described putting curl.exe beside iw4l.exe. |
The Terminal report explains the appeal better than a feature list. A player could get onto the board and descend a ramp, yet could neither push nor do tricks. Replacing the controller changed the experience from watching the board move to controlling it. That's a useful success report because it includes what went wrong first.
For your first session, choose one interaction you care about. If it's Minecraft combat, check shooting, drops and block breaking before spending time on skating files. If it's skating, check pushing and tricks before exploring a map. Those are recommendations for evaluating the crossover, rather than additional gameplay results from our lab.
What happened when we ran it
Our November 13, 2026 source run at commit f608f85 installed successfully in 37 seconds, built in 628 seconds and completed its test step in 148 seconds with zero tests reported.
| Source-run step | Recorded outcome | What it tells you |
|---|---|---|
| Install | Succeeded in 37 seconds, 682 dependencies recorded | Dependency setup completed in this sandbox. |
| Build | Succeeded in 628 seconds | The recorded source build completed. |
| Tests | Succeeded in 148 seconds, cargo test: 0 passed, 0 failed of 0 | The command succeeded without a reported executed test case. |
The recorded configuration was 3 CPUs, 12 GB RAM and image label lab-rust:1. The checkout contained 2,905 files, approximately 703,192 source lines and occupied 27.4 MB. The scan found zero CI workflow files, no Dockerfile and no tests directory. These are checkout observations, including vendored material, rather than a count of code written specifically for this mashup. The image label supplies neither the actual Rust toolchain version nor the operating-system version.
Zero reported tests changes how much reassurance the green result offers. A completed compilation is useful to someone who wants to inspect or modify the source. It supplies no gameplay regression coverage on its own. In particular, it cannot tell a player whether a controller can push the board or whether the inventory draws an item's icon.
A separate hands-on attempt stopped at its safety precheck because no Compose file existed. The specific failure record lists compose.yaml, compose.yml, docker-compose.yaml and docker-compose.yml as absent. That is a requirement of our deployment harness, not evidence that a desktop game should ship a container stack.
The generic run summary nevertheless describes deployment through the project's own Docker Compose, with ports bound to 127.0.0.1. It conflicts with the failed precheck. We give the specific step precedence and report a blocked hands-on deployment, followed by successful teardown. There is no completed gameplay task to report from that attempt.
Where people get stuck: match the symptom before trying a fix
The issue tracker separates launch failures, asset downloads and controller problems, so a workaround for one symptom should stay attached to that symptom.
| Symptom and source | What the reporter encountered | Resolution recorded in the supplied thread |
|---|---|---|
| Issue #10: launch after 0.3 | The pc_options_video menu had no item 28, including after a fresh install | Open. One person said it recovered spontaneously, without a reproducible fix. |
| Issue #17: same menu error | A launch failure with logs attached | Open. vladtrc linked an upstream pull request, without a confirmation of a working release in this thread. |
| Issue #23: Minecraft returns to menu | The Mojang download failed with curl exit code 3 | Open, with reports of success after moving the folder to C:/ or placing curl.exe beside iw4l.exe. |
| Issue #26: command log, no rendering | The log stopped without an error | Closed after a dual-GPU user supplied a custom batch-file workaround. |
| Issue #29: no skating controls | Mode switching worked, pushing and tricks did not | Closed after the reporter changed from PS5 Edge to Xbox. |
| Issue #15: crafting table | Interaction attempts did nothing | Open. A commenter described a GUI-enabled version under testing, rather than a released fix. |
The download story is particularly easy to misread. The player in #23 selected the Minecraft world, saw a freeze and landed back at the menu. The log narrowed the failure to curl returning exit code 3. Wet-Band-Aid then reported success after moving the installation directly to C:/, while Zebratic reported success with curl.exe beside the game executable. Those are local workarounds in that thread. The error alone supplies no diagnosis of a Mojang outage.
For #26, the supplied batch file selects WGPU_BACKEND=vulkan, sets VK_LOADER_DRIVERS_DISABLE=amd and sets DISABLE_VULKAN_OBS_CAPTURE=1. Its author explicitly says the fix was specific to having two GPUs. Treat it as a hardware-specific lead for the same rendering symptom. Disabling an AMD driver selection path on an unrelated system would be a poor first troubleshooting step.
v0.4.0 changes how to read older bug reports
The v0.4.0 release notes claim fixes for inventory icons and a stuck skate state, while still listing an invisible skateboard on some maps.
In issue #31, the reporter identifies v0.3.2 and describes missing item icons despite working world textures, held items, dropped items and stack counts. The v0.4.0 notes say inventory item icons show again. That is the wording in the release notes. Describe that as an upstream fix claim for the earlier symptom, rather than telling every new player that icons are broken.
The same release says skating no longer gets stuck after a skate error and Minecraft block edges now act as grind rails. That makes the video summary's older restriction on grinding Minecraft edges a version-sensitive observation. The release also claims weapon reload and aim-timing fixes. None of those notes specifies that switching away from a PS5 Edge controller is obsolete.
Controller reports need their own small matrix because opposite failures appear in separate threads:
| Evidence | Scope | Reported outcome |
|---|---|---|
| Issue #8 | Earlier Gamesir T7 and Xbox One report | Skating input worked while other controls did not. The reporter marked it fixed in v0.3.0. |
| Issue #29 | PS5 Edge in skate mode | Changing to Xbox restored pushing and tricks for pubert69. |
| v0.4.0 release | A stuck state after a skate error | Upstream says that state is fixed. |
Record the release, controller model and exact failing action when asking for help. A statement that a controller works in menus answers a different question from whether its skating inputs work.
Choose the 2009 MW2 data before spending money
IW4L's README explicitly identifies Call of Duty: Modern Warfare 2 (2009), and the mashup asks for your own MW2 installation.
The distinction has already cost someone money. In issue #25, the author asks the README to distinguish Steam app 10180, Modern Warfare 2 (2009), from app 3595230, Modern Warfare II. Commenter rubixus reports buying the wrong one. The supplied thread remains open and contains no recorded documentation resolution.
Use the full 2009 title when checking what you own. The mashup README says only the Steam version has been tested, and the IW4L README specifies installed MW2 Multiplayer data. Seeing the letters MW2 on a store page isn't enough.
Skate 3 is optional, but enabling skating requires the Xbox 360 game's extracted default.xex, its data folder and a controller. Minecraft need not be installed: the README says its files download from Mojang on first launch. That separates the preparation into an existing MW2 installation, optional skating assets and a first-run Minecraft download.
A writable folder and curl matter more than an account setup
The documented player route is to extract the release into a writable folder, run iw4l.exe and select the game files.
The README specifically excludes Program Files and gives several routes into the Minecraft world: the menu's Minecraft tab, Minecraft World.bat, or the map minecraft:overworld console command. The first Minecraft launch needs internet access and curl. Later offline play is a documented behavior, not a result from our sandbox.
For source developers, BUILD.md lists Rust through rustup, a C toolchain and Bevy system libraries. Its Linux instructions include Wayland and udev headers because those features are enabled. Use those platform instructions rather than interpreting our successful sandbox build as proof that a stock desktop has every prerequisite.
Keep the source-code license separate from the game data. The README says original game assets belong to their owners and that you need your own copies. For a private experiment, obtain the release from the project and point it at your own files. If you intend to distribute a ready-to-play bundle, the source license alone is insufficient evidence that you can include its game assets.
Attention shows interest, not a support commitment
Trendshift records 890 stars gained and two merged pull requests over its September 27 to November 13 window, which describes repository attention rather than successful play sessions.
The Trendshift record cannot tell you how many people launched a map, kept playing or returned after an update. The controller and asset-download threads are more useful for that decision because their authors describe a task, a failure and what changed.
The public GitHub metadata retrieved on November 13 lists the last push as October 2, 2026. Together with the issue discussions and v0.4.0 notes, that gives a dated picture of released work and user troubleshooting. It isn't enough to infer either abandonment or a promised support cadence. Choose this project because you want to explore this particular crossover, with time set aside for the errors above.
2010-rust-rewrite-mashup vs IW4L and skate3clone
Choose IW4L for an MW2 runtime experiment or skate3clone for skating reconstruction work; choose the mashup when the interaction between games is the attraction.
These are related projects with narrower purposes, so the comparison is about scope. There is no measured speed or reliability winner here.
| Project | Documented purpose | Pick it when |
|---|---|---|
| 2010-rust-rewrite-mashup | MW2, Skate 3 mode and a Minecraft world together | You want to try cross-game interactions. |
| vladtrc/iw4L | An open-source runtime loading owned MW2 (2009) assets | You want to inspect or change MW2 movement and combat without choosing a crossover for that work. |
| chasmlol/skate3clone | A source-only Rust/Bevy reconstruction of Skate 3 systems | You want to study skating and its owned-game asset workflow. |
IW4L's README calls gameplay incomplete and warns that APIs, caches, configuration and networking can change between commits. Moving upstream doesn't buy a finished replacement game. Skate3clone likewise calls itself an early work in progress and requires assets from a legally owned Xbox 360 copy. These alternatives narrow what you're investigating, rather than removing the experimental nature of the work.
What the other reviews get wrong
A r/skate3 comment that the crossover's controls all work overstates the evidence, because issue #29 documents a controller-specific failure.
SourceDiligent6492's comment is an understandable reaction to crossover footage. Pubert69's report is a better guide to buying hardware or planning a session: map movement, mode switching and skating actions can behave differently. Keep that distinction even when a release advertises controller improvements.
The Chasm repost also explicitly labels parity as the author's report. Turning it into an independent benchmark would change what the source says. Similarly, Mudahar's gameplay reaches us through a third-party summary, which is useful for identifying observed interactions but weaker than a versioned reproduction. Our recommendation rests on a completed source build and attributed gameplay evidence, with those sources kept distinct.
Questions people ask
You need owned game data for the documented setup, and the runtime underneath the crossover is IW4L.
Do I need to own any of the original games to play 2010-rust-rewrite-mashup?
The README requires your own MW2 copy. Skate 3's Xbox 360 files are optional and enable skating. Minecraft does not need to be installed because its files download on first launch. The README's credits also state that you need your own copies of the original games.
Does it require Modern Warfare 2 from 2009 or Modern Warfare II?
Use Modern Warfare 2 (2009). IW4L names that game explicitly. Issue #25 documents confusion between its Steam listing and Modern Warfare II, including a wrong purchase.
Which game or runtime does this mashup run in?
It runs on IW4L, the Rust MW2 runtime. The mashup's README describes Skate 3 mode and a Minecraft world inside that runtime.
How can I fix the pc_options_video launch error?
The supplied issue #10 thread has no reproducible fix. Issue #17 links an upstream pull request but contains no confirmation that a particular release resolves the error. Save the launch log and identify your release when following those threads.
Is there a local fix for the failed Mojang download, or is it a Mojang server problem?
Issue #23 contains local workaround reports: move the installation to C:/ or place curl.exe beside iw4l.exe. Its curl exit code 3 supplies no evidence of a Mojang server outage.
Does the project combine reusable Bevy plugins, or does it merge the games' code directly?
The evidence identifies the combined runtime and components, without resolving a reusable plugin interface. In the supplied r/bevy discussion, J8w34qgo3 specifically reports difficulty finding the app builder. A developer adopting code should inspect the integration boundaries before treating this as a plugin-composition example.
Can I stream the mashup to my audience?
The supplied Reddit thread asks about streaming but provides no permission answer. The README explains game-file requirements, not streaming rights. Check the relevant game and platform policies before arranging a public broadcast.
What we have not tested yet
We have not tested playable graphics, controller compatibility, crafting, multiplayer or sustained frame pacing in our own session; our evidence covers a source run and a blocked deployment attempt.
We did not reproduce the v0.4.0 fix claims, the hardware-specific rendering batch file or the Proton Experimental report. The v0.3.2 inventory issue and earlier controller reports remain versioned observations. A clean first launch and a return visit after caching Minecraft assets would be useful separate checks.
The supplied logs do not establish the actual toolchain or operating-system version. Our Compose safety failure also prevents a gameplay assessment from the hands-on path. Its contradictory generic deployment summary needs correction in the lab record before it can support any deployment claim.
We have no comparative gameplay benchmark, security audit, measured adoption count or support-response study. Documentation is the only dimension we rate here: 3/5 means the README provides an actionable setup and controls guide, while issue #25 exposes a consequential edition ambiguity. Setup ease, community support and gameplay maturity receive N/A because the completed evidence doesn't assess those experiences sufficiently.
Before buying anything for this experiment, check the 2009 MW2 listing against the files you already own. Before planning a session around skating, confirm that your controller can push and perform a trick.


