Skip to content

Translating Messages

Purdze edited this page Sep 24, 2026 · 1 revision

Every text players see is in plugins/Hounded/messages.yml, so you can recolour or translate all of it.

How it works

  • Messages use MiniMessage formatting: <red>, <bold>, <gradient:gold:yellow> and so on.
  • Words in angle brackets that aren't formatting tags, like <player> or <time>, are placeholders that Hounded fills in. Keep them in your translation. You can move them, but don't rename them.
  • To show a literal <, write \<. The help texts do this for \<player>.
  • prefix is put in front of chat messages.
  • Keys missing from your file fall back to the bundled English, so a partial translation still works. Hounded never overwrites your file.
  • Apply changes with /hounded reload.

Placeholders per message

Placeholder Used in
<player> role.assigned, role.removed, role.not-assigned, round.runner-*
<role>, <roles> role.* (filled from role.name.*)
<players> role.list
<seconds> start.headstart, start.headstart-too-long, round.runner-left
<time> display.headstart, display.timer, win.*
<runner> compass.how-to-use-*, compass.now-tracking, compass.no-data, display.distance, display.distance-portal, display.no-trail
<distance> display.distance, display.distance-portal
<dimension> display.distance-portal (filled from dimension.*)

Plain-text names

role.name.*, state.* and dimension.* are single words or short phrases that get inserted into other messages and placeholders. Translate them too, and keep them free of formatting if you use the placeholders in other plugins.

Sharing a translation

Translated Hounded? Share your messages.yml in an issue so other servers can use it too.

Clone this wiki locally