Magnificent Minimap for Bedrock: Dependencies, Mobile Controls, and Realm Checklist

Quick answer: Magnificent Minimap currently requires three creator-linked projects: the minimap itself, UI Queue and Kamii's Script Configuration. The creator also says the Beta API experiment must be enabled. Import and activate the matching packs only in a backed-up test copy, verify that all three are active, open the world, then test the documented mobile or PC control before changing map settings. Do not promise console or Realm support: the creator says console is not available yet, and the current page does not establish Realm behavior.

MineBrush checked the creator-owned CurseForge pages on August 25, 2026. No creator file, screenshot or media was downloaded, and Bedrock was not launched. The steps below are a source-first safety route. Exact pack composition, import order, device performance, controller behavior, world persistence and Realm compatibility remain unknown until tested with the exact current files.

Current creator-owned source tuple

The Magnificent Minimap project is owned by qduoubp, identifies the project as MIT-licensed and currently shows Magnificent Minimap Resource v1.7 as the main release, dated July 10, 2026. The page displays game labels 26.0, 1.21.130, 1.21.120 and 1.21.100.

The same page names two required companions:

• UI Queue, also by qduoubp, currently showing v1.6 dated March 19, 2026 with a 26.3 project label;
• Kamii's Script Configuration, also by qduoubp, currently showing v1.3 dated August 6, 2025 with a 1.21.90 project label and All Rights Reserved status.

Those labels are evidence, not a compatibility proof. CurseForge project labels can span multiple builds, and the minimap's main-file name alone does not tell MineBrush whether every behavior/resource component is bundled or separately linked. Use each creator-owned Relations/file page immediately before import. Never substitute a similarly named mirror.

What the creator says it does

The project description lists a rotating minimap, multiple rendering styles, customization, entity indicators, compass orientation, circular and rectangular views, a map atlas and a Nether minimap. It documents /configuration for the configuration menu and says that command is available only with Kamii's Script Configuration.

The page also labels the add-on “very experimental,” warns that it may consume substantial RAM and make a world temporarily unplayable until reopened, and says it has not been tested on low-end devices. That warning belongs at the center of the install plan—not buried after the fun feature list.

Make a reversible test world

1. Update your backup of the real world and confirm you can restore it.
2. Create a separate local test copy. Do not start on the only Realm or survival copy.
3. Record your Bedrock build, device, input method and the exact three creator project URLs.
4. From each creator-owned page, choose only a file whose displayed game label fits your build. If the relation is unclear, stop.
5. Import the packages, then verify them in the world's Resource Packs and Behavior Packs screens. Do not assume a successful import means activation.
6. Enable the Beta API experiment only on the disposable copy, because the creator states it is required.
7. Open the test world and wait before touching settings. Confirm that the HUD loads and the world remains responsive.

MineBrush cannot establish the exact import order from the current public text. If the creator supplies an order in the actual file description or relations screen, follow that source. Otherwise add one dependency at a time, close the world between changes and record the result.

Test the documented controls

For touch, test three real moments: walking, opening inventory and entering/exiting sneak. A button can work in an empty field and still collide with a device HUD during normal play. Record screen size and UI scale with the result; “works on mobile” is too broad.

Dependency-first troubleshooting

If the minimap does not appear, do not immediately re-import the same file. Walk the chain:

1. Confirm the test world has the minimap project and both named dependencies active, not merely installed globally.
2. Confirm Beta API is enabled on that test copy.
3. Confirm the Bedrock build matches the file labels shown on each current creator page.
4. Close and reopen the world once, because the creator specifically describes reopening as the response to an unplayable high-memory state.
5. Try the documented control for your input method.
6. Use /configuration only after Kamii's Script Configuration is active.
7. If one step remains ambiguous, preserve the world copy and ask on the creator page with the exact tuple.

A missing overlay, missing configuration command and frozen world are different symptoms. Keep them separate. The first points toward activation or UI rendering; the second toward the configuration dependency; the third belongs to the creator's experimental/performance warning.

Realm checklist: prove local before remote

The current project text does not promise Realm support, upload persistence, multiplayer synchronization or behavior after a Realm update. Treat all of those as unknown. If you have authority to manage the Realm and accept the experiment risk, use this gate:

• local disposable copy opens repeatedly;
• all three project entries remain active after a restart;
• the minimap control works on every input class you intend to support;
• memory behavior is acceptable during a longer local session;
• you have a fresh downloadable Realm backup;
• players know the add-on is experimental and console is not currently documented as available;
• you are prepared to remove the add-on and restore the backup if upload or join behavior fails.

Passing that checklist still does not prove Realm compatibility. It only makes a controlled test less reckless. If you cannot create and restore a backup, stop before the Realm step.

What the MineBrush fixture proves

The included dependency matrix is a static decision aid. Its validator requires the three named projects, Beta API, a world-copy checkpoint, an input-specific control and an explicit Realm-unknown stop. It rejects a missing dependency, a console-supported claim, a low-end-safe claim, an unqualified Realm-ready claim and a creator-file mirror. It does not open a .mcpack, inspect a manifest or run Bedrock.

Rights and download safety

This article links only to creator-owned CurseForge project pages. MineBrush does not mirror the minimap, dependencies, screenshots or gallery media. The editorial cover is an original AI-generated MineBrush illustration and is not gameplay proof. The minimap project displays MIT, UI Queue's current project page provides its own project information, and Kamii's Script Configuration displays All Rights Reserved. Always follow the license and distribution terms attached to the exact file you select.

Stop conditions

• Stop if any one of the three creator project links is missing or replaced by a mirror.
• Stop if the exact file/build relation is unclear.
• Stop before enabling experiments in the only copy of a world.
• Stop if the world becomes unstable, memory pressure rises or the device repeatedly closes the world.
• Stop before claiming console support; the creator currently says it is unavailable.
• Stop before a Realm attempt without a tested local copy and current backup.

For more creator-resource safety checks, visit Minecraft guides. Browse the wider ecosystem through Minecraft Bedrock add-ons. Keep creator files on their verified project routes rather than relying on third-party mirrors.

Bottom line

Magnificent Minimap is a three-project, experiment-enabled setup with an explicit creator warning. Verify the current minimap, UI Queue and Kamii configuration pages; test on a backed-up local copy; use the input-specific control; and treat console, low-end devices and Realms as unproven. That route takes longer than “tap install,” but it gives you a rollback path when an experimental HUD add-on gets spicy.