World Message

World Message is a map-level display block used to show text to all players on a map. It functions like a global Message but is tied to the world and cannot be destroyed by players or enemies, making it suitable for persistent informational displays such as map tips, story text, or status notifications.

When editing in-game, interacting with a Message block and tapping the pencil button allows a player to enter custom text with a 220-character limit. Text displayed on World Message supports simple color markup using HTML-like tags: a colored portion begins with a tag of the form [color] (where color can be a preset name or a hex code) and the colored span is closed with empty square brackets []. This enables highlighting parts of a message without relying on external assets.

Icons for blocks, items, and units can be inserted into the message text on desktop platforms by opening the Core Database and shift-clicking an entry; that action copies the icon text into the clipboard and it can be pasted into the Message. This works because the icons in the Core Database are treated as renderable text and therefore integrate into chat and Message displays.

World Message can be manipulated programmatically by logic processors: World Processors use the Print and Print Flush commands to compose and send text to a Message. Print appends a string onto an internal queue, allowing multiple Prints to build a longer message in parts; Print Flush writes the queued string to the target Message block and then clears the queue for subsequent use. This queuing behavior makes it straightforward to construct messages dynamically from multiple sources or repeated logic cycles.

Practical notes and usage tips:

• Because World Message cannot be destroyed, it is ideal for map authors who need permanent on-screen guidance or narrative text.
• Keep messages concise due to the 220-character cap; use color tags and icons to convey additional meaning without extra characters.
• When building dynamic displays, use Print to stage parts of the message and call Print Flush once the full content is ready; remember the queue resets after flushing.
• On desktop, exploit the Core Database icon copy trick to include recognizable item/unit symbols in messages; on mobile, icons must be entered manually or via logic.
• Use color tags sparingly and always close colored spans with [] to avoid leftover formatting affecting following text.