Switch user-facing strings to use the word "block" instead of "node"

awards.lua

@@ -168,14 +168,14 @@ awards.register_achievement("digtron_lava",{
 
 awards.register_achievement("digtron_size10",{
 	title = "Bigtron",
-	description = "Operated a Digtron with 10 or more component nodes.",
+	description = "Operated a Digtron with 10 or more component blocks.",
 	background = "awards_bg_mining.png",
 	icon = "digtron_plate.png^digtron_crate.png",
 })
 
 awards.register_achievement("digtron_size100",{
 	title = "Really Bigtron",
-	description = "Operated a Digtron with 100 or more component nodes.",
+	description = "Operated a Digtron with 100 or more component blocks.",
 	background = "awards_bg_mining.png",
 	icon = "digtron_plate.png^digtron_crate.png", -- TODO: Visually distinguish this from Bigtron
 })
@@ -280,28 +280,28 @@ awards.register_achievement("digtron_1000dirt_dug",{
 
 awards.register_achievement("digtron_1000_dug",{
 	title = "Digtron Miner",
-	description = "Excavate 1000 nodes using Digtrons",
+	description = "Excavate 1000 blocks using Digtrons",
 	background = "awards_bg_mining.png",
 	icon = "digtron_plate.png^default_tool_bronzepick.png^digtron_digger_yb_frame.png",
 })
 
 awards.register_achievement("digtron_10000_dug",{
 	title = "Digtron Expert Miner",
-	description = "Excavate 10,000 nodes using Digtrons",
+	description = "Excavate 10,000 blocks using Digtrons",
 	background = "awards_bg_mining.png",
 	icon = "digtron_plate.png^default_tool_steelpick.png^digtron_digger_yb_frame.png",
 })
 
 awards.register_achievement("digtron_100000_dug",{
 	title = "Digtron Master Miner",
-	description = "Excavate 100,000 nodes using Digtrons",
+	description = "Excavate 100,000 blocks using Digtrons",
 	background = "awards_bg_mining.png",
 	icon = "digtron_plate.png^default_tool_diamondpick.png^digtron_digger_yb_frame.png",
 })
 
 awards.register_achievement("digtron_1000000_dug",{
 	title = "DIGTRON MEGAMINER",
-	description = "Excavate over a million nodes using Digtrons!",
+	description = "Excavate over a million blocks using Digtrons!",
 	background = "awards_bg_mining.png",
 	icon = "digtron_plate.png^default_tool_mesepick.png^digtron_digger_yb_frame.png",
 })
@@ -364,14 +364,14 @@ awards.register_achievement("digtron_100gold_dug",{
 
 awards.register_achievement("digtron_1000_built",{
 	title = "Constructive Digging",
-	description = "Build 1,000 nodes with a Digtron",
+	description = "Build 1,000 blocks with a Digtron",
 	background = "awards_bg_mining.png",
 	icon = "digtron_plate.png^digtron_builder.png",
 })
 
 awards.register_achievement("digtron_10000_built",{
 	title = "Highly Constructive Digging",
-	description = "Build 10,000 nodes with a Digtron",
+	description = "Build 10,000 blocks with a Digtron",
 	background = "awards_bg_mining.png",
 	icon = "digtron_plate.png^digtron_axel_side.png^[transformR90^digtron_builder.png",
 })

doc.lua

@@ -1,31 +1,31 @@
 digtron.doc = {}
 
-digtron.doc.core_longdesc = "A crafting component used in the manufacture of all Digtron node types."
+digtron.doc.core_longdesc = "A crafting component used in the manufacture of all Digtron block types."
 digtron.doc.core_usagehelp = "Place the Digtron Core in the center of the crafting grid. All Digtron recipes consist of arranging various other materials around the central Digtron Core."
 
 --------------------------------------------------------------------
 
-digtron.doc.builder_longdesc = "A 'builder' module for a Digtron. By itself it does nothing, but as part of a Digtron it is used to construct user-defined nodes."
-digtron.doc.builder_usagehelp = "A builder head is the most complex component of this system. It has period and offset properties, and also an inventory slot where you \"program\" it by placing an example of the node type that you want it to build.\n\n" ..
+digtron.doc.builder_longdesc = "A 'builder' module for a Digtron. By itself it does nothing, but as part of a Digtron it is used to construct user-defined blocks."
+digtron.doc.builder_usagehelp = "A builder head is the most complex component of this system. It has period and offset properties, and also an inventory slot where you \"program\" it by placing an example of the block type that you want it to build.\n\n" ..
 'When the "Save & Show" button is clicked the properties for period and offset will be saved, and markers will briefly be shown to indicate where the nearest spots corresponding to those values are. The builder will build its output at those locations provided it is moving along the matching axis.\n\n' ..
 'The "output" side of a builder is the side with a black crosshair on it.\n\n' ..
-'Builders also have a "facing" setting. If you haven\'t memorized the meaning of the 24 facing values yet, builder heads have a helpful "Read & Save" button to fill this value in for you. Simply build a temporary instance of the node in the output location in front of the builder, adjust it to the orientation you want using the screwdriver tool, and then when you click the "Read & Save" button the node\'s facing will be read and saved.'
+'Builders also have a "facing" setting. If you haven\'t memorized the meaning of the 24 facing values yet, builder heads have a helpful "Read & Save" button to fill this value in for you. Simply build a temporary instance of the block in the output location in front of the builder, adjust it to the orientation you want using the screwdriver tool, and then when you click the "Read & Save" button the block\'s facing will be read and saved.'
 
 --------------------------------------------------------------------
 
 digtron.doc.inventory_longdesc = "Stores building materials for use by builder heads and materials dug up by digger heads."
 digtron.doc.inventory_usagehelp = "Inventory modules have the same capacity as a chest. They're used both for storing the products of the digger heads and as the source of materials used by the builder heads. A digging machine whose builder heads are laying down cobble can automatically self-replenish in this way, but note that an inventory module is still required as buffer space even if the digger heads produced everything needed by the builder heads in a given cycle.\n\n"..
-"Inventory modules are not required for a digging-only machine. If there's not enough storage space to hold the materials produced by the digging heads the excess material will be ejected out the back of the control node. They're handy for accumulating ores and other building materials, though.\n\n"..
+"Inventory modules are not required for a digging-only machine. If there's not enough storage space to hold the materials produced by the digging heads the excess material will be ejected out the back of the control block. They're handy for accumulating ores and other building materials, though.\n\n"..
 "Digging machines can have multiple inventory modules added to expand their capacity."
 
 digtron.doc.fuelstore_longdesc = "Stores fuel to run a Digtron"
 digtron.doc.fuelstore_usagehelp = "Digtrons have an appetite. Build operations and dig operations require a certain amount of fuel, and that fuel comes from fuel hopper modules. Note that movement does not require fuel, only digging and building.\n\n"..
 "When a control unit is triggered, it will tally up how much fuel is required for the next cycle and then burn items from the fuel hopper until a sufficient amount of heat has been generated to power the operation. Any leftover heat will be retained by the control unit for use in the next cycle; this is the \"heat remaining in controller furnace\". This means you don't have to worry too much about what kinds of fuel you put in the hopper, none will be wasted (unless you dig away a control unit with some heat remaining in it, that heat does get wasted).\n\n" ..
 "The fuel costs for digging and building can be configured in the init.lua file. By default using one lump of coal as fuel a digtron can:\n"..
-"\tBuild 40 nodes\n"..
-"\tDig 40 stone nodes\n"..
-"\tDig 60 wood nodes\n"..
-"\tDig 80 dirt or sand nodes"
+"\tBuild 40 blocks\n"..
+"\tDig 40 stone blocks\n"..
+"\tDig 60 wood blocks\n"..
+"\tDig 80 dirt or sand blocks"
 
 digtron.doc.combined_storage_longdesc = "Stores fuel for a Digtron and also has an inventory for building materials"
 digtron.doc.combined_storage_usagehelp = "For smaller jobs the two dedicated modules may simply be too much of a good thing, wasting precious Digtron space to give unneeded capacity. The combined storage module is the best of both worlds, splitting its internal space between building material inventory and fuel storage. It has 3/4 building material capacity and 1/4 fuel storage capacity."
@@ -37,14 +37,14 @@ digtron.doc.empty_crate_usagehelp = "Digtrons can be pushed around and rotated,
 "Place an empty Digtron crate next to a Digtron and right-click it to pack the Digtron (and all its inventory and settings) into the crate. You can then collect the crate, bring it somewhere else, build the crate, and then unpack the Digtron from it again. The Digtron will appear in the same relative location and orientation to the crate as when it was packed away inside it."
 
 digtron.doc.loaded_crate_longdesc = "A crate containing a Digtron array"
-digtron.doc.loaded_crate_usagehelp = "This crate contains a Digtron assembly that was stored in it earlier. Place it somewhere and right-click on it to access the label text that was applied to it. There's also a button that causes it to display the shape the deployed Digtron would take if you unpacked the crate, marking unbuildable nodes with a warning marker. And finally there's a button to actually deploy the Digtron, replacing this loaded crate with an empty that can be reused later."
+digtron.doc.loaded_crate_usagehelp = "This crate contains a Digtron assembly that was stored in it earlier. Place it somewhere and right-click on it to access the label text that was applied to it. There's also a button that causes it to display the shape the deployed Digtron would take if you unpacked the crate, marking unbuildable blocks with a warning marker. And finally there's a button to actually deploy the Digtron, replacing this loaded crate with an empty that can be reused later."
 
 ----------------------------------------------------------------------
 
 digtron.doc.controller_longdesc = "A basic controller to make a Digtron array move and operate."
 digtron.doc.controller_usagehelp = "Right-click on this module to make the digging machine go one step. The digging machine will go in the direction that the control module is oriented.\n\n" ..
 "A control module can only trigger once per second. Gives you time to enjoy the scenery and smell the flowers (or their mulched remains, at any rate).\n\n" ..
-"If you're standing within the digging machine's volume, or in a node adjacent to it, you will be pulled along with the machine when it moves."
+"If you're standing within the digging machine's volume, or in a block adjacent to it, you will be pulled along with the machine when it moves."
 
 digtron.doc.auto_controller_longdesc = "A more sophisticated controller that includes the ability to set the number of cycles it will run for, as well as diagonal movement."
 digtron.doc.auto_controller_usagehelp = "An Auto-control module can be set to run for an arbitrary number of cycles. Once it's running, right-click on it again to interrupt its rampage. If anything interrupts it - the player's click, an undiggable obstruction, running out of fuel - it will remember the number of remaining cycles so that you can fix the problem and set it running again to complete the original plan.\n\n" ..
@@ -61,14 +61,14 @@ digtron.doc.axle_usagehelp = "This magical module can rotate a Digtron array in
 ---------------------------------------------------------------------
 
 digtron.doc.digger_longdesc = "A standard Digtron digger head"
-digtron.doc.digger_usagehelp = "Facing of a digger head is significant; it will excavate material from the node on the spinning grinder wheel face of the digger head. Generally speaking, you'll want these to face forward - though having them aimed to the sides can also be useful."
+digtron.doc.digger_usagehelp = "Facing of a digger head is significant; it will excavate material from the block on the spinning grinder wheel face of the digger head. Generally speaking, you'll want these to face forward - though having them aimed to the sides can also be useful."
 
 digtron.doc.dual_digger_longdesc = "Two standard Digtron digger heads merged at 90 degrees to each other"
-digtron.doc.dual_digger_usagehelp = "This digger head is mainly of use when you want to build a Digtron capable of digging diagonal paths. A normal one-direction dig head would be unable to clear nodes in both of the directions it would be called upon to move, resulting in a stuck Digtron.\n\n" ..
+digtron.doc.dual_digger_usagehelp = "This digger head is mainly of use when you want to build a Digtron capable of digging diagonal paths. A normal one-direction dig head would be unable to clear blocks in both of the directions it would be called upon to move, resulting in a stuck Digtron.\n\n" ..
 "One can also make use of dual dig heads to simplify the size and layout of a Digtron, though this is generally not of practical use."
 
 digtron.doc.dual_soft_digger_longdesc = "Two standard soft-material Digtron digger heads merged at 90 degrees to each other"
-digtron.doc.dual_soft_digger_usagehelp = "This digger head is mainly of use when you want to build a Digtron capable of digging diagonal paths. A normal one-direction dig head would be unable to clear nodes in both of the directions it would be called upon to move, resulting in a stuck Digtron.\n\n" ..
+digtron.doc.dual_soft_digger_usagehelp = "This digger head is mainly of use when you want to build a Digtron capable of digging diagonal paths. A normal one-direction dig head would be unable to clear blocks in both of the directions it would be called upon to move, resulting in a stuck Digtron.\n\n" ..
 "Like a normal single-direction soft digger head, this digger only excavates material belonging to groups softer than stone" ..
 "One can make use of dual dig heads to simplify the size and layout of a Digtron, though this is generally not of practical use."
 
@@ -79,14 +79,14 @@ digtron.doc.intermittent_soft_digger_longdesc = "A standard soft-material Digtro
 digtron.doc.intermittent_soft_digger_usagehelp = "This is a standard soft-material digger head capable of digging any material, but it will only trigger periodically as the Digtron moves. This can be useful for punching regularly-spaced holes in a tunnel wall, for example."
 
 digtron.doc.soft_digger_longdesc = "A Digtron digger head that only excavates soft materials"
-digtron.doc.soft_digger_usagehelp = 'This specialized digger head is designed to excavate only softer material such as sand or gravel. In technical terms, this digger digs nodes belonging to the "crumbly", "choppy", "snappy", "oddly_diggable_by_hand" and "fleshy" groups.\n\n'..
-"The intended purpose of this digger is to be aimed at the ceiling or walls of a tunnel being dug, making spaces to allow shoring nodes to be inserted into unstable roofs but leaving the wall alone if it's composed of a more stable material.\n\n" ..
+digtron.doc.soft_digger_usagehelp = 'This specialized digger head is designed to excavate only softer material such as sand or gravel. In technical terms, this digger digs blocks belonging to the "crumbly", "choppy", "snappy", "oddly_diggable_by_hand" and "fleshy" groups.\n\n'..
+"The intended purpose of this digger is to be aimed at the ceiling or walls of a tunnel being dug, making spaces to allow shoring blocks to be inserted into unstable roofs but leaving the wall alone if it's composed of a more stable material.\n\n" ..
 "It can also serve as part of a lawnmower or tree-harvester."
 
 ---------------------------------------------------------------------
 
 digtron.doc.structure_longdesc = "Structural component for a Digtron array"
-digtron.doc.structure_usagehelp = "These nodes allow otherwise-disconnected sections of digtron nodes to be linked together. They are not usually necessary for simple diggers but more elaborate builder arrays might have builder nodes that can't be placed directly adjacent to other digtron nodes and these nodes can serve to keep them connected to the controller.\n\n" ..
+digtron.doc.structure_usagehelp = "These blocks allow otherwise-disconnected sections of digtron blocks to be linked together. They are not usually necessary for simple diggers but more elaborate builder arrays might have builder blocks that can't be placed directly adjacent to other digtron blocks and these blocks can serve to keep them connected to the controller.\n\n" ..
 "They may also be used for providing additional traction if your digtron array is very tall compared to the terrain surface that it's touching.\n\n" ..
 "You can also use them decoratively, or to build a platform to stand on as you ride your mighty mechanical leviathan through the landscape."
 

init.lua

@@ -174,7 +174,7 @@ minetest.register_lbm({
 			"button_exit[2.2,0.5;1,0.1;execute;Set &\nExecute]" ..
 			"tooltip[execute;Begins executing the given number of cycles]" ..
 			"field[0.5,2.0;1,0.1;slope;Slope;${slope}]" ..
-			"tooltip[slope;For diagonal digging. After every X nodes the auto controller moves forward, the controller will add an additional cycle moving the digtron laterally in the direction of the arrows on the side of this controller. Set to 0 for no lateral digging.]" ..
+			"tooltip[slope;For diagonal digging. After every X blocks the auto controller moves forward, the controller will add an additional cycle moving the digtron laterally in the direction of the arrows on the side of this controller. Set to 0 for no lateral digging.]" ..
 			"field[1.5,2.0;1,0.1;offset;Offset;${offset}]" ..
 			"tooltip[offset;Sets the offset of the lateral motion defined in the Slope field. Note: this offset is relative to the controller's location. The controller will move down when it reaches the indicated point.]" ..
 			"field[2.5,2.0;1,0.1;period;Delay;${period}]" ..

node_builders.lua

@@ -49,18 +49,18 @@ minetest.register_node("digtron:builder", {
 			default.gui_bg_img ..
 			default.gui_slots ..
 			"list[current_name;main;0.5,0;1,1;]" ..
---			"tooltip[main;Builder will build the type of node in this slot. Note that only one item needs to be placed here, to 'program' it. The builder will draw construction materials from the central inventory when building.]" ..
-			"label[0.5,0.8;Node to build]" ..
+--			"tooltip[main;Builder will build the type of block in this slot. Note that only one item needs to be placed here, to 'program' it. The builder will draw construction materials from the central inventory when building.]" ..
+			"label[0.5,0.8;Block to build]" ..
 			"field[2.5,0.8;1,0.1;period;Periodicity;${period}]" ..
 			"tooltip[period;Builder will build once every n steps. These steps are globally aligned, so all builders with the same period and offset will build on the same location.]" ..
 			"field[3.5,0.8;1,0.1;offset;Offset;${offset}]" ..
-			"tooltip[offset;Offsets the start of periodicity counting by this amount. For example, a builder with period 2 and offset 0 builds every even-numbered node and one with period 2 and offset 1 builds every odd-numbered node.]" ..
+			"tooltip[offset;Offsets the start of periodicity counting by this amount. For example, a builder with period 2 and offset 0 builds every even-numbered block and one with period 2 and offset 1 builds every odd-numbered block.]" ..
 			"button_exit[4.2,0.5;1,0.1;set;Save &\nShow]" ..
 			"tooltip[set;Saves settings]" ..
 			"field[5.7,0.8;1,0.1;build_facing;Facing;${build_facing}]" ..
-			"tooltip[build_facing;Value from 0-23. Not all node types make use of this. Use the 'Read & Save' button to copy the facing of the node currently in the builder output location]" ..
+			"tooltip[build_facing;Value from 0-23. Not all block types make use of this. Use the 'Read & Save' button to copy the facing of the block currently in the builder output location]" ..
 			"button_exit[6.4,0.5;1,0.1;read;Read &\nSave]" ..
-			"tooltip[read;Reads the facing of the node currently in the build location, then saves all settings]" ..
+			"tooltip[read;Reads the facing of the block currently in the build location, then saves all settings]" ..
 			"list[current_player;main;0,1.3;8,1;]" ..
 			"list[current_player;main;0,1.3;8,1;]" ..
 			default.get_hotbar_bg(0,1.3) ..

node_controllers.lua

@@ -82,7 +82,7 @@ local auto_formspec = "size[3.5,2]" ..
 	"button_exit[2.2,0.5;1,0.1;execute;Set &\nExecute]" ..
 	"tooltip[execute;Begins executing the given number of cycles]" ..
 	"field[0.5,2.0;1,0.1;slope;Slope;${slope}]" ..
-	"tooltip[slope;For diagonal digging. After every X nodes the auto controller moves forward, the controller will add an additional cycle moving the digtron laterally in the direction of the arrows on the side of this controller. Set to 0 for no lateral digging.]" ..
+	"tooltip[slope;For diagonal digging. After every X blocks the auto controller moves forward, the controller will add an additional cycle moving the digtron laterally in the direction of the arrows on the side of this controller. Set to 0 for no lateral digging.]" ..
 	"field[1.5,2.0;1,0.1;offset;Offset;${offset}]" ..
 	"tooltip[offset;Sets the offset of the lateral motion defined in the Slope field. Note: this offset is relative to the controller's location. The controller will move down when it reaches the indicated point.]" ..
 	"field[2.5,2.0;1,0.1;period;Delay;${period}]" ..

node_crate.lua

@@ -24,7 +24,7 @@ minetest.register_node("digtron:empty_crate", {
 		if layout.contains_protected_node then
 			local meta = minetest.get_meta(pos)
 			minetest.sound_play("buzzer", {gain=0.5, pos=pos})
-			meta:set_string("infotext", "Digtron can't be packaged, it contains protected nodes")
+			meta:set_string("infotext", "Digtron can't be packaged, it contains protected blocks")
 			-- no stealing other peoples' digtrons
 			return
 		end
@@ -54,8 +54,8 @@ local loaded_formspec =  "size[4,1.5]" ..
 	"field[0.3,0.5;4,0.5;title;Digtron Name;${title}]" ..
 	"button_exit[0.5,1.2;1,0.1;save;Save\nTitle]" ..
 	"tooltip[save;Saves the title of this Digtron]" ..
-	"button_exit[1.5,1.2;1,0.1;show;Show\nNodes]" ..
-	"tooltip[save;Shows what nodes the packed Digtron will occupy if unpacked]" ..
+	"button_exit[1.5,1.2;1,0.1;show;Show\nBlocks]" ..
+	"tooltip[save;Shows which blocks the packed Digtron will occupy if unpacked]" ..
 	"button_exit[2.5,1.2;1,0.1;unpack;Unpack]" ..
 	"tooltip[unpack;Attempts to unpack the Digtron on this location]"
 
@@ -121,7 +121,7 @@ minetest.register_node("digtron:loaded_crate", {
 		end
 		
 		if protected_node then
-			meta:set_string("infotext", meta:get_string("title") .. "\nUnable to deploy Digtron due to protected nodes in target area")
+			meta:set_string("infotext", meta:get_string("title") .. "\nUnable to deploy Digtron due to protected blocks in target area")
 			minetest.sound_play("buzzer", {gain=0.5, pos=pos})
 			return
 		end

node_diggers.lua

@@ -31,7 +31,7 @@ local intermittent_on_construct = function(pos)
 		"field[0.5,0.8;1,0.1;period;Periodicity;${period}]" ..
 		"tooltip[period;Digger will dig once every n steps. These steps are globally aligned, all diggers with the same period and offset will dig on the same location.]" ..
 		"field[1.5,0.8;1,0.1;offset;Offset;${offset}]" ..
-		"tooltip[offset;Offsets the start of periodicity counting by this amount. For example, a digger with period 2 and offset 0 digs every even-numbered node and one with period 2 and offset 1 digs every odd-numbered node.]" ..
+		"tooltip[offset;Offsets the start of periodicity counting by this amount. For example, a digger with period 2 and offset 0 digs every even-numbered block and one with period 2 and offset 1 digs every odd-numbered block.]" ..
 		"button_exit[2.2,0.5;1,0.1;set;Save]" ..
 		"tooltip[set;Saves settings]"
 	)

util_execute_cycle.lua

@@ -58,7 +58,7 @@ local function neighbour_test(layout, status_text)
 	if layout.traction * digtron.traction_factor < table.getn(layout.all) then
 		-- digtrons can't fly
 		minetest.sound_play("squeal", {gain=1.0, pos=layout.controller})
-		return string.format("Digtron has %d nodes but only enough traction to move %d nodes.\n", table.getn(layout.all), layout.traction * digtron.traction_factor)
+		return string.format("Digtron has %d blocks but only enough traction to move %d blocks.\n", table.getn(layout.all), layout.traction * digtron.traction_factor)
 			 .. status_text, 2
 	end