Shared text formatting reference for Takion, PrismaticAPI, legacy colors, SIR tags, chat components, and MiniMessage.

Shared message formatting

Modern BitAspire plugins that use Takion and PrismaticAPI can process a mixed formatting stack. Product pages should still document feature-specific placeholders, but this page explains the shared concepts.

Supported families

Family	Example	Use it for
Legacy color codes	`&aHello`, `&lBold`	Simple colors and classic Minecraft formatting.
Hex colors	`&#2C08BAHello` or feature-documented hex forms	Precise brand colors when supported by the output channel.
SIR/Takion markers	`<P>`, `<C>`, `<n>`	Prefix insertion, centered text, and line separation in SIR-family configs.
PrismaticAPI tags	`<G:2C08BA>Text</G:028A97>`, `<R:1>Rainbow</R>`	Gradients, rainbows, and richer color processing.
MiniMessage	`<green>Hello</green>`, `<click:run_command:/help>Help</click>`	Adventure-style components when the plugin/channel supports component output.
Component channels	`[title]`, `[action-bar]`, bossbar entries	Routing text to titles, action bars, bossbars, or other output channels.

Mixed formatting

Takion/PrismaticAPI-backed text can intentionally mix legacy colors, Prismatic tags, and MiniMessage-style input when the target feature supports it.

private: '[title] <G:2C08BA>Welcome {player}</G:028A97><n>&7Enjoy the server.'

Use mixed formatting only where it improves readability. Simple messages are easier to maintain with simple legacy color codes.

Placeholders

Placeholders are feature-specific. Common examples are:

Placeholder	Typical meaning
`{player}`	Current player name.
`{target}`	Target player or argument.
`{message}`	Message body.
`{world}`	World name.
`{time}`	Duration or timing value.
`%placeholderapi_value%`	PlaceholderAPI value when PlaceholderAPI is installed.

Prefer documented lowercase placeholders. Some plugins keep legacy aliases for compatibility, but new examples should use lowercase or kebab-case names such as {ignore-users}.

Strings, lists, and line separators

If a message accepts a list, each item can become its own output line. If the feature uses a single string and supports line separators, use the configured separator such as <n>.

receiver:
  - '[title:3] &bHi, {receiver}!<n>&7{sender} mentioned you.'
  - '[action-bar] &eReply when you are ready.'

Practical guidance

Use plain legacy colors for simple admin messages.
Use Prismatic gradients/rainbows for short labels, not full paragraphs.
Use MiniMessage when click, hover, or Adventure components are needed.
Keep placeholders exactly as documented by the feature page.
Test titles, action bars, bossbars, Discord embeds, and chat separately because each output channel has different limits.

Message Formatting