| Commit message (Collapse) | Author | Age |
|---|
| | |
|
| |
|
| |
Add backwards-compatible metatable functions for vectors.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
fixes #10695
|
| | |
|
| |
|
|
|
| |
Falling nodes that were spawned prior the recent falling node changes did not require param2.
Default to param2 = 0 when none is found in the node data.
|
| | |
|
| |
|
|
| |
Co-authored-by: sfan5 <sfan5@live.de>
Co-authored-by: SmallJoker <SmallJoker@users.noreply.github.com>
|
| |
|
|
|
| |
falling nodes intentionally still fall through players
fixes #5313
|
| |
|
|
| |
fixes #4781, fixes #9293
|
| |
|
|
| |
colorwallmounted, color, airlike, signlike, torchlike and glow (#9205)
|
| | |
|
| |
|
| |
Fix (or workaround?) for 'Falling nodes with node inventory cause crash when unloaded'
|
| |
|
|
|
|
|
|
|
| |
* Add sounds for falling and attached nodes
The sound specified in `node_definition.sounds.fall` is used.
When a falling node is spawned at a position or an attached node drops, the sound is played at this position.
* allow all sorts of soundspecs
|
| | |
|
| | |
|
| |
|
|
| |
Allow changing the velocity of objects relatively to their current velocity
|
| |
|
|
|
|
| |
Prevents falling node entities entering the ignore at a world edge and
resting on unloaded nodes 16 nodes below, unreachable, undiggable and
still being processed by 'on step' because they don't revert to nodes.
|
| | |
|
| |
|
|
|
|
|
|
| |
Falling nodes should make a sound. This can only be done here,
so for simplicity we just call the sound_play() here with the node
place sound. We ignore any gain value in the sound spec since a
falling node should be loud, so the 1.0 default gain makes sense
here.
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* Automatic item and node colorization
Now nodes with a palette yield colored item stacks, and colored items
place colored nodes by default. The client predicts the colorization.
* Backwards compatibility
* Use nil
* Style fixes
* Fix code style
* Document changes
|
| | |
|
| |
|
|
|
|
|
|
| |
* Add minetest.spawn_falling_node(pos)
* lua_api.txt: Add minetest.spawn_falling_node(pos)
* Update minetest.spawn_falling_node(pos)
|
| |
|
|
|
|
| |
Correct node placement prediction for attached colorwallmounted nodes.
Correct placement direction for colorfacedir and colorwallmounted nodes.
Correct detatch mechanism for attached colorwallmounted nodes.
|
| | |
|
| |
|
|
|
| |
If the object pos is over limit, 'add entity' will not add an entity,
causing 'obj' to be nil.
|
| |
|
|
|
|
|
|
|
|
|
| |
Fixes #4778 which was about the error:
ServerError: Lua: Runtime error from mod '' in callback item_OnPlace():
/usr/local/share/minetest/builtin/game/item.lua:278: attempt to call global 'check_attached_node' (a nil value)
The issue was a regression of commit 649448a2a91fbf3e944b2f2e739f4e2292af1df0
"Rename nodeupdate and nodeupdate_single and make them part of the official API"
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Now, the renamed forms of nodeupdate and nodeupdate_single are part of the official API.
As nodeupdate has been used by Minetest Game and in mods despite of not
being part of the official API, we ease the transition by still supporting
it for the 0.4.15 release. After the release, the two functions can be removed.
The removal will not violate the stability promise, as that promise only
includes the official and documented API.
Also, make some formerly global functions local. They most likely haven't
been used by mods, therefore they won't get stubs with deprecation warnings,
hard erroring directly.
|
| |
|
|
|
|
|
|
| |
Original commit by t4im, rebased and developed by paramat.
Fix CONTENT_IGNORE being replaced by falling nodes or causing large
areas of sand to collapse into itself.
Format some conditional code for clarity.
Add and clarify some comments.
|
| | |
|
| |
|
|
|
|
|
| |
The fallback vector is in case 'wallmounted to dir' is nil due
to voxelmanip placing a wallmounted node without resetting a
pre-existing param2 value that is out-of-range for wallmounted.
The fallback vector corresponds to param2 = 0.
|
| | |
|
| |
|
|
|
|
|
| |
This seems very little cost and matches the old behavior more
closely. This will cause some more falling nodes to get added
to falling clusters. With the efficiency of the algorithm, this
really doesn't do much damage.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
This took me a while to figure out. We no longer visit all 9 block
around and with the touched node, but instead visit adjacent plus
self. We then walk -non- recursively through all neigbors and if
they cause a nodeupdate, we just keep walking until it ends. On
the way back we prune the tail.
I've tested this with 8000+ sand nodes. Video result is here:
https://youtu.be/liKKgLefhFQ
Took ~ 10 seconds to process and return to normal.
|
| |
|
|
|
|
|
| |
2016-03-27 15:47:01: ERROR[Main]: ServerError: Lua: Runtime error from mod '*builtin*' in callback luaentity_Step(): Node name is not set or is not a string!
2016-03-27 15:47:01: ERROR[Main]: stack traceback:
2016-03-27 15:47:01: ERROR[Main]: [C]: in function 'add_node'
2016-03-27 15:47:01: ERROR[Main]: /usr/share/minetest/builtin/game/falling.lua:96: in function </usr/share/minetest/builtin/game/falling.lua:43>
|
| |
|
|
|
|
|
|
|
|
|
| |
Commit
65c09a96f41705bb8e75fc5ff4276342be91ed11 "Set acceleration only once in falling node"
has made the acceleration being set only once.
But this has introduced a regression.
Fix #3884.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
Fixes: http://i.imgur.com/arAWw1i.png (middle-right)
|
| | |
|
| | |
|
| | |
|
| |
|
