Understand the mod.
Build what’s possible.
A careful porting workflow, with AI on your own device.
Inspect first. Review every feature. Approve before building.
Same idea.
A new implementation.
Tell us what you’re porting.
Your files stay on this device. Java code is never executed.
Archive evidence & inspection limits
Full file inventory
The local model can be wrong. It has no live web access; uncertain APIs and versions must be verified.
Your plan comes first.
Upload a mod or describe its behavior.
Your feature-by-feature verdict will appear here.
A/B/C are proposed classifications, not compatibility guarantees. “?” means evidence or API verification is missing. Percentages count listed features, not fidelity or completion.
| Build | Feature | Category | How in Bedrock | Difference / reason |
|---|
Should I build it according to this plan?
Build an add-on draft.
New code only. Uploaded code and assets are used as evidence and are never packaged into your export.
Analyze a mod and approve a plan to unlock building.
Generated files — inspect before importing
Syntax, SDK type and packaging checks are not game tests. Generated behavior and API compatibility remain unverified.
From download to your world.
- Download & import. After a build, download the .mcaddon. On Android, open it with your target Minecraft app from Files. On iPhone/iPad, use Files → Share → Minecraft (or Minecraft Education) if available. Import handling varies by device and edition.
- Activate both packs. Make a backup or a test world. Open its settings → Behavior Packs → My Packs, and activate the new pack. Activate its Resource Pack too, if the build includes one.
- Check versions & experiments. Use the exact game and Script API versions you verified. Enable cheats and operator permissions to test /scriptevent. Stable APIs generally don’t require Beta APIs; enable experiments only when the generated guide explicitly requires them. !help is version-sensitive.
- Test a command. Run
/scriptevent blockbridge:help help. Try!helponly if optional chat support was enabled and supported. Feature-specific tests appear after building. - Troubleshoot. Version mismatch: check the dependency and minimum engine version. Missing pack: confirm import completed and activate it in the world. Script failure: enable the Minecraft Content Log and inspect errors. Missing textures: follow the asset list. Test one pack at a time for conflicts.
- Know the exclusions. Category C and unresolved features are not included. Education requires separate verification. Consoles usually need a supported transfer route; a direct local file import may be unavailable.
Keep the idea. Change the route.
A custom Java renderer, engine modification or Java-only dependency cannot simply run inside a Bedrock add-on. A smaller gameplay recreation may be the closest option.
Geyser is not a universal mod bridge. Mods that require a Java client are not automatically usable by Bedrock players. Evaluate server-only behavior and supported integrations individually.