I was thinking about a trait field or an effect which changes expected wages. But when I looked in the code yesterday, wages were 100% afk, so there is nothing we can do about it at the moment
Yeah... I wrote a number of times about that already. The plan is to generalize everything that we can and package the logic in separate modules (classes), like wages and ranks (ranks prolly post beta) are to be handled through "Tier" module. There is an issue about it...
The amount of stats and skills we have to deal with is simply too vast to maintain without centralized system.
In case of MC the game always should know how to ignore stats that he doesn't have. Otherwise problems begin much sooner due to unisex items which may have such stats too. I suppose adding all stats and hiding those he doesn't use is the best way.
Ok, I'll make one default dict with all stats for everybody.
Most likely such flags will be required for traits anyway. Some of them can be useful for MC, some cannot.
Oki, NPC/ArenaFighter/Mobs classes can benefit from flags as well, I think we already have some form of mob_only flag, I don't remember if we check for it in code but we must at one point.
I am going to take care of the common stats dict now.Actually, I think that we can just check if the character has a stat... it will be more appropriate. Especially if we add more trait flags.