Certain items, e.g. heated lode, were meant not to
be carryable so that players would need to plan
certain constructions properly. The "hot potato"
feature was added to achieve this, and I had
assumed that players would eventually find it
sufficiently frustrating that they would stop and try
to figure out how to do things properly. This has
not worked out, and players working at a forge
spend a lot of their time fiddling with hot things
trying to randomly throw it into the right spot.
This change should make it more difficult for
players to manipulate the "hot potato" item
physics to move items that shouldn't be movable
by hand once heated. Problems involving heated
item placement need to be solved through proper
furnace design, not workarounds. As a bonus, it's
now also harder to accidentally hot-potato your
items into places it's hard to get them out of.
At some point in the future, we will probably be
adding tongs to provide a proper way to move
these items, once players have reached the
proper tech level.
We were using the igniter's position instead of the
flammable's to check if the flammable had already
been tested, which caused fire not to spread fully
though large blocks of contiguous flammables, and
biased the direction of fire spread where it did.
Thanks to Elon_Satoshi a.k.a. Copenhagen_Bram for
discovering, reporting, and helping to confirm that
this bug had a long history.
- Add debug logging
- Raise the ignition check limit to 250%
- Atomic ignition queue management, to ensure that
there's no chance of things getting "stuck" in the
blacklist due to partial queue resets
The new method of intercepting item addition into
player inventories hooks into the base metatables for
the userdata types only once per type, instead of
trying to substitute every inventory object with a
table (which crashed some things) and does a lookup
to find the player per inv. This should hopefully be
more reliable, and avoid some of the leaks to
rearrangement we had before.
If we can finally stop hitting the player inv rearrange
safety net then it can be removed.
The use of hash instead of string for pos was causing
a bug in doors some time ago where doors would
randomly fail to fire ... and then now we're seeing
reports of fire that refuses to ignite for some specific
planks...
Thanks to Kimapr for the basic approach, and proving
the concept.
Doors pressing a single-item stack now place that
item as a node, and trigger placement recipes. Doors
pressing nodes that don't have a single item stack
node form (sticks, leaves) also trigger placement
craft recipes.
All craft pressing recipes require some form of
backstop to provide pressure.
This reverts commit 253c2282917ecade5b8356d592edab40b1d517f5.
Apparently this warning is full of crap. Explicitly
setting use_texture_alpha in the node def does
something DIFFERENT than what the engine says
it's doing enabling it internally. use_texture_alpha
enables alpha BLENDING, which is what we
don't want with interpolation filters, whereas
leaving it off enables alpha THRESHOLDING which
is exactly what we want.
- Add reset command
- Reset alerts on resetting state
- Add option to hide hints
- Add option to add custom hint attrs
- Add option to pass in an already-fully-formed
hint object and skip construction helpers
- Tidy up terrain hints a bit
ContentDB's .gitattributes export-subst support
has been broken for a while now, and apparently
won't be fixed (it's depending on an upstream
that is similarly ignoring the issue).
We need to account for the fact that what looks
like a dev version might actually be a CDB
version that's simply not tagged right.
