Bay 12 Games Forum

this is a second prototype, with a much more complex system and some other improvements. (the gist of what this about: making feeding your fort (much) harder and more interesting by giving food different properties and making units eat more.)

* not only item types but materials are now considered. item types have a base value, materials are composed of different types of nutrition (fat, protein, complex carbohydrates, sugar, fiber, water, alcohol).
* each of these types modfiy the base value and have different effects on the unit's hunger, thirst, stomach content/food and body fat values. for example, a PLANT_GROWTH of base value 8000 that is composed soleley of fiber will reduce hunger by about half that amount, but actually burn fat, and put a lot of useless material in the stomach. an egg with the same base value will decrease hunger by about 6000, while taking up less space in the stomach(but adding more nutrition to it). a sugary treat of the same size will cause the unit to put on some extra weight, and put enormous amounts of nutrition into the stomach, while taking up only little room.
* materials are ordered into groups tied to several plant/creature tokens, such that a group of species shares nutrition values for their materials. example:

using this system, no raw modfification at all is necessary, all the data is read from the table. in addition there is a set of default values for common material tokens (LEAF, FRUIT, MUSCLE, BRAIN, DRINK, ...) so this will work with pretty much any set of raws.

* no longer causes dwarves to eat more often, instead units will eat several items in a row until their hunger threshold is reached. to facilitate that, the hunger/thirst counters are stored and only written into memory after several jobs were completed.
* immoderation has a strong effect on the unit's subjective feeling of hunger. dwarves will eat up to 33% less or 88% more than their hunger would dictate. this, together with the above changes, will lead dwarves to go on massive binges, some more so than others. immoderate dwarves will grow fat and lardy (this requires further testing tho).
* this doesnt quite work so well yet with drinks, mostly because the alcohol syndrome isnt made for it (and the base value for drinks is fairly low, a beer gives about 1/5th of the normal value). dwarves will frequently drink until theyre unconscious, and then immediately drink again when they wake up.

stuff:
- drink water, give water, and serve drink are not yet implemented
- in future versions, there will be more counters that need to be stored and updated, like vitamins, etc. currently im using persist-storage to track jobs, but i am not sure it will be fast enough to update ~200 units and their counters every tick?
- is editing syndrome severity in memory feasible? do alcohol effects from multiple sources stack? i could base the alcohol effects on the alcohol content of the drink directly, if i edit the syndome after it is applied. this way there is no need for multiple alcohol templates, and it is more granual.
- stomach_content doesnt seem to do much, it just goes up to 300000 but doesnt seem to stop dwarves from eating. its conceivable that eating a lot of fibrous stuff without any nuttrition actually is dangerous.

code:

im wondering how many items plants with multiple growths will yield when harvested, and how seed-type growths behave. basically, how many seeds will a plant give from growth only, and will the plant always yield 1 of each type of growth that it has?

furthermore, if i have a reaction that uses various plants with multiple item reaction products, can i use empty item products? such that i can get say a couple of seeds, fruit and leaves from one plant, and just seeds and fruit from the other? how would a blank item product look like then, or would i just leave it out?

Im writing a simple script to make members of the fort eat/drink more. what it does is that it browses through all units with the right civ_id
every few ticks and then increments the counters.

now the thing is, the list of active units with civ_id being the fortress civ includes a lot of random stuff. my fortress with 101 residents and 119 pets has 265 units that belong to my civ for some reason or another. what flag(s) in the unit struct can i use to distinguish eaters (dwarves and foreign residents only) from non-eaters (pets/ghosts/..) ?

im trying to implement the typical vanilla [FUEL] behaviour for a custom (dfhack-made) job. basically i generate a reaction with fuel tag at some point in time while the game is running and then issue a job for it. this works fine, except the [FUEL] doesnt - the job behaves as if there was no fuel needed. i dont know why this happens, presumably because the reaction didnt exist when the game was loaded first?

so i tried to add a bar of fuel to the job struct directly, which is possible, but the fuel will not be used up in the process. my dwarf will get a bar of fuel, use it in the reaction, and then the bar of fuel will remain in the workshop.

what can i do about this?

im trying to implement a menu script for my custom smelter that lets you select a class of ore first before presenting to you a selection of ores from that class to pick from. should be basically the same kind of ui that some built in workshops have, like forge, glassmaker etc.

now the problem is that eventful seems to only provide a callin routine for replacing the whole wokshop menu, not just the "Add new task" submenu. how would i go about just replacing that, while keeping the basic menu?

so how exactly does the new fruit harvesting work, what kind of growth will it harvest? since leaves i assume wont be plucked off plants, and there are a couple off odd things such as artichoke hearts, how does the game determine which growths are meant to be picked and which are meant to be put into bags? how will that affect custom growths that dont go by regular names?

is completely disabled now? i made a custom civ that starts with expert levels in climbing, as well as stance climber (like cats do, climbing with either hands or legs) but they refuse to climb at all. in fact they just sit around at the bottom of a 1z deep pit of rough soil walls, aparently unable to path out and take jobs - i didnt test if they also prefer to starve to death, but i guess they would.

which is sad, because i would love to build my fortress around the idea.