Reorder DecentHolograms lines without changing their contents

Applies to: DecentHolograms; match the linked maintainer documentation to your installed platform and release.
Documentation checked 9 November 2026.

Changing the order of a display can disturb a line’s formatting or conditions when an administrator rebuilds it by copying text. Preserve the existing content and test the installed line operations instead.

Prepare the test

Record the hologram name, world and location before editing. Match the command family to the installed release because newer display commands and older hologram commands can differ.

Make the change

Record each line in its current order and note any line-specific permission, spacing or alignment. Use a numbered local list so a later screenshot does not leave the original order ambiguous.
Clone the display into a private test location and check the supported swap or line-edit commands for its command family. Do not assume that a command for a newer display object accepts an older hologram.
Move only the two intended lines and inspect the result with an ordinary viewer. Check whether formatting and permissions remain attached to the intended text after the operation.
Repeat from another viewing angle and test any dynamic value on the moved lines. Apply the verified change to the public object only after the copied display preserves its complete meaning.

Check the result

The display should present the intended reading order without changing text, visibility or update behaviour. Compare the numbered record with the final state and keep the original order in the maintenance note.

If the test fails

Reverse the swap using the saved order if a line setting moved unexpectedly. Restore the saved display configuration when needed, preserving its identity rather than deleting the original and rebuilding all lines by hand.

Line numbering can differ between command families and releases. Confirm the help output on a harmless copy before editing the public sign.

References and related help

Check the official DecentHolograms documentation against your installed release before using a command or setting from another version.

Give a LuckPerms permission an expiry without leaving permanent access

Make a LuckPerms event rank expire while preserving other ranks

Limit a LuckPerms command permission to one Minecraft world

Keep a LuckPerms permission local to one network backend

Move a player along a LuckPerms track without replacing unrelated groups

Fix a LuckPerms prefix priority without changing chat formatting

Remove a direct LuckPerms exception without weakening its parent rank

Apply a small LuckPerms web-editor session to the correct server

Export LuckPerms data before changing its storage configuration

Find an inheritance cycle before it complicates a rank change

Keep default-player permissions separate from staff inheritance

Diagnose LuckPerms edits that reach one backend but not another

Check a player UUID before changing LuckPerms account data

Remove a staff member from one LuckPerms track without clearing their account

Give an EssentialsX rank a fixed home limit

Restrict one EssentialsX warp to an approved player group

Test EssentialsX teleport delay and movement cancellation

Add an EssentialsX cooldown to one utility command

Resolve an EssentialsX command alias conflict without removing either plugin

Check EssentialsX AFK kick exemptions for a staff role

Limit EssentialsX nickname changes without granting formatting control

Give staff a read-only EssentialsX player-information role

Recover from an accidental EssentialsX ignore setting

Restrict EssentialsX repair commands to the intended tool policy

Review EssentialsX command-disabled entries after a plugin change

Test an EssentialsX jail location without trapping a real player

Change the EssentialsX starting balance for new players only

Set EssentialsX maximum and minimum money limits with a boundary test

Change the EssentialsX currency symbol without changing stored money

Test an EssentialsX pay dispute using two controlled accounts

Review EssentialsX worth prices before enabling item selling

Explain an EssentialsX balance leaderboard that looks out of date

Trace an unexpected EssentialsX command charge

Back up EssentialsX money before a player-data migration

Verify a LiteBans temporary ban expires at the intended time

Test whether a LiteBans mute covers a private-message command

Build a LiteBans appeal-review role without punishment access

Check a LiteBans moderator’s maximum punishment duration

Find which plugin handled a ban command on a mixed-plugin server

Verify the server scope of a LiteBans network punishment

Investigate a LiteBans database connection failure without losing history

Reverse one appealed LiteBans punishment while preserving the audit trail

Test an AdvancedBan time layout before staff use it

Check AdvancedBan warnings without accidentally escalating a real player

Give an AdvancedBan helper access to history without ban powers

Check AdvancedBan storage before changing from local files to MySQL

Lift one AdvancedBan restriction after an approved appeal

Locate AdvancedBan correctly on a proxy network

Test SuperVanish visibility with separate staff and player accounts

Check whether a vanished SuperVanish moderator can pick up items

Verify flight is safe when a SuperVanish moderator reappears

Check silent chest inspection without changing container contents

Find a SuperVanish join or player-list information leak

Remove vanish access from a staff role without leaving a hidden account

Check PremiumVanish layered visibility after changing staff ranks

Verify PremiumVanish network vanish across Velocity backends

Check vanished staff interactions before a live investigation

Recognize the PremiumVanish API jar before installing an integration

Give GrimAC alerts to one observer without granting exemptions

Remove a GrimAC exemption and verify when checks resume

Collect a GrimAC prediction log for a false-positive report