Print

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

[Infiltrator]

Well, footsy didn't like me saying this is a bug (I think it's strange behaviour, but yeah), so I guess I'll post this here instead:


I have a dwarf with Talented Tanner (V Rusty) and Proficient Mason, but he's still called a tanner, rather than mason.

Now, I think (yes, yes, it's only an opinion) that unless the dwarf is assigned the labour in the p->l screen, than only its rusted value should count in terms of determining profession name. So, in the case above, he should be called a mason, UNLESS I turn tanning back on for him.

The reason is that sometimes your doctors and other dwarves start to rust because there isn't enough work for them (yes, I need to manage better; but that's not the point), but if they still have the labour assigned to them, they should still count the unrusted value so that you can find them easier. After all, that is what the unit list is for, isn't it?

[Granite26]

So... subtract levels of rusty from skill level for purposes of class/profession name?

[Dutchling]

You know you can create custom jobs for Dwarfs right? Why do you want to solve a ''problem'' if it already solved?

[Infiltrator]

Granite26: Yeah, basically. But not if they still have that labour enabled. So, if you keep a doctor's labours on, but he gets rusty, you'll still see him as a doctor, and be able to find him easily.

Dutchling: You know that doesn't solve the problem at all, right? Sure you can rename their profession, but when you go to the unit list, you still have to scroll down to the brown section and try to find your dwarf out of all those farmers whose profession you've renamed. So yeah, not solved. Why do you claim that a problem is "solved" if it isn't?