Print

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

[Loci]

The current system makes control of visitors, residents, and children completely impossible, which can be problematic in a number of cases (ex. a resident nearly drove himself mad by repeatedly riding my archer-minecart past scary corpses. I've constrained him with burrows for now, but that won't work when a civilian alert is active.). Instead, I would suggest a graduated control system with three levels: Permit, Request, and Require. Visitors and children could be permitted to do work (though they would only perform occasional jobs when they choose to), residents could be requested to do work (more frequent jobs than visitors, but less frequent than citizens), and citizens would be required to do work (the same as current labor assignments). At all levels disabling the labor would prevent that particular type of job. So the player could allow a visiting armorsmith to hammer out a few steel helms or a particularly-helpful child to contribute to the fortress occasionally, ask long-term residents to "earn their keep" by performing some work (and satisfy some of their needs as well), and forbid everybody from stressful minecart rides. A particular creature's willingness to help out could depend on personality traits (e.g. sense of duty), state of mind, skills, item preferences, etc. A visiting weaponsmith might jump at the opportunity to make iron maces (satisfying two preferences) and completely refuse to haul refuse.

[PatrikLundell]

I agree with the logic for children and residents, but less so for visitors.

One problem with visitors is that they can come in large hordes (sometimes literally, in the case of questor hordes, and performance troupes sometimes contain members that are described as having a non performer job), which makes it a pain to keep them set to appropriate working states. I wouldn't mind some kind of system where visitors could request permission to use workshops, though, as long as it's kept to a reasonable level (a fair bit less frequent that residence petitions, maybe down to a maximum of once per season or something like that), but in that case you'd definitely need to get more info than you get for petitions, such as e.g. skill level and what they want to produce. There'd also have to be some way for those jobs to be introduced into the appropriate workshops without too much trouble (inserting a "make steel mace" job won't work unless the workshop is also locked to allow only the requestor, for instance, so it would need a "personal" job type where the job is inserted into the workshop and tied to a particular individual, and the workshops would need some way to tag them for eligibility for those kinds of jobs (possible to modify on a per case or general basis from the request interface). Said individual would also have to jump to it immediately when the job appears (similar to NOW!, but without the negative thought) so the bugger doesn't spend half a year in a temple while blocking the workshop, only to then move on to the library for a reading binge for instance. If introduced, that kind of system might work to allow for citizens to satisfy some of their needs on their own without player micro management, though, although you'd probably have to permit/disallow materials, so they won't waste precious resources on their hobby dabbling.

[Shonai_Dweller]

I agree, more types of occupations should be available to visitors (not direct control or labour setting though, they are visitors, after all). There's no issue with blocking workshops once they're replaced by zones. It's just extra labour for hire.

[GoblinCookie]

Visitors should be able to work but it should upset them if they are employed in things that they consider not their occupation.  It is basically, we will do the work you ask but if you give them us too much unsuitable work we will just up sticks and leave.

Also we need to be given control of the labour list of [CAN_LEARN] 'pets'.  Currently they work based upon a default labour list which we cannot ever modify.