Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[Gnomechomsky]

When drafting a dwarf with a custom profession name, instead of saying "<dwarf> has become a recruit", it says, "<dwarf> has become a <existing custom profession label>".  Not sure what the behavior should be, though...we should still be able to customize the labels on military dwarves, right?

Maybe "Urist McDwarf, Plumber, was drafted into the military"?

[Yanlin]

Urisonald McDonald has created McDonalds!

Urist McFreeman has become a combatant.

[MMad]

Hm.. I'm thinking custom civilian profession labels should be seperate from custom military profession labels. So you could have a "Plumber" be drafted to a "Recruit" (default), rename his military profession to "Manhandler", then un-draft him and have him become a "Plumber" instead.

The main argument in favor of this approach is that pretty much no custom profesison label, civilian or military, would be relevant after drafting or un-drafting.

[Proteus]

This has always been the case, custom titles stay the same no matter what military or civilian position the dwarves take.
I assume it isnīt a bug but a feature (which I often use, for example to name my legendary dwarves; it is useful to know, for example if I mass draft the dwarves in case of an emergency, that this dwarf is my legendary woodcrafter (or one of the founders, who each get their custom titles upon embark) and not a common recruit like everyone else).

[Yanlin]

What's up with plumber?

Is the guy named Urist McMario?

[Gnomechomsky]

This has always been the case, custom titles stay the same no matter what military or civilian position the dwarves take.
I assume it isnīt a bug but a feature (which I often use, for example to name my legendary dwarves; it is useful to know, for example if I mass draft the dwarves in case of an emergency, that this dwarf is my legendary woodcrafter (or one of the founders, who each get their custom titles upon embark) and not a common recruit like everyone else).

I agree...the behavior isn't necessarily wrong, but the wording of the message makes it confusing.  He's becoming a recruit, not a <whatever I labeled him as>.  Either just clarifying the message, or making two separate labels for civilian and military would work.