minetest-mods
/
technic
mirror of https://github.com/minetest-mods/technic.git
1
0
Fork 1
Code Issues Releases Wiki Activity
technic/technic/machines/HV/quarry.lua

177 lines
6.3 KiB
Lua
Raw Normal View History

Partial rewrite
2013-07-17 21:34:35 +02:00
Add support for translations via intllib
2013-10-30 18:45:32 +01:00
local S = technic.getter
Partial rewrite
2013-07-17 21:34:35 +02:00
minetest.register_craft({
recipe = {
Rework some recipes to use more varied ingredients
2014-07-07 22:48:38 +02:00
{"technic:carbon_plate", "pipeworks:filter", "technic:composite_plate"},
Consistently use cable in electric machine recipes All electric machine recipes now include cable of the appropriate tier as the bottom-middle ingredient, immediately below the casing ingredient. Many LV machines were using a copper ingot in that location.
2014-07-06 19:45:16 +02:00
{"technic:motor", "technic:machine_casing", "technic:diamond_drill_head"},
{"technic:carbon_steel_block", "technic:hv_cable0", "technic:carbon_steel_block"}},
Partial rewrite
2013-07-17 21:34:35 +02:00
output = "technic:quarry",
})
local quarry_dig_above_nodes = 3 -- How far above the quarry we will dig nodes
local quarry_max_depth = 100
In quarry, skip past undiggable nodes The quarry used to get stuck when it encountered an undiggable node. Change it to skip past that node, digging whatever later stuff it can. Necessarily, the current digging position becomes semantically-significant state: it is no longer sufficient to search the quarry cuboid from the top on each iteration. The current digging height is reported in the quarry's interaction form, and can be reset to the top using a button on the form. Where there is a non-air node within the quarry directly above the next node to dig, it blocks the quarry's access to that node, even if everything involved is diggable. Thus an undiggable node casts a shadow of undug nodes below it. Resolving undiggability of a node is a major reason to use the restart button.
2014-08-17 20:19:11 +02:00
local quarry_demand = 10000
Partial rewrite
2013-07-17 21:34:35 +02:00
Better quarry control dialog The size configuration is no longer cleared when exiting the dialog with <esc>. The enable/disable toggle button now indicates the current state. The name of the toggle button now varies according to state, so that pressing the button multiple times in one state (which can arise due to lag making the user unsure about whether the first press registered) only makes the state change that the user requested, rather than toggling repeatedly.
2014-05-23 23:37:44 +02:00
local function set_quarry_formspec(meta)
In quarry, skip past undiggable nodes The quarry used to get stuck when it encountered an undiggable node. Change it to skip past that node, digging whatever later stuff it can. Necessarily, the current digging position becomes semantically-significant state: it is no longer sufficient to search the quarry cuboid from the top on each iteration. The current digging height is reported in the quarry's interaction form, and can be reset to the top using a button on the form. Where there is a non-air node within the quarry directly above the next node to dig, it blocks the quarry's access to that node, even if everything involved is diggable. Thus an undiggable node casts a shadow of undug nodes below it. Resolving undiggability of a node is a major reason to use the restart button.
2014-08-17 20:19:11 +02:00
local radius = meta:get_int("size")
local formspec = "size[6,2.5]"..
"item_image[0,0;1,1;technic:quarry]"..
"label[1,0;"..S("%s Quarry"):format("HV").."]"..
"field[0.3,1.5;2,1;size;"..S("Radius:")..";"..radius.."]"
Better quarry control dialog The size configuration is no longer cleared when exiting the dialog with <esc>. The enable/disable toggle button now indicates the current state. The name of the toggle button now varies according to state, so that pressing the button multiple times in one state (which can arise due to lag making the user unsure about whether the first press registered) only makes the state change that the user requested, rather than toggling repeatedly.
2014-05-23 23:37:44 +02:00
if meta:get_int("enabled") == 0 then
In quarry, skip past undiggable nodes The quarry used to get stuck when it encountered an undiggable node. Change it to skip past that node, digging whatever later stuff it can. Necessarily, the current digging position becomes semantically-significant state: it is no longer sufficient to search the quarry cuboid from the top on each iteration. The current digging height is reported in the quarry's interaction form, and can be reset to the top using a button on the form. Where there is a non-air node within the quarry directly above the next node to dig, it blocks the quarry's access to that node, even if everything involved is diggable. Thus an undiggable node casts a shadow of undug nodes below it. Resolving undiggability of a node is a major reason to use the restart button.
2014-08-17 20:19:11 +02:00
formspec = formspec.."button[4,1.2;2,1;enable;"..S("Disabled").."]"
Better quarry control dialog The size configuration is no longer cleared when exiting the dialog with <esc>. The enable/disable toggle button now indicates the current state. The name of the toggle button now varies according to state, so that pressing the button multiple times in one state (which can arise due to lag making the user unsure about whether the first press registered) only makes the state change that the user requested, rather than toggling repeatedly.
2014-05-23 23:37:44 +02:00
else
In quarry, skip past undiggable nodes The quarry used to get stuck when it encountered an undiggable node. Change it to skip past that node, digging whatever later stuff it can. Necessarily, the current digging position becomes semantically-significant state: it is no longer sufficient to search the quarry cuboid from the top on each iteration. The current digging height is reported in the quarry's interaction form, and can be reset to the top using a button on the form. Where there is a non-air node within the quarry directly above the next node to dig, it blocks the quarry's access to that node, even if everything involved is diggable. Thus an undiggable node casts a shadow of undug nodes below it. Resolving undiggability of a node is a major reason to use the restart button.
2014-08-17 20:19:11 +02:00
formspec = formspec.."button[4,1.2;2,1;disable;"..S("Enabled").."]"
Better quarry control dialog The size configuration is no longer cleared when exiting the dialog with <esc>. The enable/disable toggle button now indicates the current state. The name of the toggle button now varies according to state, so that pressing the button multiple times in one state (which can arise due to lag making the user unsure about whether the first press registered) only makes the state change that the user requested, rather than toggling repeatedly.
2014-05-23 23:37:44 +02:00
end
In quarry, skip past undiggable nodes The quarry used to get stuck when it encountered an undiggable node. Change it to skip past that node, digging whatever later stuff it can. Necessarily, the current digging position becomes semantically-significant state: it is no longer sufficient to search the quarry cuboid from the top on each iteration. The current digging height is reported in the quarry's interaction form, and can be reset to the top using a button on the form. Where there is a non-air node within the quarry directly above the next node to dig, it blocks the quarry's access to that node, even if everything involved is diggable. Thus an undiggable node casts a shadow of undug nodes below it. Resolving undiggability of a node is a major reason to use the restart button.
2014-08-17 20:19:11 +02:00
local diameter = radius*2 + 1
local nd = meta:get_int("dug")
local rel_y = quarry_dig_above_nodes - math.floor(nd / (diameter*diameter))
formspec = formspec.."label[0,2;"..minetest.formspec_escape(
nd == 0 and S("Digging not started") or
(rel_y < -quarry_max_depth and S("Digging finished") or
S("Digging %d m "..(rel_y > 0 and "above" or "below").." machine")
:format(math.abs(rel_y)))
).."]"
formspec = formspec.."button[4,2;2,1;restart;"..S("Restart").."]"
Better quarry control dialog The size configuration is no longer cleared when exiting the dialog with <esc>. The enable/disable toggle button now indicates the current state. The name of the toggle button now varies according to state, so that pressing the button multiple times in one state (which can arise due to lag making the user unsure about whether the first press registered) only makes the state change that the user requested, rather than toggling repeatedly.
2014-05-23 23:37:44 +02:00
meta:set_string("formspec", formspec)
Partial rewrite
2013-07-17 21:34:35 +02:00
end
In quarry, skip past undiggable nodes The quarry used to get stuck when it encountered an undiggable node. Change it to skip past that node, digging whatever later stuff it can. Necessarily, the current digging position becomes semantically-significant state: it is no longer sufficient to search the quarry cuboid from the top on each iteration. The current digging height is reported in the quarry's interaction form, and can be reset to the top using a button on the form. Where there is a non-air node within the quarry directly above the next node to dig, it blocks the quarry's access to that node, even if everything involved is diggable. Thus an undiggable node casts a shadow of undug nodes below it. Resolving undiggability of a node is a major reason to use the restart button.
2014-08-17 20:19:11 +02:00
local function set_quarry_demand(meta)
local radius = meta:get_int("size")
local diameter = radius*2 + 1
local machine_name = S("%s Quarry"):format("HV")
if meta:get_int("enabled") == 0 then
meta:set_string("infotext", S("%s Disabled"):format(machine_name))
meta:set_int("HV_EU_demand", 0)
elseif meta:get_int("dug") == diameter*diameter * (quarry_dig_above_nodes+1+quarry_max_depth) then
meta:set_string("infotext", S("%s Finished"):format(machine_name))
meta:set_int("HV_EU_demand", 0)
else
meta:set_string("infotext", S(meta:get_int("HV_EU_input") >= quarry_demand and "%s Active" or "%s Unpowered"):format(machine_name))
meta:set_int("HV_EU_demand", quarry_demand)
Partial rewrite
2013-07-17 21:34:35 +02:00
end
end
In quarry, skip past undiggable nodes The quarry used to get stuck when it encountered an undiggable node. Change it to skip past that node, digging whatever later stuff it can. Necessarily, the current digging position becomes semantically-significant state: it is no longer sufficient to search the quarry cuboid from the top on each iteration. The current digging height is reported in the quarry's interaction form, and can be reset to the top using a button on the form. Where there is a non-air node within the quarry directly above the next node to dig, it blocks the quarry's access to that node, even if everything involved is diggable. Thus an undiggable node casts a shadow of undug nodes below it. Resolving undiggability of a node is a major reason to use the restart button.
2014-08-17 20:19:11 +02:00
local function quarry_receive_fields(pos, formname, fields, sender)
Partial rewrite
2013-07-17 21:34:35 +02:00
local meta = minetest.get_meta(pos)
In quarry, skip past undiggable nodes The quarry used to get stuck when it encountered an undiggable node. Change it to skip past that node, digging whatever later stuff it can. Necessarily, the current digging position becomes semantically-significant state: it is no longer sufficient to search the quarry cuboid from the top on each iteration. The current digging height is reported in the quarry's interaction form, and can be reset to the top using a button on the form. Where there is a non-air node within the quarry directly above the next node to dig, it blocks the quarry's access to that node, even if everything involved is diggable. Thus an undiggable node casts a shadow of undug nodes below it. Resolving undiggability of a node is a major reason to use the restart button.
2014-08-17 20:19:11 +02:00
if fields.size and string.find(fields.size, "^[0-9]+$") then
local size = tonumber(fields.size)
if size >= 2 and size <= 8 and size ~= meta:get_int("size") then
meta:set_int("size", size)
meta:set_int("dug", 0)
Partial rewrite
2013-07-17 21:34:35 +02:00
end
end
In quarry, skip past undiggable nodes The quarry used to get stuck when it encountered an undiggable node. Change it to skip past that node, digging whatever later stuff it can. Necessarily, the current digging position becomes semantically-significant state: it is no longer sufficient to search the quarry cuboid from the top on each iteration. The current digging height is reported in the quarry's interaction form, and can be reset to the top using a button on the form. Where there is a non-air node within the quarry directly above the next node to dig, it blocks the quarry's access to that node, even if everything involved is diggable. Thus an undiggable node casts a shadow of undug nodes below it. Resolving undiggability of a node is a major reason to use the restart button.
2014-08-17 20:19:11 +02:00
if fields.enable then meta:set_int("enabled", 1) end
if fields.disable then meta:set_int("enabled", 0) end
if fields.restart then meta:set_int("dug", 0) end
set_quarry_formspec(meta)
set_quarry_demand(meta)
Partial rewrite
2013-07-17 21:34:35 +02:00
end
In quarry, skip past undiggable nodes The quarry used to get stuck when it encountered an undiggable node. Change it to skip past that node, digging whatever later stuff it can. Necessarily, the current digging position becomes semantically-significant state: it is no longer sufficient to search the quarry cuboid from the top on each iteration. The current digging height is reported in the quarry's interaction form, and can be reset to the top using a button on the form. Where there is a non-air node within the quarry directly above the next node to dig, it blocks the quarry's access to that node, even if everything involved is diggable. Thus an undiggable node casts a shadow of undug nodes below it. Resolving undiggability of a node is a major reason to use the restart button.
2014-08-17 20:19:11 +02:00
local function quarry_run(pos, node)
Make switching station run all machines it is connected to, including those in unloaded blocks.
2014-07-11 11:00:46 +02:00
local meta = minetest.get_meta(pos)
In quarry, skip past undiggable nodes The quarry used to get stuck when it encountered an undiggable node. Change it to skip past that node, digging whatever later stuff it can. Necessarily, the current digging position becomes semantically-significant state: it is no longer sufficient to search the quarry cuboid from the top on each iteration. The current digging height is reported in the quarry's interaction form, and can be reset to the top using a button on the form. Where there is a non-air node within the quarry directly above the next node to dig, it blocks the quarry's access to that node, even if everything involved is diggable. Thus an undiggable node casts a shadow of undug nodes below it. Resolving undiggability of a node is a major reason to use the restart button.
2014-08-17 20:19:11 +02:00
if meta:get_int("enabled") and meta:get_int("HV_EU_input") >= quarry_demand then
local pdir = minetest.facedir_to_dir(node.param2)
local qdir = pdir.x == 1 and vector.new(0,0,-1) or
(pdir.z == -1 and vector.new(-1,0,0) or
(pdir.x == -1 and vector.new(0,0,1) or
vector.new(1,0,0)))
local radius = meta:get_int("size")
local diameter = radius*2 + 1
local startpos = vector.add(vector.add(vector.add(pos,
vector.new(0, quarry_dig_above_nodes, 0)),
pdir),
vector.multiply(qdir, -radius))
local endpos = vector.add(vector.add(vector.add(startpos,
vector.new(0, -quarry_dig_above_nodes-quarry_max_depth, 0)),
vector.multiply(pdir, diameter-1)),
vector.multiply(qdir, diameter-1))
local vm = VoxelManip()
local minpos, maxpos = vm:read_from_map(startpos, endpos)
local area = VoxelArea:new({MinEdge=minpos, MaxEdge=maxpos})
local data = vm:get_data()
local c_air = minetest.get_content_id("air")
local owner = meta:get_string("owner")
local nd = meta:get_int("dug")
while nd ~= diameter*diameter * (quarry_dig_above_nodes+1+quarry_max_depth) do
local ry = math.floor(nd / (diameter*diameter))
local ndl = nd % (diameter*diameter)
if ry % 2 == 1 then
ndl = diameter*diameter - 1 - ndl
end
local rq = math.floor(ndl / diameter)
local rp = ndl % diameter
if rq % 2 == 1 then rp = diameter - 1 - rp end
local digpos = vector.add(vector.add(vector.add(startpos,
vector.new(0, -ry, 0)),
vector.multiply(pdir, rp)),
vector.multiply(qdir, rq))
local can_dig = true
if can_dig and minetest.is_protected and minetest.is_protected(digpos, owner) then
can_dig = false
end
local dignode
if can_dig then
Optimize quarry_run Don't load the whole digging area when only a small piece is relevant. Also, move the (time expensive) check whether the air above a block is free to the last position, which spares unneccessary checks when multiple quarries are placed together, or a quarry has to loop over air for another reason.
2015-01-24 04:30:48 +01:00
dignode = technic.get_or_load_node(digpos) or minetest.get_node(digpos)
In quarry, skip past undiggable nodes The quarry used to get stuck when it encountered an undiggable node. Change it to skip past that node, digging whatever later stuff it can. Necessarily, the current digging position becomes semantically-significant state: it is no longer sufficient to search the quarry cuboid from the top on each iteration. The current digging height is reported in the quarry's interaction form, and can be reset to the top using a button on the form. Where there is a non-air node within the quarry directly above the next node to dig, it blocks the quarry's access to that node, even if everything involved is diggable. Thus an undiggable node casts a shadow of undug nodes below it. Resolving undiggability of a node is a major reason to use the restart button.
2014-08-17 20:19:11 +02:00
local dignodedef = minetest.registered_nodes[dignode.name] or {diggable=false}
if not dignodedef.diggable or (dignodedef.can_dig and not dignodedef.can_dig(digpos, nil)) then
can_dig = false
end
end
Optimize quarry_run Don't load the whole digging area when only a small piece is relevant. Also, move the (time expensive) check whether the air above a block is free to the last position, which spares unneccessary checks when multiple quarries are placed together, or a quarry has to loop over air for another reason.
2015-01-24 04:30:48 +01:00
if can_dig then
for ay = startpos.y, digpos.y+1, -1 do
local checkpos = {x=digpos.x, y=ay, z=digpos.z}
local checknode = technic.get_or_load_node(checkpos) or minetest.get_node(checkpos)
if checknode.name ~= "air" then
can_dig = false
break
end
end
end
In quarry, skip past undiggable nodes The quarry used to get stuck when it encountered an undiggable node. Change it to skip past that node, digging whatever later stuff it can. Necessarily, the current digging position becomes semantically-significant state: it is no longer sufficient to search the quarry cuboid from the top on each iteration. The current digging height is reported in the quarry's interaction form, and can be reset to the top using a button on the form. Where there is a non-air node within the quarry directly above the next node to dig, it blocks the quarry's access to that node, even if everything involved is diggable. Thus an undiggable node casts a shadow of undug nodes below it. Resolving undiggability of a node is a major reason to use the restart button.
2014-08-17 20:19:11 +02:00
nd = nd + 1
if can_dig then
minetest.remove_node(digpos)
for _, item in ipairs(minetest.get_node_drops(dignode.name, "")) do
technic.tube_inject_item(pos, pos, vector.new(0, 1, 0), item)
end
break
end
Make switching station run all machines it is connected to, including those in unloaded blocks.
2014-07-11 11:00:46 +02:00
end
In quarry, skip past undiggable nodes The quarry used to get stuck when it encountered an undiggable node. Change it to skip past that node, digging whatever later stuff it can. Necessarily, the current digging position becomes semantically-significant state: it is no longer sufficient to search the quarry cuboid from the top on each iteration. The current digging height is reported in the quarry's interaction form, and can be reset to the top using a button on the form. Where there is a non-air node within the quarry directly above the next node to dig, it blocks the quarry's access to that node, even if everything involved is diggable. Thus an undiggable node casts a shadow of undug nodes below it. Resolving undiggability of a node is a major reason to use the restart button.
2014-08-17 20:19:11 +02:00
meta:set_int("dug", nd)
Make switching station run all machines it is connected to, including those in unloaded blocks.
2014-07-11 11:00:46 +02:00
end
In quarry, skip past undiggable nodes The quarry used to get stuck when it encountered an undiggable node. Change it to skip past that node, digging whatever later stuff it can. Necessarily, the current digging position becomes semantically-significant state: it is no longer sufficient to search the quarry cuboid from the top on each iteration. The current digging height is reported in the quarry's interaction form, and can be reset to the top using a button on the form. Where there is a non-air node within the quarry directly above the next node to dig, it blocks the quarry's access to that node, even if everything involved is diggable. Thus an undiggable node casts a shadow of undug nodes below it. Resolving undiggability of a node is a major reason to use the restart button.
2014-08-17 20:19:11 +02:00
set_quarry_formspec(meta)
set_quarry_demand(meta)
Make switching station run all machines it is connected to, including those in unloaded blocks.
2014-07-11 11:00:46 +02:00
end
Partial rewrite
2013-07-17 21:34:35 +02:00
minetest.register_node("technic:quarry", {
Rationalise machine terminology All electrically-powered machines now consistently indicate their tier (supply voltage) in their names. As this implies that they are electrically powered, the furnaces no longer have "Electric" in their names. The fuel-fired equivalents of electric machines, which exist for alloy furnace and furnace, now say "Fuel-Fired" to distinguish them. (The fuel-fired alloy furnace used to say "Coal", which was inaccurate because it uses any fuel. The fuel-fired furnace, from the default mod, used to just be called "Furnace", which is ambiguous.) Electric power generators now consistently indicate their tier and have the word "Generator" in their names. This makes their purpose much clearer, and makes obvious craft guide searches produce useful results. The fuel-fired generators, previously just (ambiguously) called "Generator", are now explicitly "Fuel-Fired".
2014-06-20 17:58:52 +02:00
description = S("%s Quarry"):format("HV"),
split default iron/steel into three metals Override the default mod's iron/steel substance, replacing it with three metals: wrought iron (pure iron), carbon steel (iron alloyed with a little carbon), and cast iron (iron alloyed with lots of carbon). Wrought iron is easiest to refine, then cast iron, and carbon steel the most difficult, matching the historical progression. Recipes that used default steel are changed to use one of the three, the choice of alloy for each application being both somewhat realistic and also matching up with game progression. The default:steel{_ingot,block} items are identified specifically with wrought iron. This makes the default refining recipes work appropriately. Iron-using recipes defined outside technic are thus necessarily reinterpreted to use wrought iron, which is mostly appropriate. Some objects are renamed accordingly. Rather than use the default steel textures for wrought iron, with technic providing textures for the other two, technic now provides textures for all three metals. This avoids problems that would occur with texture packs that provide default_steel_{ingot,block} textures that are not intended to support this wrought-iron/carbon-steel/cast-iron distinction. A texture pack can provide a distinct set of three textures specifically for the situation where this distinction is required. Incidentally make grinding and alloy cooking recipes work correctly when ingredients are specified by alias.
2014-05-16 23:02:49 +02:00
tiles = {"technic_carbon_steel_block.png", "technic_carbon_steel_block.png",
"technic_carbon_steel_block.png", "technic_carbon_steel_block.png",
"technic_carbon_steel_block.png^default_tool_mesepick.png", "technic_carbon_steel_block.png"},
Partial rewrite
2013-07-17 21:34:35 +02:00
paramtype2 = "facedir",
Make switching station run all machines it is connected to, including those in unloaded blocks.
2014-07-11 11:00:46 +02:00
groups = {cracky=2, tubedevice=1, technic_machine = 1},
Partial rewrite
2013-07-17 21:34:35 +02:00
tube = {
connect_sides = {top = 1},
},
on_construct = function(pos)
local meta = minetest.get_meta(pos)
Rationalise machine terminology All electrically-powered machines now consistently indicate their tier (supply voltage) in their names. As this implies that they are electrically powered, the furnaces no longer have "Electric" in their names. The fuel-fired equivalents of electric machines, which exist for alloy furnace and furnace, now say "Fuel-Fired" to distinguish them. (The fuel-fired alloy furnace used to say "Coal", which was inaccurate because it uses any fuel. The fuel-fired furnace, from the default mod, used to just be called "Furnace", which is ambiguous.) Electric power generators now consistently indicate their tier and have the word "Generator" in their names. This makes their purpose much clearer, and makes obvious craft guide searches produce useful results. The fuel-fired generators, previously just (ambiguously) called "Generator", are now explicitly "Fuel-Fired".
2014-06-20 17:58:52 +02:00
meta:set_string("infotext", S("%s Quarry"):format("HV"))
Better quarry control dialog The size configuration is no longer cleared when exiting the dialog with <esc>. The enable/disable toggle button now indicates the current state. The name of the toggle button now varies according to state, so that pressing the button multiple times in one state (which can arise due to lag making the user unsure about whether the first press registered) only makes the state change that the user requested, rather than toggling repeatedly.
2014-05-23 23:37:44 +02:00
meta:set_int("size", 4)
set_quarry_formspec(meta)
In quarry, skip past undiggable nodes The quarry used to get stuck when it encountered an undiggable node. Change it to skip past that node, digging whatever later stuff it can. Necessarily, the current digging position becomes semantically-significant state: it is no longer sufficient to search the quarry cuboid from the top on each iteration. The current digging height is reported in the quarry's interaction form, and can be reset to the top using a button on the form. Where there is a non-air node within the quarry directly above the next node to dig, it blocks the quarry's access to that node, even if everything involved is diggable. Thus an undiggable node casts a shadow of undug nodes below it. Resolving undiggability of a node is a major reason to use the restart button.
2014-08-17 20:19:11 +02:00
set_quarry_demand(meta)
Partial rewrite
2013-07-17 21:34:35 +02:00
end,
after_place_node = function(pos, placer, itemstack)
local meta = minetest.get_meta(pos)
meta:set_string("owner", placer:get_player_name())
more pipeworks API-change updates
2013-12-15 21:49:28 +01:00
pipeworks.scan_for_tube_objects(pos)
Partial rewrite
2013-07-17 21:34:35 +02:00
end,
more pipeworks API-change updates
2013-12-15 21:49:28 +01:00
after_dig_node = pipeworks.scan_for_tube_objects,
Partial rewrite
2013-07-17 21:34:35 +02:00
on_receive_fields = quarry_receive_fields,
In quarry, skip past undiggable nodes The quarry used to get stuck when it encountered an undiggable node. Change it to skip past that node, digging whatever later stuff it can. Necessarily, the current digging position becomes semantically-significant state: it is no longer sufficient to search the quarry cuboid from the top on each iteration. The current digging height is reported in the quarry's interaction form, and can be reset to the top using a button on the form. Where there is a non-air node within the quarry directly above the next node to dig, it blocks the quarry's access to that node, even if everything involved is diggable. Thus an undiggable node casts a shadow of undug nodes below it. Resolving undiggability of a node is a major reason to use the restart button.
2014-08-17 20:19:11 +02:00
technic_run = quarry_run,
Partial rewrite
2013-07-17 21:34:35 +02:00
})
technic.register_machine("HV", "technic:quarry", technic.receiver)