Saltar al contenido principal

Nameplate Data

Entity data that gives one Typewriter entity its own nameplate, instead of relying on the global mob rule. Being entity data, it is viewer-specific and takes part in the normal Typewriter property precedence.

Use it for a named NPC, a boss, or any entity whose plate has to say something the global rule cannot express.

Text

lines holds MiniMessage lines and accepts resource pack font glyphs directly. It is a @Placeholder field, so PlaceholderAPI placeholders resolve per viewer.

placeholders adds literal replacements on top, written without percent signs.

FieldDefaultDescription
offsetY0.5Base height above the entity position.
lineSpacing0.3Vertical distance between lines (floored at 0.05).
backgroundColor0ARGB background; zero is fully transparent.
textOpacity2550–255, clamped.
lineWidthunboundedMaximum line width before wrapping.

Same three-slice mechanism as the other entries: craftEngineImageId is a prefix, resolved to <prefix>_left, <prefix>_middle and <prefix>_right. tileWidthPx (16), capWidthPx (3) and paddingPx (10) shape it, and bannerLineCount (1) decides how many top lines it covers — 0 covers all of them.

Single-display entities

Entities that render their own nameplate — BetterModel models, BTC mobs — do not get a second display. The banner is folded into the same string as the text. This is why capWidthPx has to match the real artwork width: on those entities there is no separate background to hide a mismeasurement, and the banner visibly eats into the text.

Attachment

attachment points at any EntityDefinitionEntry — an ItemDisplay, a BlockDisplay, a vanilla entity, or a BetterModel definition — displayed alongside the plate. attachmentOffset positions it relative to the entity, attachmentScale sizes it (floored at 0.01).

Never point an attachment at its own definition

An attachment that resolves back to the definition carrying this data spawns the entity a second time: you get a duplicated NPC and a duplicated nameplate. The attachment must always be a different definition.

Stacking

When several suppliers apply to the same viewer, lines and placeholders are concatenated across all of them, while every other field comes from the last applicable supplier. Several data entries can therefore each contribute a line to one plate.

See also