Diagnose a MiniPlaceholders tag that breaks only for one rank
A tag can fail for one rank while remaining correct for staff. Compare the provider’s data and the destination’s access checks before changing rank inheritance or granting broad permissions.
Prepare the test
Choose the correct execution platform before testing a tag. A proxy and a backend can have different expansions, audiences and permissions even when the same player appears on both.
Make the change
- Pick two ordinary test accounts with different intended ranks. Copy the exact tag and record whether each account can use the destination feature independently of the tag’s output.
- Parse the tag with each named audience through the installed platform’s documented command. Compare the result with the data provider’s own rank or metadata value for the same account.
- Check the destination plugin’s permission requirements separately. A denied menu opening and an unresolved text value are different failures, even when the player reports them together.
- Apply the smallest documented permission or metadata correction to the test rank. Repeat the named-audience parse and actual destination test without operator status or a wildcard permission.
Check the result
Both accounts should receive the values and access their roles permit. Confirm that the restricted account still cannot use administrative features after the display starts working.
If the test fails
Remove the temporary test permission if it did not address the failing layer. Restore the previous metadata value if the correction affected another feature, and preserve the comparison results for support.
An administrator preview can bypass destination restrictions. Keep ordinary-player evidence in the final test notes rather than relying on a staff screenshot.
References and related help
Check the official MiniPlaceholders documentation against your installed release before using a command or setting from another version.