Ctrlk
Homepage
For the complete documentation index, see llms.txt. This page is also available as Markdown.

CustomDeathMessage.txt

Themed per-monster taunts shown to the victim in chat when that monster kills a player

Maps a monster class (monster type id) to a custom taunt delivered to the killed player in chat. Overrides the vanilla death message for that monster class. Gated by Custom.dat CustomDeathMessageSwitch.

File Location

Data/Custom/CustomDeathMessage.txt

Loaded once at GameServer startup. Changes require a restart.

Format

Plain text, whitespace-delimited. The first comment line names the columns; each following row is <index> "<text>". The file is terminated by the literal end on its own line or by end-of-file.

//index text
1 "Hihihih I'm Very Strong Monster"
2 "Hihihih I'm Very Strong Monster"
...
end

Columns

Column
Type
Effect

index

int

Monster class (the monster's type id). Same numbering as Monster.txt entries

text

quoted string

Taunt sent to the player's chat when a monster of this class kills them. Stored in a 128-byte buffer (127 usable chars plus null terminator)

Important Behavior

  • Enabled by Custom.dat CustomDeathMessageSwitch = 1. Setting it to 0 disables the feature entirely; no replacement message is sent

  • Only triggers when a monster kills a player. Player-on-player kills are unaffected

  • The taunt is delivered to the killed player only, shown as chat originating from the killing monster. It is NOT broadcast to nearby players

  • Monster classes not listed here produce no custom taunt; there is no fallback vanilla death-line system - the field is simply silent

  • Duplicate indices: the last occurrence wins silently

  • Rows beyond the 127-char text limit are truncated when loaded; the chat send path truncates further at 255 bytes

Examples

Cross-File Dependencies

Value
Related in

index

Must match a monster class id in Monster.txt

Master toggle

Custom.dat CustomDeathMessageSwitch

Common Issues

  • Messages not appearing - CustomDeathMessageSwitch = 0 in Custom.dat, or the killing monster's class is not listed here

  • Wrong monster says the wrong line - index mismatch with the monster class table; verify the shipped monster list

  • Text cut off mid-sentence - message exceeded the 127-char text buffer or the 255-byte chat send cap; shorten it

  • Special characters mangled - file encoding is ANSI; multibyte characters may garble. Use plain ASCII where possible

PreviousDefaultClassInfo.txtNextEvent

Last updated