Skip to content

Compatibility and Troubleshooting

Jump to bottom
Charles Gantt edited this page Sep 11, 2026 · 2 revisions

Compatibility and Troubleshooting

Supported design target

  • Minecraft Bedrock 26.30 or newer
  • Stable Script APIs
  • Cheats off
  • Experiments off
  • Both included packs active
  • Standard graphics and Vibrant Visuals/PBR resource declarations
  • Single-player, multiplayer, Realm, and Bedrock Dedicated Server workflows

The add-on declares itself as add-on content and is designed to preserve achievement eligibility. If a particular retail version, device, Realm, or server build behaves differently, include that exact environment in a report.

Intentional coverage limits

This is selective protection rather than a hostile-server claim system. The current event coverage does not comprehensively stop:

  • Pistons moving blocks across a boundary
  • Hoppers transferring items across a boundary
  • Water, lava, or fire spreading into an area
  • A block breaking because an unprotected supporting block was destroyed
  • Enderman block movement
  • Wither dash or contact destruction outside reported explosion events
  • Commands, world editors, or other add-ons directly changing blocks
  • Every unusual multi-block or replaceable-block placement
  • Every custom item placement path
  • Projectile or unattributed player/entity damage paths that Bedrock does not report as direct player damage

Explosion block protection filters matching blocks out of the impacted list. The explosion itself still occurs. Critical-only filtering may leave a protected machine exposed when an unprotected supporting block is destroyed.

Menu does not open

  • For direct access, crouch and interact with the physical rune.
  • For a control stick, verify the exact case-sensitive name: PlayerGriefControl or AdminGriefControl.
  • Use or interact with a block/entity while holding the stick.
  • AdminGriefControl requires actual operator status.
  • Manager access applies only to runes where that player has the Manager role.

Rune does not appear or has missing textures

  • Confirm the Behavior Pack and Resource Pack are both active and the same version.
  • Remove obsolete duplicate pack versions from the device, then reimport the current MCADDON.
  • Inspect the Content Log for block, geometry, texture, or script errors.
  • Test in a copied world with only this add-on active to identify pack conflicts.

Protection is active outside a rune

Check Explosion scope:

  • Global protects according to dimension settings everywhere.
  • Hybrid combines global dimension rules with runes.
  • Ward limits explosion rules to enabled rune volumes.

Player restrictions remain local regardless of explosion scope.

Protection does not cover the expected height

The vertical range is fixed at 20 blocks below and 20 above the rune. The menu shows the exact minimum and maximum Y. Use additional runes at other heights for tall buildings, underground rooms, or deep mines.

Radius will not increase

Check:

  • The rune's tier cap
  • The administrator's Maximum radius
  • The administrator's Maximum rune tier
  • Different-owner overlap
  • Minimum rune distance
  • Whether upgrades are enabled

Grid is incomplete or absent

  • Enable the world Grid switch.
  • Enable Persistent Illuminated Grid, or use the 30-second preview.
  • For preview, enable Personal grid preview in PlayerGriefControl.
  • Move closer to distant edges. The visual system uses loaded nearby tiles and a helper limit.

Grid visibility never determines protection.

Explosion behavior is unexpected

Review controls from broadest to narrowest:

  1. Add-on enabled
  2. Explosion scope
  3. World source master switch
  4. Dimension enabled, source, and block mode
  5. Rune enabled, source, and block mode
  6. Separate entity-damage switch

Unknown covers unattributed explosions, including beds and respawn anchors when the engine does not identify their source. Other add-ons may independently cancel the same event; the strictest outcome may win.

Stale rune record

If a command, editor, or another add-on removed the physical rune, its stored record may remain. An operator can find it under Manage All Runes or with andys_sgp:admin runes, inspect it, and remove the registration. Console removal does not delete blocks.

Report a problem

Include:

  • Exact Minecraft Bedrock version
  • Add-on version
  • Platform and graphics mode
  • Single-player, Realm, or BDS
  • Active pack list and order
  • Relevant world, dimension, rune, and player settings
  • Exact steps and expected/actual result
  • Content Log or server-console lines

Use the support links at AndyTheMakerMC. Remove private player or server information before posting publicly.

Clone this wiki locally