Chache reports: Regarding rotation, YL_livemap ... #6347

New Issue

Closed

opened 2024-02-25 12:54:43 +00:00 by yourland-report · 32 comments

yourland-report commented 2024-02-25 12:54:43 +00:00

Member

Copy Link

Chache reports a bug:

Regarding rotation, YL_livemapping maps behave the same exceptional way as hides and other few nodes - instead of the default behaviour. That means that if you place a YL map horizontally (for example as if placed on a table) it will only appear with the north of the map pointing east. If you try to rotate it, it will just cycle through the 6 sides of the node, but never rotate the face while staying horizontal. Suggestion: make the YL maps behave in the default manner when rotating.

Player position:

{
	z = -2765.8461914063,
	x = 2969.4880371094,
	y = 17.625
}

Player look:

{
	z = 0.033715531229973,
	x = 0.5658341050148,
	y = -0.82382953166962
}

Player information:

{
	minor = 8,
	state = "Active",
	major = 5,
	max_rtt = 6.6770000457764,
	ip_version = 6,
	min_rtt = 0.028999999165535,
	avg_rtt = 0.20100000500679,
	min_jitter = 0,
	max_jitter = 6.5900001525879,
	avg_jitter = 0.16899999976158,
	connection_uptime = 5026,
	serialization_version = 29,
	patch = 0,
	protocol_version = 42,
	version_string = "5.8.0",
	formspec_version = 7,
	lang_code = "es"
}

Player meta:

{
	fields = {
		placed_nodes = "638145",
		punch_count = "53584",
		["3d_armor_inventory"] = "return {\"3d_armor:helmet_nether 1 34080\", \"3d_armor:chestplate_crystal 1 34060\", \"shields:shield_rainbow 1 13672\", \"3d_armor:leggings_crystal 1 34060\", \"3d_armor:boots_crystal 1 34160\", \"\"}",
		xp_redo_hud_color = "0xFFFF00",
		yl_commons_thankyou = "471",
		partychat = "party",
		["stamina:level"] = "13",
		["ocean_build.ocean_built"] = "12",
		["stamina:poisoned"] = "no",
		hud_state = "on",
		["stamina:exhaustion"] = "107.5",
		inflicted_damage = "1667564",
		repellant = "0",
		["ocean_build.last_warning"] = "1.65606e+09",
		["ocean_build.forbidden"] = "true",
		xp = "1565555",
		digged_nodes = "1261790",
		arenalib_infobox_arenaID = "0",
		jointime = "1645471717",
		bitten = "0",
		yl_commons_player_joined = "1708860671",
		["unified_inventory:bags"] = "return {\"unified_inventory:bag_large\", \"unified_inventory:bag_large\", \"unified_inventory:bag_large\", \"unified_inventory:bag_large\"}",
		played_time = "13364737",
		yl_commons_player_created = "1645471717",
		["signslib:pos"] = "(2927,13,-2745)",
		died = "14",
		crafted = "285127",
		yl_church = "return {[\"last_death_portal\"] = 1708692284, [\"last_heal\"] = 1653594577, [\"last_death\"] = {[\"y\"] = 27, [\"z\"] = -2131, [\"x\"] = 3229}}"
	}
}

Log identifier

[MOD] yl_report log identifier = mnqaW29Rc3X5eT704vB9nb6S79lcw4uj

Profiler save:

profile-20240225T125443.json_prettyEE

Status:

# Server: version: 5.7.0-yl-thx-tmm | game: Minetest Game | uptime: 17h 31min 41s | max lag: 0.785s | clients (27/52): AliasAlreadyTaken, Aliza, Azelf, Bailiff, Bingo, Boot, Chache, Craftsman, daydream, der_c_aus_a, DragonWrangler1, florian, JeCel, JinnyC, LeetPeet, LilyBelle, lumberJack, Marat1ch, MineWorlds, Murmel, Penelopee, Ravise, Service, Sokomine, tagtraum, TimurHami, valli

Teleport command:

/teleport xyz 2969 18 -2766

Compass command:

/give_compass Construction mnqaW29Rc3X5eT704vB9nb6S79lcw4uj D2691E 2969 18 -2766

Chache reports a bug: > Regarding rotation, YL_livemapping maps behave the same exceptional way as hides and other few nodes - instead of the default behaviour. That means that if you place a YL map horizontally (for example as if placed on a table) it will only appear with the north of the map pointing east. If you try to rotate it, it will just cycle through the 6 sides of the node, but never rotate the face while staying horizontal. Suggestion: make the YL maps behave in the default manner when rotating. Player position: ``` { z = -2765.8461914063, x = 2969.4880371094, y = 17.625 } ``` Player look: ``` { z = 0.033715531229973, x = 0.5658341050148, y = -0.82382953166962 } ``` Player information: ``` { minor = 8, state = "Active", major = 5, max_rtt = 6.6770000457764, ip_version = 6, min_rtt = 0.028999999165535, avg_rtt = 0.20100000500679, min_jitter = 0, max_jitter = 6.5900001525879, avg_jitter = 0.16899999976158, connection_uptime = 5026, serialization_version = 29, patch = 0, protocol_version = 42, version_string = "5.8.0", formspec_version = 7, lang_code = "es" } ``` Player meta: ``` { fields = { placed_nodes = "638145", punch_count = "53584", ["3d_armor_inventory"] = "return {\"3d_armor:helmet_nether 1 34080\", \"3d_armor:chestplate_crystal 1 34060\", \"shields:shield_rainbow 1 13672\", \"3d_armor:leggings_crystal 1 34060\", \"3d_armor:boots_crystal 1 34160\", \"\"}", xp_redo_hud_color = "0xFFFF00", yl_commons_thankyou = "471", partychat = "party", ["stamina:level"] = "13", ["ocean_build.ocean_built"] = "12", ["stamina:poisoned"] = "no", hud_state = "on", ["stamina:exhaustion"] = "107.5", inflicted_damage = "1667564", repellant = "0", ["ocean_build.last_warning"] = "1.65606e+09", ["ocean_build.forbidden"] = "true", xp = "1565555", digged_nodes = "1261790", arenalib_infobox_arenaID = "0", jointime = "1645471717", bitten = "0", yl_commons_player_joined = "1708860671", ["unified_inventory:bags"] = "return {\"unified_inventory:bag_large\", \"unified_inventory:bag_large\", \"unified_inventory:bag_large\", \"unified_inventory:bag_large\"}", played_time = "13364737", yl_commons_player_created = "1645471717", ["signslib:pos"] = "(2927,13,-2745)", died = "14", crafted = "285127", yl_church = "return {[\"last_death_portal\"] = 1708692284, [\"last_heal\"] = 1653594577, [\"last_death\"] = {[\"y\"] = 27, [\"z\"] = -2131, [\"x\"] = 3229}}" } } ``` Log identifier ``` [MOD] yl_report log identifier = mnqaW29Rc3X5eT704vB9nb6S79lcw4uj ``` Profiler save: ``` profile-20240225T125443.json_prettyEE ``` Status: ``` # Server: version: 5.7.0-yl-thx-tmm | game: Minetest Game | uptime: 17h 31min 41s | max lag: 0.785s | clients (27/52): AliasAlreadyTaken, Aliza, Azelf, Bailiff, Bingo, Boot, Chache, Craftsman, daydream, der_c_aus_a, DragonWrangler1, florian, JeCel, JinnyC, LeetPeet, LilyBelle, lumberJack, Marat1ch, MineWorlds, Murmel, Penelopee, Ravise, Service, Sokomine, tagtraum, TimurHami, valli ``` Teleport command: ``` /teleport xyz 2969 18 -2766 ``` Compass command: ``` /give_compass Construction mnqaW29Rc3X5eT704vB9nb6S79lcw4uj D2691E 2969 18 -2766 ```

AliasAlreadyTaken was assigned by yourland-report 2024-02-25 12:54:43 +00:00

whosit commented 2024-02-25 17:10:15 +00:00

Member

Copy Link

Maps have

        drawtype = "signlike",
        paramtype2 = "wallmounted",

I guess that's just how they are?
Not sure what are the benefits though.

Maps have ``` drawtype = "signlike", paramtype2 = "wallmounted", ``` I guess that's just how they are? Not sure what are the benefits though.

AliasAlreadyTaken added the

1. kind/enhancement

label 2024-02-25 17:44:05 +00:00

flux commented 2024-02-25 18:31:42 +00:00

Member

Copy Link

would have to set paramtype2 = "facedir". is there a reason why it's currently "wallmounted"?

would have to set `paramtype2 = "facedir"`. is there a reason why it's currently "wallmounted"?

AliasAlreadyTaken commented 2024-02-25 18:35:18 +00:00

Owner

Copy Link

would have to set paramtype2 = "facedir". is there a reason why it's currently "wallmounted"?

Yes, there is a very good cause: Because this was pretty much my very first mod. Apparently wallmounted was the first value that worked approximately the way I wanted. That's how it became the chosen one(tm). Means: If we can change it to fix this issue without requiring a migration, let's do.

> would have to set `paramtype2 = "facedir"`. is there a reason why it's currently "wallmounted"? Yes, there is a very good cause: Because this was pretty much my very first mod. Apparently wallmounted was the first value that worked approximately the way I wanted. That's how it became the chosen one(tm). Means: If we can change it to fix this issue without requiring a migration, let's do.

flux commented 2024-02-25 18:45:47 +00:00

Member

Copy Link

without requiring a migration

i think it would require a migration, which could be handled by a very simple run-once LBM. i'll test it out and see.

> without requiring a migration i think it *would* require a migration, which could be handled by a very simple run-once LBM. i'll test it out and see.

whosit commented 2024-02-25 18:48:41 +00:00

Member

Copy Link

paramtype2 = "facedir"

    Supported drawtypes: "normal", "nodebox", "mesh"

Making a mesh shouldn't be too hard though...

``` paramtype2 = "facedir" Supported drawtypes: "normal", "nodebox", "mesh" ``` Making a mesh shouldn't be too hard though...

AliasAlreadyTaken commented 2024-02-25 19:12:28 +00:00

Owner

Copy Link

Aren't meshes the most expensive drawtype? Or does that depend on the mesh?

Aren't meshes the most expensive drawtype? Or does that depend on the mesh?

whosit commented 2024-02-25 20:18:36 +00:00

Member

Copy Link

Aren't meshes the most expensive drawtype? Or does that depend on the mesh?

I have no idea, but nodeboxes also work:

    minetest.register_node("yl_livemapping:" .. m_name .. "_ne_blank", {
        description = "Northeast " .. m_description,
        _doc_items_create_entry = false,
        drawtype = "nodebox",
        tiles = {
            "default_dirt.png",    
            "default_dirt.png",
            "default_dirt.png",
            "default_dirt.png",    
            "default_dirt.png",
            "yl_" .. m_name .. "_ne.png",
        },
        is_ground_content = false,
        inventory_image = "yl_" .. m_name .. "_ne.png",
        wield_image = "yl_" .. m_name .. "_ne.png",
        paramtype = "light",
        paramtype2 = "facedir",
        walkable = false,
        climbable = true,
        sunlight_propagates = false,
        node_box = {
            type = "fixed",
            fixed = {
                { -0.5, -0.5, (0.5 - 1 / 16), 0.5, 0.5, 0.5 }, 
            }
        },
        groups = {
            choppy = 2,
            flammable = 2
        }
        -- on_rightclick = swap_on_rightclick,
    })

> Aren't meshes the most expensive drawtype? Or does that depend on the mesh? I have no idea, but nodeboxes also work: ```lua minetest.register_node("yl_livemapping:" .. m_name .. "_ne_blank", { description = "Northeast " .. m_description, _doc_items_create_entry = false, drawtype = "nodebox", tiles = { "default_dirt.png", "default_dirt.png", "default_dirt.png", "default_dirt.png", "default_dirt.png", "yl_" .. m_name .. "_ne.png", }, is_ground_content = false, inventory_image = "yl_" .. m_name .. "_ne.png", wield_image = "yl_" .. m_name .. "_ne.png", paramtype = "light", paramtype2 = "facedir", walkable = false, climbable = true, sunlight_propagates = false, node_box = { type = "fixed", fixed = { { -0.5, -0.5, (0.5 - 1 / 16), 0.5, 0.5, 0.5 }, } }, groups = { choppy = 2, flammable = 2 } -- on_rightclick = swap_on_rightclick, }) ``` 

image.png

234 KiB

flux commented 2024-02-25 20:27:21 +00:00

Member

Copy Link

i'm already working on this. i'm still banging my head on the logic to correctly orient the map when it's placed, though.

i'm already working on this. i'm still banging my head on the logic to correctly orient the map when it's placed, though.

whosit commented 2024-02-25 20:33:42 +00:00

Member

Copy Link

i'm already working on this. i'm still banging my head on the logic to correctly orient the map when it's placed, though.

You mean, convert param2?
They seem to orient on placement ok with my definition (but always vertical)

And to convert rotations here's this:
https://github.com/minetest/minetest/blob/master/doc/lua_api.md#item-handling

> i'm already working on this. i'm still banging my head on the logic to correctly orient the map when it's placed, though. You mean, convert param2? They seem to orient on placement ok with my definition (but always vertical) And to convert rotations here's this: https://github.com/minetest/minetest/blob/master/doc/lua_api.md#item-handling

flux commented 2024-02-25 20:34:04 +00:00

Member

Copy Link

the nodebox i'm using is

{-0.5, -0.5 + (1/16), -0.5, 0.5, -0.5 + (1/16), 0.5}

using this, i can get away with only specifying one texture (no need for dirt around the edges). the map appears to "float" above the wall a little bit, but that's what they do currently.

i'm also putting the map orthogonal to the "y axis", so that rotating it with the screwdriver works sanely.

the nodebox i'm using is ```lua {-0.5, -0.5 + (1/16), -0.5, 0.5, -0.5 + (1/16), 0.5} ``` using this, i can get away with only specifying one texture (no need for dirt around the edges). the map appears to "float" above the wall a little bit, but that's what they do currently. i'm also putting the map orthogonal to the "y axis", so that rotating it with the screwdriver works sanely.

whosit commented 2024-02-25 20:42:32 +00:00

Member

Copy Link

using this, i can get away with only specifying one texture (no need for dirt around the edges). the map appears to "float" above the wall a little bit, but that's what they do currently.

I think having some material for the backing (maybe wood? cloth? paper? anything...) would look better than floating map...

i'm also putting the map orthogonal to the "y axis", so that rotating it with the screwdriver works sanely.

I see... but I always expect weirdness from screwdriver and just use rhotator, which works fine here.

> using this, i can get away with only specifying one texture (no need for dirt around the edges). the map appears to "float" above the wall a little bit, but that's what they do currently. I think having some material for the backing (maybe wood? cloth? paper? anything...) would look better than floating map... > > i'm also putting the map orthogonal to the "y axis", so that rotating it with the screwdriver works sanely. I see... but I always expect weirdness from screwdriver and just use rhotator, which works fine here.

flux commented 2024-02-26 02:58:00 +00:00

Member

Copy Link

rhotator, which works fine here.

no-one has ever been able to convince me that the rhotator is a suitable replacement for the screwdriver. if you're standing in one place,or only some faces of the node are visible, there's just no way to achieve certain results.

> rhotator, which works fine here. no-one has ever been able to convince me that the rhotator is a suitable replacement for the screwdriver. if you're standing in one place,or only some faces of the node are visible, there's just no way to achieve certain results.

flux commented 2024-02-26 02:59:25 +00:00

Member

Copy Link

I think having some material for the backing (maybe wood? cloth? paper? anything...) would look better than floating map...

i think i agree, but no-one has requested such a feature, and someone might complain, because people complain about every minor change...

> I think having some material for the backing (maybe wood? cloth? paper? anything...) would look better than floating map... i think i agree, but no-one has requested such a feature, and someone might complain, because people complain about every minor change...

AliasAlreadyTaken commented 2024-02-26 11:33:16 +00:00

Owner

Copy Link

They might have a legit usecase we haven't thought of, but We are making changes. your-land/bugtracker#3039

They might have a legit usecase we haven't thought of, but We are making changes. your-land/bugtracker#3039

Chache commented 2024-02-26 13:21:40 +00:00

Copy Link

If you'll excuse the short off-topic:

no-one has ever been able to convince me that the rhotator is a suitable replacement for the screwdriver. if you're standing in one place,or only some faces of the node are visible, there's just no way to achieve certain results.

Using only the rotating feature of the Rhotator it's not possible, but combining that with the "push closest edge" feature, all 24 combinations of a single node's position+orientation should be achievable even if there's only one face visible.

If you'll excuse the short off-topic: > no-one has ever been able to convince me that the rhotator is a suitable replacement for the screwdriver. if you're standing in one place,or only some faces of the node are visible, there's just no way to achieve certain results. Using only the rotating feature of the Rhotator it's not possible, but combining that with the "push closest edge" feature, all 24 combinations of a single node's position+orientation should be achievable even if there's only one face visible.

whosit commented 2024-02-26 13:30:29 +00:00

Member

Copy Link

Using only the rotating feature of the Rhotator it's not possible, but combining that with the "push closest edge" feature, all 24 combinations of a single node's position+orientation should be achievable even if there's only one face visible.

Does not work for nodes that don't have an edge you can push in some orientations. I don't think you can orient this thin map box with it's back to you (if only one face is accessible)

> Using only the rotating feature of the Rhotator it's not possible, but combining that with the "push closest edge" feature, all 24 combinations of a single node's position+orientation should be achievable even if there's only one face visible. Does not work for nodes that don't have an edge you can push in some orientations. I don't think you can orient this thin map box with it's back to you (if only one face is accessible)

flux referenced this issue from a commit 2024-03-04 22:32:27 +00:00

your-land/bugtracker#6347 make maps facedir so they can be rotated fully

flux commented 2024-03-04 22:35:58 +00:00

Member

Copy Link

finally got around to finishing this: 4eb6fdc656

currently the maps do not have "side" textures as in whosit's implementation. if alias approves, i could add one.

i also haven't fully tested the conversion orientations, but it's working for the main map in haven.

finally got around to finishing this: https://gitea.your-land.de/your-land/yl_livemapping/commit/4eb6fdc656f5be62612b359a0f3e231e61d8ba72 currently the maps do *not* have "side" textures as in whosit's implementation. if alias approves, i could add one. i also haven't fully tested the conversion orientations, but it's working for the main map in haven.

AliasAlreadyTaken commented 2024-03-04 22:52:41 +00:00

Owner

Copy Link

Ready for QA? :D

Ready for QA? :D

flux added the

4. step/ready to QA test

label 2024-03-08 00:57:24 +00:00

flux commented 2024-03-08 00:57:31 +00:00

Member

Copy Link

yes

yes

whosit commented 2024-03-08 18:16:20 +00:00

Member

Copy Link

Maravillosa maps got flipped

/teleport xyz 39 4 22463

Maravillosa maps got flipped  `/teleport xyz 39 4 22463`

screenshot_20240308_211445.png

590 KiB

rewired_X commented 2024-03-08 21:03:35 +00:00

Copy Link

better hope a certain soko won't mind the maps being hung by a single nail on each piece

better hope a certain soko won't mind the maps being hung by a single nail on each piece

AliasAlreadyTaken commented 2024-03-08 23:35:05 +00:00

Owner

Copy Link

Sounds like QA:NOK?

Sounds like QA:NOK?

AliasAlreadyTaken added this to the 1.1.123 milestone 2024-03-08 23:35:12 +00:00

whosit added the

ugh/QA NOK

label 2024-03-08 23:56:20 +00:00

flux commented 2024-03-09 04:48:15 +00:00

Member

Copy Link

Sounds like QA:NOK?

yes i'm gonna have to recheck the LBM. ugh. that's tedious.

> Sounds like QA:NOK? yes i'm gonna have to recheck the LBM. ugh. that's tedious.

AliasAlreadyTaken commented 2024-03-09 11:12:43 +00:00

Owner

Copy Link

QA

PdS maps as well

QA PdS maps as well 

grafik.png

452 KiB

flux commented 2024-03-09 22:40:15 +00:00

Member

Copy Link

that means the LBM wasn't even run....

testing locally, it works correctly in all directions:

and it looks fine on the test server to me currently, and has param2=17:

possibly lag and the LBM just hadn't run yet?

 that means the LBM wasn't even run.... testing locally, it works correctly in all directions:  and it looks fine on the test server to me currently, and has `param2=17`:  possibly lag and the LBM just hadn't run yet?

image.png

6.9 KiB

image.png

358 KiB

image.png

456 KiB

whosit commented 2024-03-09 22:43:24 +00:00

Member

Copy Link

I noticed those after spending lots of time there trying to figure out it's the tiny croc causing client stutter...
But server has been restarted since then, so I have no idea honestly.

I noticed those after spending lots of time there trying to figure out it's the tiny croc causing client stutter... But server has been restarted since then, so I have no idea honestly.

flux commented 2024-03-09 22:47:23 +00:00

Member

Copy Link

PdS map is still broken though... but it has param2=5, so that means the LBM also hasn't run there yet either? but it's not running while i'm sitting there looking....

PdS map is still broken though... but it has `param2=5`, so that means the LBM *also* hasn't run there yet either? but it's not running while i'm sitting there looking....

flux commented 2024-03-09 22:55:38 +00:00

Member

Copy Link

visited a number of other cities, and the maps were broken in all of them.

maybe try removing yl_livemapping:convert_to_facedir~24623515; (or whatever number you get) from $worldpath/env_meta.txt? i have no idea why the LBM might not be running.

visited a number of other cities, and the maps were broken in all of them. maybe try removing `yl_livemapping:convert_to_facedir~24623515;` (or whatever number you get) from `$worldpath/env_meta.txt`? i have no idea why the LBM might not be running.

flux referenced this issue 2024-03-10 06:01:13 +00:00

run-once LBMs don't always seem to run #6432

AliasAlreadyTaken commented 2024-03-10 15:03:46 +00:00

Owner

Copy Link

Maybe the LBM did run - twice and more? It cannot know the "correct" orientation, right?

Maybe the LBM did run - twice and more? It cannot know the "correct" orientation, right?

flux commented 2024-03-11 18:08:08 +00:00

Member

Copy Link

Maybe the LBM did run - twice and more? It cannot know the "correct" orientation, right?

it only modifies the param2 value if it's 0, 1, 2, 3, 4, or 5, and none of the resulting values are any of those, so it can be run repeatedly and still produce the same results. it's just luck that it worked out like that.

> Maybe the LBM did run - twice and more? It cannot know the "correct" orientation, right? it only modifies the param2 value if it's 0, 1, 2, 3, 4, or 5, and none of the resulting values are any of those, so it can be run repeatedly and still produce the same results. it's just luck that it worked out like that.

AliasAlreadyTaken removed the

ugh/QA NOK

label 2024-03-12 02:00:11 +00:00

AliasAlreadyTaken commented 2024-03-12 02:31:44 +00:00

Owner

Copy Link

QA

No way. proverb of my grandfather: "Wenn mans richtig macht, dann funktionierts auch."

More or less: "If you do it right, it works."

QA No way. proverb of my grandfather: "Wenn mans richtig macht, dann funktionierts auch." More or less: "If you do it right, it works."

AliasAlreadyTaken added the

ugh/QA OK

label 2024-03-12 02:31:55 +00:00

flux removed the

4. step/ready to QA test

label 2024-03-28 22:50:08 +00:00

AliasAlreadyTaken was unassigned by flux 2024-03-28 22:50:11 +00:00

flux commented 2024-03-28 22:50:21 +00:00

Member

Copy Link

live

live

flux closed this issue 2024-03-28 22:50:21 +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

1.1.123

Projects

Clear projects

No project

Assignees

Clear assignees

No Assignees

6 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#6347

No description provided.