flux reports: when re-generating an entity v ... #2416

New Issue

Open

opened 2022-08-07 04:24:30 +00:00 by yourland-report · 17 comments

yourland-report commented 2022-08-07 04:24:30 +00:00

Member

Copy Link

flux reports a bug:

when re-generating an entity via an LBM, possibly we do that in an minetest.after callback, w/ a random step of 0-5 server ticks, or such

Player position:

{
	y = 14.5,
	z = 1155.9250488281,
	x = 2083.5869140625
}

Player look:

{
	y = 0.15160585939884,
	z = -0.96786898374557,
	x = -0.20061227679253
}

Player information:

{
	patch = 0,
	formspec_version = 6,
	lang_code = "",
	major = 5,
	minor = 6,
	version_string = "5.6.0",
	state = "Active",
	min_rtt = 0.16400000452995,
	ip_version = 6,
	protocol_version = 40,
	max_rtt = 5.7540001869202,
	avg_rtt = 0.17499999701977,
	min_jitter = 0,
	max_jitter = 5.5830001831055,
	avg_jitter = 0,
	connection_uptime = 44010,
	serialization_version = 29
}

Player meta:

{
	fields = {
		["petz:werewolf"] = "1",
		["stamina:level"] = "16",
		["signslib:pos"] = "(1273,69,540)",
		["petz:old_override_table"] = "return {[\"new_move\"] = true, [\"sneak\"] = true, [\"sneak_glitch\"] = false, [\"jump\"] = 1.5, [\"speed\"] = 2, [\"gravity\"] = 1}",
		yl_church = "return {[\"last_death_portal\"] = 1653796347, [\"last_death\"] = {[\"y\"] = 26, [\"z\"] = 2823, [\"x\"] = 7034}, [\"last_heal\"] = 1615504208}",
		punch_count = "89340",
		jointime = "1615351173",
		inflicted_damage = "1482270",
		arenalib_infobox_arenaID = "0",
		partychat = "party",
		["petz:werewolf_clan_idx"] = "1",
		["stamina:exhaustion"] = "86.5",
		yl_commons_player_created = "1615351173",
		["unified_inventory:bags"] = "return {\"water_life:croc_bag\", \"water_life:croc_bag\", \"water_life:croc_bag\", \"water_life:croc_bag\"}",
		["petz:werewolf_vignette_id"] = "20",
		xp = "1280822",
		yl_commons_thankyou = "136",
		["petz:lycanthropy"] = "1",
		bitten = "0",
		played_time = "21271695",
		digged_nodes = "1087226",
		placed_nodes = "353207",
		died = "67",
		crafted = "39489",
		yl_commons_player_joined = "1659802287",
		["stamina:poisoned"] = "no",
		hud_state = "on",
		repellant = "0",
		["3d_armor_inventory"] = "return {\"3d_armor:helmet_nether 1 2280\", \"3d_armor:chestplate_nether 1 4560\", \"3d_armor:leggings_nether 1 4560\", \"nether_mobs:dragon_shield 1 2280\", \"nether_mobs:dragon_boots 1 2280\", \"\"}"
	}
}

Log identifier

[MOD] yl_report log identifier = Cmcp1G11JYiRYFZ3UqQqsQq1QhGrnscl

Profiler save:

profile-20220807T042429.json_prettyEE

Status:

# Server: version: 5.5.1-yl | game: Minetest Game | uptime: 7d 1h 2min 29s | max lag: 1.87s | clients: bluattire, Woodman1234, Aayush0350C, dragon014, Azelf, evil123, jerry, acen2006, Ivanhoe, daydream, Lupercus, Onlan, hbreturns, the_chosen_one, Bailiff, AliasAlreadyTaken, digdeeper, digdeep, Winter_Tundra, Yuki567, Service, flux

Teleport command:

/teleport xyz 2084 15 1156

Compass command:

/give_compass Construction Cmcp1G11JYiRYFZ3UqQqsQq1QhGrnscl D2691E 2084 15 1156

flux reports a bug: > when re-generating an entity via an LBM, possibly we do that in an `minetest.after` callback, w/ a random step of 0-5 server ticks, or such Player position: ``` { y = 14.5, z = 1155.9250488281, x = 2083.5869140625 } ``` Player look: ``` { y = 0.15160585939884, z = -0.96786898374557, x = -0.20061227679253 } ``` Player information: ``` { patch = 0, formspec_version = 6, lang_code = "", major = 5, minor = 6, version_string = "5.6.0", state = "Active", min_rtt = 0.16400000452995, ip_version = 6, protocol_version = 40, max_rtt = 5.7540001869202, avg_rtt = 0.17499999701977, min_jitter = 0, max_jitter = 5.5830001831055, avg_jitter = 0, connection_uptime = 44010, serialization_version = 29 } ``` Player meta: ``` { fields = { ["petz:werewolf"] = "1", ["stamina:level"] = "16", ["signslib:pos"] = "(1273,69,540)", ["petz:old_override_table"] = "return {[\"new_move\"] = true, [\"sneak\"] = true, [\"sneak_glitch\"] = false, [\"jump\"] = 1.5, [\"speed\"] = 2, [\"gravity\"] = 1}", yl_church = "return {[\"last_death_portal\"] = 1653796347, [\"last_death\"] = {[\"y\"] = 26, [\"z\"] = 2823, [\"x\"] = 7034}, [\"last_heal\"] = 1615504208}", punch_count = "89340", jointime = "1615351173", inflicted_damage = "1482270", arenalib_infobox_arenaID = "0", partychat = "party", ["petz:werewolf_clan_idx"] = "1", ["stamina:exhaustion"] = "86.5", yl_commons_player_created = "1615351173", ["unified_inventory:bags"] = "return {\"water_life:croc_bag\", \"water_life:croc_bag\", \"water_life:croc_bag\", \"water_life:croc_bag\"}", ["petz:werewolf_vignette_id"] = "20", xp = "1280822", yl_commons_thankyou = "136", ["petz:lycanthropy"] = "1", bitten = "0", played_time = "21271695", digged_nodes = "1087226", placed_nodes = "353207", died = "67", crafted = "39489", yl_commons_player_joined = "1659802287", ["stamina:poisoned"] = "no", hud_state = "on", repellant = "0", ["3d_armor_inventory"] = "return {\"3d_armor:helmet_nether 1 2280\", \"3d_armor:chestplate_nether 1 4560\", \"3d_armor:leggings_nether 1 4560\", \"nether_mobs:dragon_shield 1 2280\", \"nether_mobs:dragon_boots 1 2280\", \"\"}" } } ``` Log identifier ``` [MOD] yl_report log identifier = Cmcp1G11JYiRYFZ3UqQqsQq1QhGrnscl ``` Profiler save: ``` profile-20220807T042429.json_prettyEE ``` Status: ``` # Server: version: 5.5.1-yl | game: Minetest Game | uptime: 7d 1h 2min 29s | max lag: 1.87s | clients: bluattire, Woodman1234, Aayush0350C, dragon014, Azelf, evil123, jerry, acen2006, Ivanhoe, daydream, Lupercus, Onlan, hbreturns, the_chosen_one, Bailiff, AliasAlreadyTaken, digdeeper, digdeep, Winter_Tundra, Yuki567, Service, flux ``` Teleport command: ``` /teleport xyz 2084 15 1156 ``` Compass command: ``` /give_compass Construction Cmcp1G11JYiRYFZ3UqQqsQq1QhGrnscl D2691E 2084 15 1156 ```

AliasAlreadyTaken was assigned by yourland-report 2022-08-07 04:24:30 +00:00

AliasAlreadyTaken added the

1. kind/enhancement

label 2022-08-07 06:05:01 +00:00

flux self-assigned this 2022-08-07 16:58:58 +00:00

flux added this to the flux's TODO list project 2022-08-07 16:59:01 +00:00

flux added the

3. source/lag

2. prio/interesting

labels 2022-08-07 16:59:20 +00:00

AliasAlreadyTaken was unassigned by flux 2022-08-07 17:01:34 +00:00

flux commented 2022-08-09 19:26:38 +00:00

Member

Copy Link

perhaps i could create a generalized "add_entity_queue", which adds at most a fixed # of these "create on load" entities every server tick.

mods which should use this:

• anvil (cottages)
• display_modpack
• itemframes
• itemshelf
• signs_lib
• smartshop

perhaps i could create a generalized "add_entity_queue", which adds at most a fixed # of these "create on load" entities every server tick. mods which should use this: * [ ] anvil (cottages) * [ ] display_modpack * [ ] itemframes * [ ] itemshelf * [ ] signs_lib * [ ] smartshop

flux commented 2022-08-10 20:37:15 +00:00

Member

Copy Link

from alias:

what	min us	max us	avg us	min %	max %	avg %
smartshop:	0	104671	556	0.0	53.4	0.5
- on_player_receive_fields[1]	1	4	2	0.0	0.0	0.0
- LBM 'smartshop:load_shop'	14064	88890	51477	39.4	45.3	42.4
- LBM 'smartshop:repay_lost_stuff'	1942	15781	8861	5.4	8.0	6.7

from alias: | what | min us | max us | avg us | min % | max % | avg % | | -------- | -------- | -------- |-------- | -------- | -------- | -------- | |smartshop: | 0 | 104671 | 556 | 0.0 | 53.4 | 0.5 | - on_player_receive_fields[1] | 1 | 4 | 2 | 0.0 | 0.0 | 0.0 | - LBM 'smartshop:load_shop' | 14064 | 88890 | 51477 | 39.4 | 45.3 | 42.4 | - LBM 'smartshop:repay_lost_stuff' | 1942 | 15781 | 8861 | 5.4 | 8.0 | 6.7

flux commented 2022-08-10 22:30:39 +00:00

Member

Copy Link

ugh. this became a rabbit hole.

1. the LBMs are still quite expensive even if the stuff is queued to execute across multiple server steps
2. i (re?)discovered that LBMs run when a block becomes active (active_block_range=1), not when it's loaded (max_block_send_distance=10), nor when the entities in the block would normally be loaded (active_object_send_range_blocks=3). this meant that a lot of times, i was throwing away and re-creating entities when i didn't need to be. that wasn't hard to fix - the LBM needed to check to see if the existing entities matched what was expected to be there, and only re-create them then. however, doing those checks is almost as expensive as just re-creating them... but it looks a bit better.
3. there's no way to spread out sending already loaded entities to clients, so the client still gets a huge lag spike when they wander into an area w/ a huge number of loaded entities.

this lead me into trying to identify ways to only keep the entities loaded if a player is close enough to see it well. this may have to be an ABM, which ... may help the clients, but will certainly create a lot of processing load.

ugh. this became a rabbit hole. 1. the LBMs are still quite expensive even if the stuff is queued to execute across multiple server steps 2. i (re?)discovered that LBMs run when a block becomes *active* (`active_block_range=1`), not when it's *loaded* (`max_block_send_distance=10`), nor when the entities in the block would normally be loaded (`active_object_send_range_blocks=3`). this meant that a lot of times, i was throwing away and re-creating entities when i didn't need to be. that wasn't hard to fix - the LBM needed to check to see if the existing entities matched what was expected to be there, and only re-create them then. however, doing those checks is almost as expensive as just re-creating them... but it looks a bit better. 3. there's no way to spread out sending *already loaded* entities to clients, so the client still gets a huge lag spike when they wander into an area w/ a huge number of loaded entities. this lead me into trying to identify ways to only keep the entities loaded if a player is close enough to see it well. this may have to be an ABM, which ... may help the clients, but will certainly create a lot of processing load.

flux commented 2022-08-10 23:04:20 +00:00

Member

Copy Link

i wonder if i should just go back to having statically-saved entities and double-checking the state of things whenever one loads (whether via add_entity or statically). given that there's only 1 thread, there's ways to avoid the "race condition".

i wonder if i should just go back to having statically-saved entities and double-checking the state of things whenever one loads (whether via `add_entity` or statically). given that there's only 1 thread, there's ways to avoid the "race condition".

flux commented 2022-08-10 23:32:21 +00:00

Member

Copy Link

if we remain non-static, i wonder if we could benefit of from manually restricting outselves to the declared max_objects_per_block=512 value. like, if there's that many entities nearby, refuse to create more. then again, a single mapblock rarely has that many entities in it, usually at most a couple hundred.

options:

• lower max_objects_per_block and implement the idea above. downside to that would be that if e.g. several hundred pets unloaded, not all of them might survive.
• allow specifying a limit specifically for smartshop nodes (and possibly for other "node-bound" entities)

if we remain non-static, i wonder if we could benefit of from manually restricting outselves to the declared `max_objects_per_block=512` value. like, if there's that many entities nearby, refuse to create more. then again, a single mapblock rarely has *that* many entities in it, usually at most a couple hundred. options: * lower `max_objects_per_block` and implement the idea above. downside to that would be that if e.g. several hundred pets unloaded, not all of them might survive. * allow specifying a limit specifically for smartshop nodes (and possibly for other "node-bound" entities)

flux commented 2022-08-10 23:33:10 +00:00

Member

Copy Link

perhaps i should just create a "node_entities" mod to make managing them unified and sensical

perhaps i should just create a "node_entities" mod to make managing them unified and sensical

flux added the

4. step/at work

label 2022-08-11 00:06:05 +00:00

flux commented 2022-08-11 00:09:53 +00:00

Member

Copy Link

testing...

testing... 

screenshot_20220810_133421.png

1.7 MiB

flux commented 2022-08-11 00:17:54 +00:00

Member

Copy Link

want to finish the cottages update before i work on this more. it's turned into a huge thing.

want to finish the cottages update before i work on this more. it's turned into a huge thing.

flux commented 2022-10-01 02:07:00 +00:00

Member

Copy Link

this turned into 3 mods:

• https://github.com/fluxionary/minetest-futil
• https://github.com/fluxionary/minetest-action_queues
• https://github.com/fluxionary/minetest-node_entity_queue

see #2623 for more info.

this issue should stay open, as a tracker of progress in making use of node_entity_queue for the various mods.

this turned into 3 mods: * https://github.com/fluxionary/minetest-futil * https://github.com/fluxionary/minetest-action_queues * https://github.com/fluxionary/minetest-node_entity_queue see #2623 for more info. this issue should stay open, as a tracker of progress in making use of node_entity_queue for the various mods.

AliasAlreadyTaken commented 2022-10-12 16:33:13 +00:00

Owner

Copy Link

Could the engine be optimized in this place? If you need to jump through several API hoops to achieve a small loadbalancing effect, maybe engine upstream needs to improve at this point?

Could the engine be optimized in this place? If you need to jump through several API hoops to achieve a small loadbalancing effect, maybe engine upstream needs to improve at this point?

flux commented 2022-10-12 17:57:07 +00:00

Member

Copy Link

Could the engine be optimized in this place? If you need to jump through several API hoops to achieve a small loadbalancing effect, maybe engine upstream needs to improve at this point?

yes, i believe there's several proposals to help out w/ entity and LBM stuff.

• node bound entities - which hasn't been commented on since 2019, but shows that people have discussed various optimizations for such entities
• add bulk ABMs; there's also discussion there of bulk LBMs

> Could the engine be optimized in this place? If you need to jump through several API hoops to achieve a small loadbalancing effect, maybe engine upstream needs to improve at this point? yes, i believe there's several proposals to help out w/ entity and LBM stuff. * [node bound entities](https://github.com/minetest/minetest/issues/6963) - which hasn't been commented on since 2019, but shows that people have discussed various optimizations for such entities * [add bulk ABMs](https://github.com/minetest/minetest/pull/12128); there's also discussion there of bulk LBMs

flux commented 2022-11-03 04:54:33 +00:00

Member

Copy Link

i do think i can create a mod which defines a canonical interface for creating such entities, but it's a non-trivial amount of work. it might be a good API mod to incorporate into a game (your-land/administration#174), but it'll be an uphill battle to make other mods depend on it.

i do think i can create a mod which defines a canonical interface for creating such entities, but it's a non-trivial amount of work. it might be a good API mod to incorporate into a game (https://gitea.your-land.de/your-land/administration/issues/174), but it'll be an uphill battle to make other mods depend on it.

flux commented 2022-11-03 12:51:33 +00:00

Member

Copy Link

upstream engine issue about this, which i should get around to reading sometime https://github.com/minetest/minetest/issues/6963

upstream engine issue about this, which i should get around to reading sometime https://github.com/minetest/minetest/issues/6963

flux removed the

4. step/at work

label 2022-11-03 12:52:19 +00:00

AliasAlreadyTaken commented 2022-11-03 16:50:11 +00:00

Owner

Copy Link

If it's in the base game, all mods using this game as a basis will depend on it.

Making all modmokers reotroactively add support will be next to impossible.

If it's in the base game, all mods using this game as a basis will depend on it. Making all modmokers reotroactively add support will be next to impossible.

flux added the

4. step/ready to QA test

label 2023-05-02 21:55:37 +00:00

AliasAlreadyTaken commented 2023-12-06 19:07:40 +00:00

Owner

Copy Link

QA

How would I test this?

QA How would I test this?

AliasAlreadyTaken added the

4. step/question

label 2023-12-06 19:07:47 +00:00

flux commented 2023-12-07 20:11:07 +00:00

Member

Copy Link

How would I test this?

note: this is only "fixed" for smartshops - other node entities, e.g. signs and item frames, don't make use of the queue.

first, you need to modify the instrumentation code so that you can see the source of various callbacks in order to differentiate them:

diff --git a/builtin/profiler/instrumentation.lua b/builtin/profiler/instrumentation.lua
index 5c1cb191b..42b1c0c5a 100644
--- a/builtin/profiler/instrumentation.lua
+++ b/builtin/profiler/instrumentation.lua
@@ -61,11 +61,9 @@ local function generate_name(def)
        elseif label == false then
                return format("%s", class or func_name):trim()
        end
-
-       local index_id = def.mod .. (class or func_name)
-       local index = counts[index_id] or 1
-       counts[index_id] = index + 1
-       return format("%s[%d] %s", class or func_name, index, class and func_name or ""):trim()
+       local info = debug.getinfo(def.func)
+       local worldpath = minetest.get_worldpath()
+       return format("%s %s#%s", class or func_name, info.source:gsub(worldpath, ""), info.linedefined)
 end
 
 ---
diff --git a/builtin/profiler/reporter.lua b/builtin/profiler/reporter.lua
index 5928a3718..2e24a1fe0 100644
--- a/builtin/profiler/reporter.lua
+++ b/builtin/profiler/reporter.lua
@@ -77,7 +77,7 @@ local Formatter = {
        end
 }
 
-local widths = { 55, 9, 9, 9, 5, 5, 5 }
+local widths = { 80, 9, 9, 9, 5, 5, 5 }
 local txt_row_format = sprintf(" %%-%ds | %%%ds | %%%ds | %%%ds | %%%ds | %%%ds | %%%ds", unpack(widths))
 
 local HR = {}

then, you need to create a giant wall of smartshops w/ random items in them. mark two positions with worldedit, and run the following snippet (change "flux" to your name):

local player_name = "flux"
local items = {}
for item in pairs(minetest.registered_items) do
 table.insert(items, item)
end
local non_nodes = {}
for item in pairs(minetest.registered_tools) do
 table.insert(non_nodes, item)
end
for item in pairs(minetest.registered_craftitems) do
 table.insert(non_nodes, item)
end

local f = minetest.get_player_by_name(player_name)

local p1 = worldedit.pos1[player_name]
local p2 = worldedit.pos2[player_name]
local v = VoxelArea:new({MinEdge = p1, MaxEdge = p2})

for i in v:iterp(worldedit.pos1.flux, worldedit.pos2.flux) do
 local p = v:position(i)
 local n = minetest.get_node(p)
 if n.name ~= "smartshop.shop" then
  minetest.item_place_node(ItemStack("smartshop:shop"), f, {type = "node", under=p, above=p}, 0)
 end
 local shop = smartshop.api.get_object(p)
 local inv = shop.inv
 if p.y % 2 == 0 then
  for i = 1, 4 do
   inv:set_stack(("pay%i"):format(i), 1,  non_nodes[math.random(1, #non_nodes)])
   inv:set_stack(("give%i"):format(i), 1,  non_nodes[math.random(1, #non_nodes)])
  end
 else
  for i = 1, 4 do
   inv:set_stack(("pay%i"):format(i), 1,  items[math.random(1, #items)])
   inv:set_stack(("give%i"):format(i), 1,  items[math.random(1, #items)])
  end
 end
 shop:update_entities()
end

now, you need to turn off node_entity_queue and restart the server. when you log back in next to the wall of smartshops, you can check the performance of the smartshop callbacks:

now, re-enable node_entity_queue and restart the server again. check the performance again:

the performance isn't as incredible as i wish it were, but it's reducing the size of the biggest lag spike to 1/3 the previous duration.

> How would I test this? note: this is only "fixed" for smartshops - other node entities, e.g. signs and item frames, don't make use of the queue. first, you need to modify the instrumentation code so that you can see the *source* of various callbacks in order to differentiate them: ```diff diff --git a/builtin/profiler/instrumentation.lua b/builtin/profiler/instrumentation.lua index 5c1cb191b..42b1c0c5a 100644 --- a/builtin/profiler/instrumentation.lua +++ b/builtin/profiler/instrumentation.lua @@ -61,11 +61,9 @@ local function generate_name(def) elseif label == false then return format("%s", class or func_name):trim() end - - local index_id = def.mod .. (class or func_name) - local index = counts[index_id] or 1 - counts[index_id] = index + 1 - return format("%s[%d] %s", class or func_name, index, class and func_name or ""):trim() + local info = debug.getinfo(def.func) + local worldpath = minetest.get_worldpath() + return format("%s %s#%s", class or func_name, info.source:gsub(worldpath, ""), info.linedefined) end --- diff --git a/builtin/profiler/reporter.lua b/builtin/profiler/reporter.lua index 5928a3718..2e24a1fe0 100644 --- a/builtin/profiler/reporter.lua +++ b/builtin/profiler/reporter.lua @@ -77,7 +77,7 @@ local Formatter = { end } -local widths = { 55, 9, 9, 9, 5, 5, 5 } +local widths = { 80, 9, 9, 9, 5, 5, 5 } local txt_row_format = sprintf(" %%-%ds | %%%ds | %%%ds | %%%ds | %%%ds | %%%ds | %%%ds", unpack(widths)) local HR = {} ``` then, you need to create a giant wall of smartshops w/ random items in them. mark two positions with worldedit, and run the following snippet (change "flux" to your name): ```lua local player_name = "flux" local items = {} for item in pairs(minetest.registered_items) do table.insert(items, item) end local non_nodes = {} for item in pairs(minetest.registered_tools) do table.insert(non_nodes, item) end for item in pairs(minetest.registered_craftitems) do table.insert(non_nodes, item) end local f = minetest.get_player_by_name(player_name) local p1 = worldedit.pos1[player_name] local p2 = worldedit.pos2[player_name] local v = VoxelArea:new({MinEdge = p1, MaxEdge = p2}) for i in v:iterp(worldedit.pos1.flux, worldedit.pos2.flux) do local p = v:position(i) local n = minetest.get_node(p) if n.name ~= "smartshop.shop" then minetest.item_place_node(ItemStack("smartshop:shop"), f, {type = "node", under=p, above=p}, 0) end local shop = smartshop.api.get_object(p) local inv = shop.inv if p.y % 2 == 0 then for i = 1, 4 do inv:set_stack(("pay%i"):format(i), 1, non_nodes[math.random(1, #non_nodes)]) inv:set_stack(("give%i"):format(i), 1, non_nodes[math.random(1, #non_nodes)]) end else for i = 1, 4 do inv:set_stack(("pay%i"):format(i), 1, items[math.random(1, #items)]) inv:set_stack(("give%i"):format(i), 1, items[math.random(1, #items)]) end end shop:update_entities() end ```  now, you need to turn off node_entity_queue and restart the server. when you log back in next to the wall of smartshops, you can check the performance of the smartshop callbacks:  now, re-enable node_entity_queue and restart the server again. check the performance again:  the performance isn't as incredible as i wish it were, but it's reducing the size of the biggest lag spike to 1/3 the previous duration.

image.png

640 KiB

image.png

976 KiB

image.png

1.3 MiB

flux commented 2023-12-18 23:48:30 +00:00

Member

Copy Link

the node_entity_queue is now live, though only smartshops make use of it. there's still far more sign and itemframe entities around in general.

the node_entity_queue is now live, though only smartshops make use of it. there's still far more sign and itemframe entities around in general.

flux referenced this issue 2023-12-19 21:39:54 +00:00

better profiler output #5753

whosit referenced this issue 2024-01-26 16:46:56 +00:00

Service reports: Unlag spawn. Reduce signposts ... #5234

flux added

4. step/partially fixed

3. source/mod upstream

3. source/integration

and removed

4. step/ready to QA test

4. step/question

labels 2024-03-30 19:17:33 +00:00

Sign in to join this conversation.

No Branch/Tag Specified

Branches Tags

Labels

Clear labels   

1. kind/balancing

Depends on balancing

  

1. kind/breaking

something that alters or disables an existing game mechanic

  

1. kind/bug

Something is not working

  

1. kind/construction

A build needs fixing

  

1. kind/documentation

Needs proper documentation

  

1. kind/enhancement

New feature

  

1. kind/griefing

players despoiling builds or nature

  

1. kind/invalid

Not a valid report, e.g. created by mistake with no content.

  

1. kind/meme

issue is mostly a joke

  

1. kind/node limit

something which works for or against the node limit

  

1. kind/other

Something not within the other kinds

  

1. kind/protocol

something concerning how staff should react to player requests, or how players should treat each other

  

2. prio/controversial

not likely to happen w/out a lot of discussion

  

2. prio/critical

Very important

  

2. prio/elevated

something players are eager to have fixed

  

2. prio/good first issue

the resolution to this is could be done by a new minetest contributor, who doesn't yet understand the mod ecosystem

  

2. prio/interesting

one of us has real interest in getting this implemented or fixed. however, more research might be needed.

  

2. prio/low

Not so important

  

3. source/art

art needs to be created or found for this to exist. includes sound, 3d modelling, and in-game building.

  

3. source/client

Issue is with the minetest client, or with player client configuration or the technical details of their setup

  

3. source/engine

Issue is due to a bug or feature of the minetest engine

  

3. source/ingame

Problem and solution exist in-game, e.g. builds or player moderation

  

3. source/integration

Two or more nonbuggy mechanics conflict, or our attempts to rectify conflicting mechanics have created a new bug

  

3. source/lag

A problem which is caused or made worse by lag, due to server processing issues, client processing issues, or network issues

  

3. source/license

A licensing problem is involved

  

3. source/mod upstream

Problem is upstream (not engine/client)

  

3. source/unknown

  

3. source/website

Affects the website

  

4. step/approved

Alias has approved this feature, someone should implement it

  

4. step/at work

Being worked on

  

4. step/blocked

we plan to do this, but other work has to be finished first

  

4. step/discussion

issue is under discussion, a solution has not been dictated or agreed upon

  

4. step/help wanted

Need some help

  

4. step/needs confirmation

  

4. step/partially fixed

this is mitigated or partially solved, but more work needs to be done

  

4. step/question

More information is needed

  

4. step/ready to deploy

has been QA tested by another person. has no outstanding issues. might be installed on prod, but needs final testing

  

4. step/ready to QA test

the code is supposedly fixed, but needs to be tested.

  

4. step/want approval

Someone can quickly implement this if Alias approves the change/feature

  

5. result/cannot reproduce

  

5. result/duplicate

This issue or pull request already exists

  

5. result/fixed

problem is fixed

  

5. result/maybe

not planned currently, but maybe some day

  

5. result/wontfix

the reported issue won't be changed, whether it's intentional or not.

  

ugh/petz

yet another petz bugz.

  

ugh/QA main

That's something we can only wait and see whether it hapens again: On the main server

  

ugh/QA NOK

Fix didn't yield the expected results

  

ugh/QA OK

tested

No Label

1. kind/balancing

1. kind/breaking

1. kind/bug

1. kind/construction

1. kind/documentation

1. kind/enhancement

1. kind/griefing

1. kind/invalid

1. kind/meme

1. kind/node limit

1. kind/other

1. kind/protocol

2. prio/controversial

2. prio/critical

2. prio/elevated

2. prio/good first issue

2. prio/interesting

2. prio/low

3. source/art

3. source/client

3. source/engine

3. source/ingame

3. source/integration

3. source/lag

3. source/license

3. source/mod upstream

3. source/unknown

3. source/website

4. step/approved

4. step/at work

4. step/blocked

4. step/discussion

4. step/help wanted

4. step/needs confirmation

4. step/partially fixed

4. step/question

4. step/ready to deploy

4. step/ready to QA test

4. step/want approval

5. result/cannot reproduce

5. result/duplicate

5. result/fixed

5. result/maybe

5. result/wontfix

ugh/petz

ugh/QA main

ugh/QA NOK

ugh/QA OK

Milestone

Clear milestone

No items

No Milestone

Projects

Clear projects

No project

flux's TODO list

Assignees

Clear assignees

No Assignees

flux

3 Participants

Notifications

Subscribe

Due Date

The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: your-land/bugtracker#2416

No description provided.