What RedRock claimed to be
A fan-made Quest app that would host actual Minecraft Bedrock you already owned: play it inside our window, load native mods, add stereo VR later. Sideloaded. Unofficial. Not a clone, not a cracked APK, not Microsoft.
That sentence already contains the contradiction. The rest of this page is what happened when we treated it as a product anyway.
1. The host was impossible
The original design was mcpelauncher-on-device: extract
libminecraftpe.so, dlopen it inside RedRock,
spoof package identity, stub Google Play PairIP, draw the game in our
GLES window.
Bedrock 1.26 wraps the real game in PairIP. We reproduced both failure modes on a Quest 3S (1.26.45.1):
-
Stub
libpairipcore.so/libmaesdk.so— the game’s own code never decrypts. SIGSEGV inMinecraftGame::init. -
Keep PairIP and re-sign the APK — PairIP’s native signature check
sees a foreign cert. SIGSEGV in
libpairipcore.sobefore assets load.
Identity spoofing did not save it. About twenty crash gates (opPackageName, resource IDs, asset manager, permissions, bootstrap remapping) existed only because the process was lying about being Minecraft. That list does not end.
Do not try to run Minecraft Bedrock inside another Android app. PairIP is not a bug. It is the product.
2. Installing the real app kills the product
The only way the game booted was to stop hosting. Fetch Play splits,
hand them to PackageInstaller unmodified, launch
com.mojang.minecraftpe as itself. Real uid, real
signature, PairIP satisfied. Cold start about 1.5s.
That is not a host. That is a sideloaded downloader that installs Minecraft as a second Quest app — which is what the official Store path already does, without Developer Mode, without an unofficial Play client, and without us.
If your “Minecraft on Quest” project has to PackageInstaller the real APK, you do not have a product. You have a worse installer for someone else’s app.
3. Mods and VR died with the host
Native mods need code inside Bedrock’s process. Stereo OpenXR / two-eye Minecraft needs the same. Retargeting the game framebuffer onto a VR panel from another process needs root. PairIP blocks the first two. We still wrote “ongoing VR mod” on the website.
Do not advertise stereo VR or in-process Bedrock mods on Quest until you can run inside the game. We could not. You will not by stubbing PairIP.
4. Unofficial Google Play fetch is a ToS trap
Play has no consumer “save this APK to disk” API. We used the same
class of client as mcpelauncher: sign in on Google’s EmbeddedSetup
page, take an oauth cookie, ask Play for arm64-v8a
delivery, keep files for personal use.
That can violate Google’s Terms of Service. Google can terminate the account. “Use a disposable Google account” is a warning, not a business plan. Play Console is only for apps you publish. It is the wrong tool for Minecraft.
If Play refuses (not owned, paid/DRM, region), that is the end. There is no honest bypass. Mirrors are redistribution.
Do not build a product on unofficial Play protocol. Do not scrape APKs. Do not share Play artifacts. Do not put someone else’s Google account on a headset.
5. We published as if it were shippable
We stood up a Next.js marketing site. FAQ schema, llms.txt,
Open Graph, a “Minecraft on Quest” landing page aimed at search and
answer engines. We put a Quest APK on a public catalog as “version 1”.
Then we hid the site with 404s and noindex when it was obvious the
core claim was dead.
SEO for unofficial Minecraft has no honest win:
- Rank for “minecraft on my oculus” and you look like Microsoft’s product.
- Stamp “not Minecraft” on every page and you look like a fake spin-off.
- Stamp “actual Minecraft, unofficial host” and you are still not the Store app, still on PairIP, still on ToS ice.
Next.js was the wrong surface. A search-optimized React app for a sideload tool that could not host the game. The site outran the software by months.
Do not index an unofficial client of someone else’s game. Do not put APKs on the public internet next to the word Minecraft. If the host does not work, do not ship a storefront.
6. “Unofficial” is not a license
Microsoft, Mojang, Xbox, Google, and Meta did not endorse, ship, or approve RedRock. Minecraft®, Google Play™, Meta Quest®, Horizon OS are their marks. BSD covers our source only. The name RedRock was never a grant to impersonate the official project, and it was never a grant to impersonate Minecraft.
Developer Mode and Unknown Sources are your problem with Meta, not a distribution channel. A 2D Horizon window is not VR. Two Android tasks (library vs immersive) do not become one game.
Fan-made does not mean allowed. If you need a lawyer to explain the homepage, do not ship the homepage.
7. Quest is not a PC launcher with a headset glued on
Desktop Bedrock launchers and Java + Fabric exist in a different world (still unofficial in places, still not ours to bless). Quest is signed Horizon OS, arm64 only, Store vs Unknown Sources, no cross-process EGL, no “just inject a .so”. An x86 extract from a Mac will not load. Treating Quest like mcpelauncher-on-Linux was the original architectural error.
If you want Minecraft on Quest, buy and install the official app. If you want mods, use platforms where that work actually exists. Do not assume Meta Quest can run a PC Bedrock stack.
What to do instead
- Play Minecraft on Quest from minecraft.net / the Meta Store.
- Get Minecraft from Microsoft or Google Play if that is how you already own it.
- Do not sideload a third-party “Minecraft host” for Quest.
- Do not redistribute Minecraft APKs or OBB files.
-
Do not stub PairIP, re-sign Bedrock, or dlopen
libminecraftpe.soon a headset. - Do not run SEO, AEO, or “llms.txt” campaigns for unofficial clients of a trademarked game.
Status
Discontinued. No downloads. No catalog. No support. Source that remains public is not a recommendation to use it. It is provided as is. We are not responsible for bans, broken headsets, or lost accounts.
Official Minecraft: minecraft.net · Meta Quest help: meta.com/help/quest · Saltmine: saltmine.me