From 656575b59d4f0d67452cca7409c9064f690f038c Mon Sep 17 00:00:00 2001 From: kwolekr Date: Thu, 7 May 2015 02:34:15 -0400 Subject: NodeResolver: Remove NodeResolveMethod This simplifies NodeResolver logic and makes some interfaces cleaner. --- doc/lua_api.txt | 9 --------- 1 file changed, 9 deletions(-) (limited to 'doc/lua_api.txt') diff --git a/doc/lua_api.txt b/doc/lua_api.txt index c01ef208c..6d1e7e705 100644 --- a/doc/lua_api.txt +++ b/doc/lua_api.txt @@ -2180,15 +2180,6 @@ These functions return the leftover itemstack. * `options` is a table containing the following optional parameters: * If `use_comments` is true and `format` is "lua", the Lua code generated will have (X, Z) * position comments for every X row generated in the schematic data for easier reading. - * If `register_after_load` is true, then `schematic`, if not yet loaded, will be registered - * after loading and persist in memory. - * node_resolve_method can be one of either "none", "direct", or "deferred" (default: "none") - * This sets the way method by with node names are mapped to their content IDs, if loaded: - * "none" performs no node resolution and preserves all node names from the schematic definition - * "direct" performs an immediate lookup of content ID, given all the nodes that have been - * registered up to this point in script execution - * "deferred" pends node resolution until after the script registration phase has ended - * In practice, it is recommended to use "none" in nearly all use cases. ### Misc. * `minetest.get_connected_players()`: returns list of `ObjectRefs` -- cgit v1.2.3