mojira.dev
REALMS-14549

Addon Inaffiality after Realm Restart

Summary: Marketplace Add-ons and Shaders become invisible/non-functional for all players after automatic daily Realm reboot due to asynchronous DRM/License validation timeout.

Description:

As a server administrator with 15+ years of hosting experience, I am reporting a critical, persistent backend issue affecting Minecraft Bedrock Realms.

Purchased Marketplace content (Add-ons and Shaders bought with Minecoins) regularly breaks and becomes completely invisible or non-functional for all active players on the Realm.

Technical Analysis & Behavior:

  1. Initial Setup: Add-ons and shaders are applied to the Realm. Everything initializes correctly. Content is visible and usable. Client and server logs indicate no errors (OK status).

  2. The Trigger: The automated daily scheduled server/instance reboot performed by the Microsoft Azure Cloud infrastructure.

  3. The Root Cause (Asynchronous Race Condition): During the automated reboot, the dedicated Realm instance boots up faster than the Xbox Live / Marketplace DRM API can validate the licenses for the owner's purchased contents.

  4. The Result: Because the DRM validation times out or responds asynchronously after the world file has already initialized its dependencies, the server suppresses the assets. The mod structures technically exist in the backend (hence no crash logs), but the textures, models, and scripts are stripped/rendered invisible to the clients.

  5. Irrelevance of Client-Side Fixes: Since this issue occurs globally for all connecting clients simultaneously after the server reboot, standard troubleshooting (clearing local cache, reinstalling the app) has 0% success rate. The corruption is strictly located within the cloud-managed runtime configuration of the Realm instance.

Steps to Reproduce:

  1. Purchase any official Add-on/Shader bundle via the Marketplace.

  2. Activate the content on a Bedrock Realm.

  3. Verify that the content works initially.

  4. Wait for the automated daily Realm instance reboot (or force a session reset by leaving the Realm empty for an extended period).

  5. Log back into the Realm.

  6. Observed Result: The Add-on features/blocks/textures are invisible or completely non-functional for all users. System logs still falsely report flawless execution.

  7. Expected Result: The Realm instance must implement a synchronous retry-logic or extended timeout for DRM license validation during boot-up before loading the world dependencies, ensuring that purchased content remains authenticated across server Restarts.

Environment:

  • Server Platform: Managed Bedrock Realms (Microsoft Azure Cloud)

  • Client Specs (Host): High-End Windows PC (8-Core CPU 4.7 GHz, 40 GB RAM, Dedicated GPU), 200 Mbps stable fiber connection.


Comments 0

No comments.

Fox

(Unassigned)

Unconfirmed

Bedrock

Retrieved