>I think that if you're truly going to bother, then being able to mix
>liquids together, add things to liquids (both soluble and
>non-soluble), freeze them, heat them up, and such like. Of course, I'm
>sure most people would stick with just being able to drink it and have
>it seep into cracks when dropped (without a container).
^^^^^^^^^^^^^^^^
I plan support for puddles. (At the programmer's option, of course.)
I'm a bit worried about mixing. Clearly, if you have the potential for
containers partly filled with liquids, you have the potential for the
player to pour another liquid in. And the programmer should be able to
make specific combinations yield new liquids, whether the player is an
alchemist or a bartender. But what about combinations the programmer
hasn't specified? I see two basic alternatives:
a) Forbid them entirely. "I don't think you should mix those..."
b) Provide a default that produces a generic liquid without special
properties and the sdesc "mixture of <foo> and <bar>"
I'm inclined to go with a, because it's more honest - b makes some
pretence of a level of simulation that doesn't exist. What do you think?
By the way, in concerns with liquids in general, remember that we're
talking about _all_ liquids. Does the property you have in mind apply to
mercury? Liquid nitrogen? Lava? Maple syrup? I'm even contemplating
generalizing this library to dry materials, like flour and sand, that
behave like liquids in certain respects, and I'm undecided about whether
I want do deal with specifically liquid properties at all.
Anyway, thanks for the suggestions. Keep them coming!
-- Carl Muckenhoupt | Is it true that Kibo habitually autogreps all of Usenet baf@tiac.net | for his name? If so: Hi, Kibo. Like the sig?