feat: support MiniMessage and hex colours in phase text

[tastybento]

The report

An admin coloured a phase hologram with <green><bold>Начало (Равнина)</bold></green> and got white text with the tags rendered literally.

Why

Holograms deserialized with LegacyComponentSerializer.legacyAmpersand(), which understands the 16 legacy & codes and nothing else. Adventure builds that instance with hexColours = false, so even &#RRGGBB did not work there.

The action bar used a second, separately configured serializer that did support hex but not MiniMessage. Two display paths, two different answers to "what formatting can I use here", and neither documented where anyone would look.

Display	Before	After
Hologram	& only	&, §, hex, MiniMessage
Action bar	& + hex	&, §, hex, MiniMessage
Boss bar title	unchanged — String API, BentoBox already resolves it	unchanged

The fix

Both Component paths now use Util.parseMiniMessageOrLegacy, which accepts MiniMessage, & and § codes, hex, and any mixture — and is cached on the BentoBox side, so the per-block hologram and action bar rebuilds do not re-parse the same strings.

This also fixes § codes being rendered as literal text. Translations come back from User.getTranslation already converted to § codes, so anything locale-sourced was being handed to a serializer bound to &. That affected the starting hologram (aoneblock.island.starting-hologram) and the action bar. Phase file hologram lines never see the translation layer, which is why the reported case showed raw MiniMessage tags rather than raw § codes.

I flagged this § behaviour as suspected when I first read the code — it is now confirmed by tests that fail against the old serializer.

Compatibility

• Existing configs are unaffected.& codes keep working and are covered by tests.
• BentoBox's MiniMessage instance is the non-strict MiniMessage.miniMessage(), so a hologram containing stray angle brackets (<-- break this) is left as literal text rather than throwing.
• Util.parseMiniMessageOrLegacy is BentoBox 3.2.0 API — no dependency bump needed. This branch is based on develop and is independent of fix: do not lose island progress when the server restarts #550.

Docs

Updated the holograms: block in 0_plains.yml — the reference phase file, and where the admin was already looking — to show all three syntaxes plus a gradient example.

Tests

565 passing. New coverage on both paths for MiniMessage, gradients, & codes, § codes and hex, asserting on the serialized formatting rather than the component tree shape.

Not boot-tested on a live server — the behaviour is exercised through the real Util code path in tests, but I have not watched a hologram render in-game.

🤖 Generated with Claude Code

https://claude.ai/code/session_014t1DSo2wMbTWZLcwXpwUmQ

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
100.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[tastybento]

The report

An admin coloured a phase hologram with <green><bold>Начало (Равнина)</bold></green> and got white text with the tags rendered literally.

Why

Holograms deserialized with LegacyComponentSerializer.legacyAmpersand(), which understands the 16 legacy & codes and nothing else. Adventure builds that instance with hexColours = false, so even &#RRGGBB did not work there.

The action bar used a second, separately configured serializer that did support hex but not MiniMessage. Two display paths, two different answers to "what formatting can I use here", and neither documented where anyone would look.

Display	Before	After
Hologram	& only	&, §, hex, MiniMessage
Action bar	& + hex	&, §, hex, MiniMessage
Boss bar title	unchanged — String API, BentoBox already resolves it	unchanged

The fix

Both Component paths now use Util.parseMiniMessageOrLegacy, which accepts MiniMessage, & and § codes, hex, and any mixture — and is cached on the BentoBox side, so the per-block hologram and action bar rebuilds do not re-parse the same strings.

This also fixes § codes being rendered as literal text. Translations come back from User.getTranslation already converted to § codes, so anything locale-sourced was being handed to a serializer bound to &. That affected the starting hologram (aoneblock.island.starting-hologram) and the action bar. Phase file hologram lines never see the translation layer, which is why the reported case showed raw MiniMessage tags rather than raw § codes.

I flagged this § behaviour as suspected when I first read the code — it is now confirmed by tests that fail against the old serializer.

Compatibility

• Existing configs are unaffected.& codes keep working and are covered by tests.
• BentoBox's MiniMessage instance is the non-strict MiniMessage.miniMessage(), so a hologram containing stray angle brackets (<-- break this) is left as literal text rather than throwing.
• Util.parseMiniMessageOrLegacy is BentoBox 3.2.0 API — no dependency bump needed. This branch is based on develop and is independent of fix: do not lose island progress when the server restarts #550.

Docs

Updated the holograms: block in 0_plains.yml — the reference phase file, and where the admin was already looking — to show all three syntaxes plus a gradient example.

Tests

565 passing. New coverage on both paths for MiniMessage, gradients, & codes, § codes and hex, asserting on the serialized formatting rather than the component tree shape.

Not boot-tested on a live server — the behaviour is exercised through the real Util code path in tests, but I have not watched a hologram render in-game.

🤖 Generated with Claude Code

https://claude.ai/code/session_014t1DSo2wMbTWZLcwXpwUmQ

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
100.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[tastybento]

The report

An admin coloured a phase hologram with <green><bold>Начало (Равнина)</bold></green> and got white text with the tags rendered literally.

Why

Holograms deserialized with LegacyComponentSerializer.legacyAmpersand(), which understands the 16 legacy & codes and nothing else. Adventure builds that instance with hexColours = false, so even &#RRGGBB did not work there.

The action bar used a second, separately configured serializer that did support hex but not MiniMessage. Two display paths, two different answers to "what formatting can I use here", and neither documented where anyone would look.

Display	Before	After
Hologram	& only	&, §, hex, MiniMessage
Action bar	& + hex	&, §, hex, MiniMessage
Boss bar title	unchanged — String API, BentoBox already resolves it	unchanged

The fix

Both Component paths now use Util.parseMiniMessageOrLegacy, which accepts MiniMessage, & and § codes, hex, and any mixture — and is cached on the BentoBox side, so the per-block hologram and action bar rebuilds do not re-parse the same strings.

This also fixes § codes being rendered as literal text. Translations come back from User.getTranslation already converted to § codes, so anything locale-sourced was being handed to a serializer bound to &. That affected the starting hologram (aoneblock.island.starting-hologram) and the action bar. Phase file hologram lines never see the translation layer, which is why the reported case showed raw MiniMessage tags rather than raw § codes.

I flagged this § behaviour as suspected when I first read the code — it is now confirmed by tests that fail against the old serializer.

Compatibility

• Existing configs are unaffected.& codes keep working and are covered by tests.
• BentoBox's MiniMessage instance is the non-strict MiniMessage.miniMessage(), so a hologram containing stray angle brackets (<-- break this) is left as literal text rather than throwing.
• Util.parseMiniMessageOrLegacy is BentoBox 3.2.0 API — no dependency bump needed. This branch is based on develop and is independent of fix: do not lose island progress when the server restarts #550.

Docs

Updated the holograms: block in 0_plains.yml — the reference phase file, and where the admin was already looking — to show all three syntaxes plus a gradient example.

Tests

565 passing. New coverage on both paths for MiniMessage, gradients, & codes, § codes and hex, asserting on the serialized formatting rather than the component tree shape.

Not boot-tested on a live server — the behaviour is exercised through the real Util code path in tests, but I have not watched a hologram render in-game.

🤖 Generated with Claude Code

https://claude.ai/code/session_014t1DSo2wMbTWZLcwXpwUmQ

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
100.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[tastybento]

The report

An admin coloured a phase hologram with <green><bold>Начало (Равнина)</bold></green> and got white text with the tags rendered literally.

Why

Holograms deserialized with LegacyComponentSerializer.legacyAmpersand(), which understands the 16 legacy & codes and nothing else. Adventure builds that instance with hexColours = false, so even &#RRGGBB did not work there.

The action bar used a second, separately configured serializer that did support hex but not MiniMessage. Two display paths, two different answers to "what formatting can I use here", and neither documented where anyone would look.

Display	Before	After
Hologram	& only	&, §, hex, MiniMessage
Action bar	& + hex	&, §, hex, MiniMessage
Boss bar title	unchanged — String API, BentoBox already resolves it	unchanged

The fix

Both Component paths now use Util.parseMiniMessageOrLegacy, which accepts MiniMessage, & and § codes, hex, and any mixture — and is cached on the BentoBox side, so the per-block hologram and action bar rebuilds do not re-parse the same strings.

This also fixes § codes being rendered as literal text. Translations come back from User.getTranslation already converted to § codes, so anything locale-sourced was being handed to a serializer bound to &. That affected the starting hologram (aoneblock.island.starting-hologram) and the action bar. Phase file hologram lines never see the translation layer, which is why the reported case showed raw MiniMessage tags rather than raw § codes.

I flagged this § behaviour as suspected when I first read the code — it is now confirmed by tests that fail against the old serializer.

Compatibility

• Existing configs are unaffected.& codes keep working and are covered by tests.
• BentoBox's MiniMessage instance is the non-strict MiniMessage.miniMessage(), so a hologram containing stray angle brackets (<-- break this) is left as literal text rather than throwing.
• Util.parseMiniMessageOrLegacy is BentoBox 3.2.0 API — no dependency bump needed. This branch is based on develop and is independent of fix: do not lose island progress when the server restarts #550.

Docs

Updated the holograms: block in 0_plains.yml — the reference phase file, and where the admin was already looking — to show all three syntaxes plus a gradient example.

Tests

565 passing. New coverage on both paths for MiniMessage, gradients, & codes, § codes and hex, asserting on the serialized formatting rather than the component tree shape.

Not boot-tested on a live server — the behaviour is exercised through the real Util code path in tests, but I have not watched a hologram render in-game.

🤖 Generated with Claude Code

https://claude.ai/code/session_014t1DSo2wMbTWZLcwXpwUmQ

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
100.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[tastybento]

The report

An admin coloured a phase hologram with <green><bold>Начало (Равнина)</bold></green> and got white text with the tags rendered literally.

Why

Holograms deserialized with LegacyComponentSerializer.legacyAmpersand(), which understands the 16 legacy & codes and nothing else. Adventure builds that instance with hexColours = false, so even &#RRGGBB did not work there.

The action bar used a second, separately configured serializer that did support hex but not MiniMessage. Two display paths, two different answers to "what formatting can I use here", and neither documented where anyone would look.

Display	Before	After
Hologram	& only	&, §, hex, MiniMessage
Action bar	& + hex	&, §, hex, MiniMessage
Boss bar title	unchanged — String API, BentoBox already resolves it	unchanged

The fix

Both Component paths now use Util.parseMiniMessageOrLegacy, which accepts MiniMessage, & and § codes, hex, and any mixture — and is cached on the BentoBox side, so the per-block hologram and action bar rebuilds do not re-parse the same strings.

This also fixes § codes being rendered as literal text. Translations come back from User.getTranslation already converted to § codes, so anything locale-sourced was being handed to a serializer bound to &. That affected the starting hologram (aoneblock.island.starting-hologram) and the action bar. Phase file hologram lines never see the translation layer, which is why the reported case showed raw MiniMessage tags rather than raw § codes.

I flagged this § behaviour as suspected when I first read the code — it is now confirmed by tests that fail against the old serializer.

Compatibility

• Existing configs are unaffected.& codes keep working and are covered by tests.
• BentoBox's MiniMessage instance is the non-strict MiniMessage.miniMessage(), so a hologram containing stray angle brackets (<-- break this) is left as literal text rather than throwing.
• Util.parseMiniMessageOrLegacy is BentoBox 3.2.0 API — no dependency bump needed. This branch is based on develop and is independent of fix: do not lose island progress when the server restarts #550.

Docs

Updated the holograms: block in 0_plains.yml — the reference phase file, and where the admin was already looking — to show all three syntaxes plus a gradient example.

Tests

565 passing. New coverage on both paths for MiniMessage, gradients, & codes, § codes and hex, asserting on the serialized formatting rather than the component tree shape.

Not boot-tested on a live server — the behaviour is exercised through the real Util code path in tests, but I have not watched a hologram render in-game.

🤖 Generated with Claude Code

https://claude.ai/code/session_014t1DSo2wMbTWZLcwXpwUmQ

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
100.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[tastybento]

The report

An admin coloured a phase hologram with <green><bold>Начало (Равнина)</bold></green> and got white text with the tags rendered literally.

Why

Holograms deserialized with LegacyComponentSerializer.legacyAmpersand(), which understands the 16 legacy & codes and nothing else. Adventure builds that instance with hexColours = false, so even &#RRGGBB did not work there.

The action bar used a second, separately configured serializer that did support hex but not MiniMessage. Two display paths, two different answers to "what formatting can I use here", and neither documented where anyone would look.

Display	Before	After
Hologram	& only	&, §, hex, MiniMessage
Action bar	& + hex	&, §, hex, MiniMessage
Boss bar title	unchanged — String API, BentoBox already resolves it	unchanged

The fix

Both Component paths now use Util.parseMiniMessageOrLegacy, which accepts MiniMessage, & and § codes, hex, and any mixture — and is cached on the BentoBox side, so the per-block hologram and action bar rebuilds do not re-parse the same strings.

This also fixes § codes being rendered as literal text. Translations come back from User.getTranslation already converted to § codes, so anything locale-sourced was being handed to a serializer bound to &. That affected the starting hologram (aoneblock.island.starting-hologram) and the action bar. Phase file hologram lines never see the translation layer, which is why the reported case showed raw MiniMessage tags rather than raw § codes.

I flagged this § behaviour as suspected when I first read the code — it is now confirmed by tests that fail against the old serializer.

Compatibility

• Existing configs are unaffected.& codes keep working and are covered by tests.
• BentoBox's MiniMessage instance is the non-strict MiniMessage.miniMessage(), so a hologram containing stray angle brackets (<-- break this) is left as literal text rather than throwing.
• Util.parseMiniMessageOrLegacy is BentoBox 3.2.0 API — no dependency bump needed. This branch is based on develop and is independent of fix: do not lose island progress when the server restarts #550.

Docs

Updated the holograms: block in 0_plains.yml — the reference phase file, and where the admin was already looking — to show all three syntaxes plus a gradient example.

Tests

565 passing. New coverage on both paths for MiniMessage, gradients, & codes, § codes and hex, asserting on the serialized formatting rather than the component tree shape.

Not boot-tested on a live server — the behaviour is exercised through the real Util code path in tests, but I have not watched a hologram render in-game.

🤖 Generated with Claude Code

https://claude.ai/code/session_014t1DSo2wMbTWZLcwXpwUmQ

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
100.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[tastybento]

The report

An admin coloured a phase hologram with <green><bold>Начало (Равнина)</bold></green> and got white text with the tags rendered literally.

Why

Holograms deserialized with LegacyComponentSerializer.legacyAmpersand(), which understands the 16 legacy & codes and nothing else. Adventure builds that instance with hexColours = false, so even &#RRGGBB did not work there.

The action bar used a second, separately configured serializer that did support hex but not MiniMessage. Two display paths, two different answers to "what formatting can I use here", and neither documented where anyone would look.

Display	Before	After
Hologram	& only	&, §, hex, MiniMessage
Action bar	& + hex	&, §, hex, MiniMessage
Boss bar title	unchanged — String API, BentoBox already resolves it	unchanged

The fix

Both Component paths now use Util.parseMiniMessageOrLegacy, which accepts MiniMessage, & and § codes, hex, and any mixture — and is cached on the BentoBox side, so the per-block hologram and action bar rebuilds do not re-parse the same strings.

This also fixes § codes being rendered as literal text. Translations come back from User.getTranslation already converted to § codes, so anything locale-sourced was being handed to a serializer bound to &. That affected the starting hologram (aoneblock.island.starting-hologram) and the action bar. Phase file hologram lines never see the translation layer, which is why the reported case showed raw MiniMessage tags rather than raw § codes.

I flagged this § behaviour as suspected when I first read the code — it is now confirmed by tests that fail against the old serializer.

Compatibility

• Existing configs are unaffected.& codes keep working and are covered by tests.
• BentoBox's MiniMessage instance is the non-strict MiniMessage.miniMessage(), so a hologram containing stray angle brackets (<-- break this) is left as literal text rather than throwing.
• Util.parseMiniMessageOrLegacy is BentoBox 3.2.0 API — no dependency bump needed. This branch is based on develop and is independent of fix: do not lose island progress when the server restarts #550.

Docs

Updated the holograms: block in 0_plains.yml — the reference phase file, and where the admin was already looking — to show all three syntaxes plus a gradient example.

Tests

565 passing. New coverage on both paths for MiniMessage, gradients, & codes, § codes and hex, asserting on the serialized formatting rather than the component tree shape.

Not boot-tested on a live server — the behaviour is exercised through the real Util code path in tests, but I have not watched a hologram render in-game.

🤖 Generated with Claude Code

https://claude.ai/code/session_014t1DSo2wMbTWZLcwXpwUmQ

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
100.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[tastybento]

The report

An admin coloured a phase hologram with <green><bold>Начало (Равнина)</bold></green> and got white text with the tags rendered literally.

Why

Holograms deserialized with LegacyComponentSerializer.legacyAmpersand(), which understands the 16 legacy & codes and nothing else. Adventure builds that instance with hexColours = false, so even &#RRGGBB did not work there.

The action bar used a second, separately configured serializer that did support hex but not MiniMessage. Two display paths, two different answers to "what formatting can I use here", and neither documented where anyone would look.

Display	Before	After
Hologram	& only	&, §, hex, MiniMessage
Action bar	& + hex	&, §, hex, MiniMessage
Boss bar title	unchanged — String API, BentoBox already resolves it	unchanged

The fix

Both Component paths now use Util.parseMiniMessageOrLegacy, which accepts MiniMessage, & and § codes, hex, and any mixture — and is cached on the BentoBox side, so the per-block hologram and action bar rebuilds do not re-parse the same strings.

This also fixes § codes being rendered as literal text. Translations come back from User.getTranslation already converted to § codes, so anything locale-sourced was being handed to a serializer bound to &. That affected the starting hologram (aoneblock.island.starting-hologram) and the action bar. Phase file hologram lines never see the translation layer, which is why the reported case showed raw MiniMessage tags rather than raw § codes.

I flagged this § behaviour as suspected when I first read the code — it is now confirmed by tests that fail against the old serializer.

Compatibility

• Existing configs are unaffected.& codes keep working and are covered by tests.
• BentoBox's MiniMessage instance is the non-strict MiniMessage.miniMessage(), so a hologram containing stray angle brackets (<-- break this) is left as literal text rather than throwing.
• Util.parseMiniMessageOrLegacy is BentoBox 3.2.0 API — no dependency bump needed. This branch is based on develop and is independent of fix: do not lose island progress when the server restarts #550.

Docs

Updated the holograms: block in 0_plains.yml — the reference phase file, and where the admin was already looking — to show all three syntaxes plus a gradient example.

Tests

565 passing. New coverage on both paths for MiniMessage, gradients, & codes, § codes and hex, asserting on the serialized formatting rather than the component tree shape.

Not boot-tested on a live server — the behaviour is exercised through the real Util code path in tests, but I have not watched a hologram render in-game.

🤖 Generated with Claude Code

https://claude.ai/code/session_014t1DSo2wMbTWZLcwXpwUmQ

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
100.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud