Bay 12 Games Forum

What you're asking for is to convert the entire mathematical foundation of the unit system in the game from integers to floating point numbers for really no good reason:

• There's no real performance benefit
• There could be a decided performance decrease; if doubles are used, they're twice the size of ints, and if floats are used, they suffer from imprecision errors with repeated use
• They're no more obvious than integers are and take more screen real-estate (as you have to list all the preceding zeroes with a floating point number but not with an integer)

The main benefit to using floating point numbers is that they're the only way to handle true fractions. When you're taking 63% of a number, you're not guaranteed to get an accurate end result if you do the math using an integer. When all of your math is done using fixed, whole numbers, floating points offer no benefits.

Actually, the biggest issue with using floating point (or double) values is that, because the fraction is stored as binary, you get infinitely repeating sequences on some rather stupid values.  For example, 0.1 is an infinitely repeating sequence.  The result of this is that, regardless of your precision, you cannot accurately add these numbers up: subtracting 0.1 from 1 ten times will give you a very tiny (but not zero!) number, because you cannot have infinite precision.  Naturally, having .000000000000000138778 of a piece of cloth is not particularly useful.

The issue is that meals made out of nothing but booze disintegrate.  This disintegration counts as art defacement.

Your suggestion would not work and is literally identical to a single-threaded process, except with a whole bunch of overhead.

You do not seem to know much of anything about multithreaded programming, or programming in general, so I suggest you just drop this.  It would be a colossal amount of work for absolutely minimal gain.  Only in situations where multiple processes need to be done at the same time and have absolutely minimal interdependencies is multithreading reasonably helpful.

Also, your definition of "turn-based" is pretty terrible, as every game in the history of ever has had a simulation framerate, so according to you there has never been a real-time game ever.

death from melting is recorded as bleeding to death. drop something...say a fish... in magma, and it'll die of blood loss real quick.

Death from melting is properly recorded as death from melting.  See: bronze colossuses.  Most normal creatures, however, cannot actually melt to death, as their body does not actually have a melting point.

The issue is that FAT has a melting point, and it's relatively low.  Fat also bleeds rather heavily.  So, if it gets warm enough, ALL your fat starts melting, resulting in MASSIVE bleeding.

This can be fixed by either removing the melting point of fat (in material_template_default.txt, under FAT_TEMPLATE) or somewhat more hilariously removing blood vessels from fat (in tissue_template_default, again under FAT_TEMPLATE, changing [VASCULAR:3] to [VASCULAR:0]).  If you just remove the blood vessels, you will "melt" without any issue, leaving a trail of grease behind you, until all your fat is gone.

A side-effect is that dragons are a bit less deadly as it takes multiple breaths to get hot enough to start burninating people, rather than a single breath to just melt their fat.  But really, it was silly anyway.

he's in a mood! Make sure you have the things he's sketching pictures of and he'll make you an artifact.

Of course, if he's in there sketching, that means you DON'T have the items.  You can see what he already has by the items that are TSKed in the workshop, so you need to acquire whatever he's asking for that ISN'T there.  Note that moody dwarves have to get the items in order, so if he wants rocks shells gems, and you have rocks and gems, he'll only get a rock and start whining about shells until you get him one.

In my experience, the issue is that designating a barracks from a weapon rack, armor stand, or bed does not result in the proper behavior.  In order to get lessons and sparring, you need to designate from a coffer instead.

On the other hand, individual training is considerably more effective and results in fewer lopped off limbs (they didn't even stop sparring until one got his cheek cut and then GASP off to the hospital to treat that!), and less time standing around waiting for somebody who never shows up.

I think having the dwarves only train every other month would be more effective, as it would hopefully synchronize their schedules enough for sessions to actually get done.

What I think happens is that the dwarf takes the booze OUT of the barrel to cook it.  Then, when he finds that there's not enough to cook something, there's no way to get the booze back INTO a barrel.  If you dismantle your kitchen it will explode into alcohol.