summaryrefslogtreecommitdiff
path: root/builtin/game/falling.lua
Commit message (Collapse)AuthorAge
* Automatic item and node colorization (#5640)Dániel Juhász2018-06-03
| | | | | | | | | | | | | | | | | * 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
* Save metainfo for falling nodesVladislav Tsendrovskii2017-03-11
|
* Add minetest.spawn_falling_node(pos) (#5339)zaoqi2017-03-04
| | | | | | | | * Add minetest.spawn_falling_node(pos) * lua_api.txt: Add minetest.spawn_falling_node(pos) * Update minetest.spawn_falling_node(pos)
* Fixes for colorwallmounted and colorfacedir nodesDániel Juhász2017-02-18
| | | | | | Correct node placement prediction for attached colorwallmounted nodes. Correct placement direction for colorfacedir and colorwallmounted nodes. Correct detatch mechanism for attached colorwallmounted nodes.
* builtin/.../falling.lua: Avoid crash when hitting unknown nodessfan52017-01-09
|
* Builtin/../falling.lua: Avoid crash when object pos over limitparamat2016-12-21
| | | | | If the object pos is over limit, 'add entity' will not add an entity, causing 'obj' to be nil.
* Introduce builtin_shared and use it to fix #4778est312016-11-16
| | | | | | | | | | | 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"
* Rename nodeupdate and nodeupdate_single and make them part of the official APIest312016-11-14
| | | | | | | | | | | | | | | 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.
* Builtin/../falling: Fix bugs caused by 'ignore' nodesparamat2016-11-07
| | | | | | | | 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.
* Builtin/../falling.lua: Code optimisationtenplus12016-10-14
|
* Builtin/falling: Add fallback vector in case of nil 'wallmounted to dir'paramat2016-10-03
| | | | | | | 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.
* Add on_punchnode callbackWayward One2016-05-17
|
* falling: walk 4 additional diagonally down directions.Auke Kok2016-04-20
| | | | | | | 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.
* Convert nodeupdate to non-recursiveAuke Kok2016-04-11
| | | | | | | | | | | | | | 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.
* stop falling.lua errortenplus12016-03-29
| | | | | | | 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>
* Falling: Set acceleration on step againRui2016-03-25
| | | | | | | | | | | 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.
* Builtin/game/falling: Re-add comma removed by recent commitparamat2016-03-19
|
* Set acceleration only once in falling nodeRui9142016-03-19
|
* Minor tweaks __builtin:falling_nodeRui2015-09-01
|
* Fix some undeclared global variablesCraig Davison2014-11-26
|
* Use round if falling node is misplacedSmallJoker2014-09-28
| | | | Fixes: http://i.imgur.com/arAWw1i.png (middle-right)
* Remove buildable_to nodes without dropping item when replaced by a falling nodeCasimir2014-08-22
|
* Allow custom liquids to have dropssfan52014-06-08
|
* Use "core" namespace internallyShadowNinja2014-05-08
|
* Organize builtin into subdirectoriesShadowNinja2014-05-07