Bay 12 Games Forum

scientology = lose

So I made a few sets of adamantine clothes with the spare threads i had lying around, and about a year later I noticed that the garment in question had become xcrappyx (it was claimed by a dwarf right after i forged it and they subsequently put it on). Why would adamantine become worn? It's a metal, much more durable than other materials, plus it's supposed to be some legendary-almost-mythical metal that is super awesome. Shouldn't such things be resistant to wear and tear? I mean, if raw adamantine can keep demons in the deep depths for thousands of years, I really don't think a dwarf wearing it as clothing will make it degrade, much less in only a year or two.

*edit* also, it takes entirely too many strands to make anything. If the point of having the wafer/cloth cost so high on making certain items is to limit the player's ability to churn out massive amounts of adamantine goods, i'd rather have it be 1 cloth for each piece of clothing, 1-3 wafers for each weapon/furniture, and have the strands takes 2-3 pieces of raw adamant each to produce. Sort of like how galena is 50% silver, raw adamantine would be much better as 50% adamantine strand.

[ December 23, 2007: Message edited by: puffs ]

Do the amphibious/flyer tokens mean that a creature doesn't get pushed around by water?

*edit* wrong forum, supposed to be in DF questions...sorry.

[ December 10, 2007: Message edited by: puffs ]

I'm not really sure why, but one of my children climbed up to the second level of my glass tower and started taking down a wall that i had designated to be removed.

Thought it'd be funny if every once in a while a migrating vagrant comes along, steals food/items from your stockpiles, and generally makes a nuisance of him/herself without doing any actual work.

Actually, never mind- I just described nobles.

But it would be interesting if you could have seasonal migrant workers...or dwarves that came/left after a year or two. Or, as opposed to a beating, another dwarven justice punishment could be banishment from the fort.

One big problem with CPU usage issues right now is that liquid flows never "settle" - after infinite years, a magma vent that loses a tiny bit of magma still has a sole 6-depth square running around in it.

What i'd like to propose is a smoothing algorithm that makes the ripples go away after a certain amount of time.

1) define the body of the liquid.
  Any tile that is adjacent to at least two contiguous solid objects that block flow (floodgates, cavern walls, constructions) is a liquid boundary.
Example:

code:

---

 These are liquid boundaries.
    xxx     Lxx     xLx
    LCL     LCL     xCL
    LLL     LLL     LLx
   These are not boundaries.
    LxL     xLx     LxL
    LCL     LCL     xCx
    LxL     LLL     LxL
C= current tile
L= liquid  
x= solid object

---

2)Handle depth changes/determine state of flux
Any time a depth change occurs at a liquid boundary, the surrounding liquid-containing tiles are examined for fluid depth. If there is a variation of 2 or more between the low depth and high depth in the 'block', liquid continues as per currently. If not, proceed to step 3.

3) Flow reduction.
Take the average depth of liquid in the block (floating point) and set the depth of each tile to that number the next "tick", rounding up >.5 and truncating otherwise.

I understand this may lead to undesirable results - draining a small portion of a reservoir would end up not decreasing its depth at all, but I think it would be nice to be able to have flows not chug processor cycles for ever and ever.

If you're really picky about having realistic fluid volume, just change the depth to be stored as floating-point and displayed as integer.

[ December 19, 2007: Message edited by: puffs ]