your-land/bugtracker
your-land
/
bugtracker
44
20
Code Issues 2.5k Projects 2 Wiki

johanlegend reports: someone stole my items from th ... #4254

New Issue
Closed
opened 2023-04-24 14:25:05 +00:00 by yourland-report · 19 comments
yourland-report commented 2023-04-24 14:25:05 +00:00
Member
Copy Link

johanlegend reports a bug:

someone stole my items from these two conatiners: chest and table saw. Using Sherlock tool, I know STEALTH opened them, and the chest are not private chest but this is a protected area, restricted by walls, so that players should have no access to here in the first place, let alone taking whatever items they took.

Player position:

{
	x = 2884.5490722656,
	y = -30591.5,
	z = 326.02700805664
}

Player look:

{
	x = -0.89647567272186,
	y = -0.43475961685181,
	z = 0.085530534386635
}

Player information:

{
	min_jitter = 0,
	max_rtt = 12.312000274658,
	avg_jitter = 0.0040000006556511,
	connection_uptime = 11903,
	serialization_version = 29,
	patch = 0,
	minor = 7,
	formspec_version = 6,
	state = "Active",
	version_string = "5.7.0",
	major = 5,
	protocol_version = 41,
	lang_code = "",
	max_jitter = 10.251000404358,
	ip_version = 6,
	min_rtt = 0.026000000536442,
	avg_rtt = 0.030999999493361
}

Player meta:

{
	fields = {
		inflicted_damage = "1442360",
		["unified_inventory:bags"] = "return {\"unified_inventory:bag_large\", \"unified_inventory:bag_large\", \"unified_inventory:bag_large\", \"unified_inventory:bag_large\"}",
		["ocean_build.last_warning"] = "1.68072e+09",
		["ocean_build.ocean_built"] = "7",
		["3d_armor_inventory"] = "return {\"3d_armor:helmet_rainbow 1 1864\", \"shields:shield_rainbow 1 1864\", \"3d_armor:enchanted_chestplate_mithril_strong 1 3262\", \"3d_armor:enchanted_leggings_mithril_strong 1 3262\", \"\", \"3d_armor:boots_crystal 1 4660\"}",
		placed_nodes = "70437",
		jointime = "1673610096",
		xp = "513761",
		["stamina:poisoned"] = "no",
		repellant = "0",
		yl_church = "return {[\"last_death_portal\"] = 1682344003, [\"last_heal\"] = 1676836695, [\"last_death\"] = {[\"x\"] = 2885, [\"y\"] = -30592, [\"z\"] = 326}}",
		punch_count = "67923",
		yl_commons_thankyou = "30",
		["stamina:level"] = "17",
		bitten = "0",
		played_time = "1381092",
		digged_nodes = "400448",
		["stamina:exhaustion"] = "111",
		died = "47",
		yl_commons_player_created = "1673610096",
		crafted = "3119",
		partychat = "party",
		yl_commons_player_joined = "1682334427",
		["signslib:pos"] = "(3049,123,414)",
		hud_state = "on",
		arenalib_infobox_arenaID = "0"
	}
}

Log identifier


[MOD] yl_report log identifier = LizG4cHPaHMEzzwj8nZLOqZDjHTBP94l

Profiler save:

profile-20230424T142505.json_prettyEE

Status:

# Server: version: 5.6.1-yl | game: Minetest Game | uptime: 21h 38min 34s | max lag: 0.736s | clients (24/52): AliasAlreadyTaken, Aliza, Atianos, Bailiff, Balrog_Dude, daydream, drgn, Flippster, flux, johanlegend, luna2000, Lupercus, mahou, MilOOOOO, MineWorlds, Murmel, Prismatim, rewired_X, Service, shanish3, sherkhan30452, sume, Sybil, Sysmatic

Teleport command:

/teleport xyz 2885 -30592 326

Compass command:

/give_compass Construction LizG4cHPaHMEzzwj8nZLOqZDjHTBP94l D2691E 2885 -30592 326
johanlegend reports a bug: > someone stole my items from these two conatiners: chest and table saw. Using Sherlock tool, I know STEALTH opened them, and the chest are not private chest but this is a protected area, restricted by walls, so that players should have no access to here in the first place, let alone taking whatever items they took. Player position: ``` { x = 2884.5490722656, y = -30591.5, z = 326.02700805664 } ``` Player look: ``` { x = -0.89647567272186, y = -0.43475961685181, z = 0.085530534386635 } ``` Player information: ``` { min_jitter = 0, max_rtt = 12.312000274658, avg_jitter = 0.0040000006556511, connection_uptime = 11903, serialization_version = 29, patch = 0, minor = 7, formspec_version = 6, state = "Active", version_string = "5.7.0", major = 5, protocol_version = 41, lang_code = "", max_jitter = 10.251000404358, ip_version = 6, min_rtt = 0.026000000536442, avg_rtt = 0.030999999493361 } ``` Player meta: ``` { fields = { inflicted_damage = "1442360", ["unified_inventory:bags"] = "return {\"unified_inventory:bag_large\", \"unified_inventory:bag_large\", \"unified_inventory:bag_large\", \"unified_inventory:bag_large\"}", ["ocean_build.last_warning"] = "1.68072e+09", ["ocean_build.ocean_built"] = "7", ["3d_armor_inventory"] = "return {\"3d_armor:helmet_rainbow 1 1864\", \"shields:shield_rainbow 1 1864\", \"3d_armor:enchanted_chestplate_mithril_strong 1 3262\", \"3d_armor:enchanted_leggings_mithril_strong 1 3262\", \"\", \"3d_armor:boots_crystal 1 4660\"}", placed_nodes = "70437", jointime = "1673610096", xp = "513761", ["stamina:poisoned"] = "no", repellant = "0", yl_church = "return {[\"last_death_portal\"] = 1682344003, [\"last_heal\"] = 1676836695, [\"last_death\"] = {[\"x\"] = 2885, [\"y\"] = -30592, [\"z\"] = 326}}", punch_count = "67923", yl_commons_thankyou = "30", ["stamina:level"] = "17", bitten = "0", played_time = "1381092", digged_nodes = "400448", ["stamina:exhaustion"] = "111", died = "47", yl_commons_player_created = "1673610096", crafted = "3119", partychat = "party", yl_commons_player_joined = "1682334427", ["signslib:pos"] = "(3049,123,414)", hud_state = "on", arenalib_infobox_arenaID = "0" } } ``` Log identifier ``` [MOD] yl_report log identifier = LizG4cHPaHMEzzwj8nZLOqZDjHTBP94l ``` Profiler save: ``` profile-20230424T142505.json_prettyEE ``` Status: ``` # Server: version: 5.6.1-yl | game: Minetest Game | uptime: 21h 38min 34s | max lag: 0.736s | clients (24/52): AliasAlreadyTaken, Aliza, Atianos, Bailiff, Balrog_Dude, daydream, drgn, Flippster, flux, johanlegend, luna2000, Lupercus, mahou, MilOOOOO, MineWorlds, Murmel, Prismatim, rewired_X, Service, shanish3, sherkhan30452, sume, Sybil, Sysmatic ``` Teleport command: ``` /teleport xyz 2885 -30592 326 ``` Compass command: ``` /give_compass Construction LizG4cHPaHMEzzwj8nZLOqZDjHTBP94l D2691E 2885 -30592 326 ```
AliasAlreadyTaken was assigned by yourland-report 2023-04-24 14:25:05 +00:00
johanlegend commented 2023-04-24 14:27:38 +00:00
Copy Link

Notice: What are those "(0,0,0)" entries by the way?

[2023-04-24T13:50:19] player:johanlegend:  =>  at (0,0,0)
[2023-04-24T13:50:19] player:johanlegend:  =>  at (0,0,0)
[2023-04-24T13:44:41] player:johanlegend: air => bones:bones at (2885,-30591,326)
[2023-04-24T00:49:26] player:STEALTH: default:chest_open => default:chest at (2883,-30591,325)
[2023-04-24T00:49:24] player:STEALTH: default:chest => default:chest_open at (2883,-30591,325)
[2023-04-24T00:49:10] player:STEALTH: default:chest_open => default:chest at (2883,-30591,325)
[2023-04-24T00:49:09] player:STEALTH:  =>  at (0,0,0)
[2023-04-24T00:49:08] player:STEALTH:  =>  at (0,0,0)
[2023-04-24T00:49:07] player:STEALTH:  =>  at (0,0,0)
[2023-04-24T00:49:06] player:STEALTH:  =>  at (0,0,0)
[2023-04-24T00:49:05] player:STEALTH:  =>  at (0,0,0)
[2023-04-24T00:49:04] player:STEALTH:  =>  at (0,0,0)
[2023-04-24T00:49:03] player:STEALTH:  =>  at (0,0,0)
[2023-04-24T00:49:02] player:STEALTH:  =>  at (0,0,0)
[2023-04-24T00:49:02] player:STEALTH:  =>  at (0,0,0)
[2023-04-24T00:49:01] player:STEALTH:  =>  at (0,0,0)
[2023-04-24T00:49:00] player:STEALTH:  =>  at (0,0,0)
[2023-04-24T00:48:59] player:STEALTH:  =>  at (0,0,0)
[2023-04-24T00:48:57] player:STEALTH: default:chest => default:chest_open at (2883,-30591,325)
[2023-04-24T00:48:31] player:STEALTH: default:chest_open => default:chest at (2883,-30591,325)
[2023-04-24T00:48:30] player:STEALTH:  =>  at (0,0,0)
[2023-04-24T00:48:29] player:STEALTH:  =>  at (0,0,0)
[2023-04-24T00:48:28] player:STEALTH:  =>  at (0,0,0)
Notice: What are those "(0,0,0)" entries by the way? ``` [2023-04-24T13:50:19] player:johanlegend: => at (0,0,0) [2023-04-24T13:50:19] player:johanlegend: => at (0,0,0) [2023-04-24T13:44:41] player:johanlegend: air => bones:bones at (2885,-30591,326) [2023-04-24T00:49:26] player:STEALTH: default:chest_open => default:chest at (2883,-30591,325) [2023-04-24T00:49:24] player:STEALTH: default:chest => default:chest_open at (2883,-30591,325) [2023-04-24T00:49:10] player:STEALTH: default:chest_open => default:chest at (2883,-30591,325) [2023-04-24T00:49:09] player:STEALTH: => at (0,0,0) [2023-04-24T00:49:08] player:STEALTH: => at (0,0,0) [2023-04-24T00:49:07] player:STEALTH: => at (0,0,0) [2023-04-24T00:49:06] player:STEALTH: => at (0,0,0) [2023-04-24T00:49:05] player:STEALTH: => at (0,0,0) [2023-04-24T00:49:04] player:STEALTH: => at (0,0,0) [2023-04-24T00:49:03] player:STEALTH: => at (0,0,0) [2023-04-24T00:49:02] player:STEALTH: => at (0,0,0) [2023-04-24T00:49:02] player:STEALTH: => at (0,0,0) [2023-04-24T00:49:01] player:STEALTH: => at (0,0,0) [2023-04-24T00:49:00] player:STEALTH: => at (0,0,0) [2023-04-24T00:48:59] player:STEALTH: => at (0,0,0) [2023-04-24T00:48:57] player:STEALTH: default:chest => default:chest_open at (2883,-30591,325) [2023-04-24T00:48:31] player:STEALTH: default:chest_open => default:chest at (2883,-30591,325) [2023-04-24T00:48:30] player:STEALTH: => at (0,0,0) [2023-04-24T00:48:29] player:STEALTH: => at (0,0,0) [2023-04-24T00:48:28] player:STEALTH: => at (0,0,0) ```
johanlegend commented 2023-04-24 14:28:37 +00:00
Copy Link

I wonder how to restrict players from coming into my area that is not intended to be seen by others.

I wonder how to restrict players from coming into my area that is not intended to be seen by others.
daydream commented 2023-04-24 15:49:31 +00:00
Member
Copy Link

You could try area ban for sure, but reporting players that glitch into protected areas puts them in jail immediately (especially if it's the SECOND time they've done it and already been warned) and repeated offences after that lead straight to bans for obstinance and disregard for the one server rule. So issue should not persist.

I will do a /bug suggest for a wildcard /area_ban PlayerName and /area_unban PlayerName

Maybe they could work with wildcard /area_ban all

something like that - probably not because even if the command grabbed all playernames and added them there could be new players on the server and it wouldn't be able to auto-update and add them also. Probably a lost cause but brings up an interesting concept anyways.

You could try area ban for sure, but reporting players that glitch into protected areas puts them in jail immediately (especially if it's the SECOND time they've done it and already been warned) and repeated offences after that lead straight to bans for obstinance and disregard for the one server rule. So issue should not persist. I will do a /bug suggest for a wildcard /area_ban PlayerName and /area_unban PlayerName Maybe they could work with wildcard /area_ban all something like that - probably not because even if the command grabbed all playernames and added them there could be new players on the server and it wouldn't be able to auto-update and add them also. Probably a lost cause but brings up an interesting concept anyways.
daydream commented 2023-04-24 15:56:25 +00:00
Member
Copy Link

See report #577 for further on disciplinary action.

See report [#577](https://gitea.your-land.de/your-land/reports/issues/577) for further on disciplinary action.
flux commented 2023-04-24 16:39:10 +00:00
Member
Copy Link

What are those "(0,0,0)" entries by the way?

that's how the rollback log shows that items were put into or removed from the chest. not very useful, huh? the main server log will show what exactly was taken.

I wonder how to restrict players from coming into my area that is not intended to be seen by others.

i'm guessing that STEALTH got over the wall by using the "place a node and jump on it before it disappears" glitch. he's on mobile, which apparently makes that much easier. he's demonstrated that he's able to do that by getting on top of the bunny maze in haven.

it's possible to ban a specific player from your area using the /area_ban command; perhaps we need to implement something similar that'd ban anyone (excluding staff) who's not added to the area.

> What are those "(0,0,0)" entries by the way? that's how the rollback log shows that items were put into or removed from the chest. not very useful, huh? the main server log will show what exactly was taken. > I wonder how to restrict players from coming into my area that is not intended to be seen by others. i'm guessing that STEALTH got over the wall by using the "place a node and jump on it before it disappears" glitch. he's on mobile, which apparently makes that much easier. he's demonstrated that he's able to do that by getting on top of the bunny maze in haven. it's possible to ban a *specific* player from your area using the `/area_ban` command; perhaps we need to implement something similar that'd ban *anyone* (excluding staff) who's not added to the area.
👍 2
sixer commented 2023-04-24 19:50:31 +00:00
Copy Link

perhaps we need to implement something similar that'd ban anyone (excluding staff) who's not added to the area.

This has a potential to be abused to troll by protecting some important area (like in middle of path for miocene move) and denying everybody right to passage. I'd be careful with implementing such measure, think about unintended applications and perhaps mitigate them, for example by requiring admin-approval for general area ban.

> perhaps we need to implement something similar that'd ban *anyone* (excluding staff) who's not added to the area. This has a potential to be abused to troll by protecting some important area (like in middle of path for miocene move) and denying everybody right to passage. I'd be careful with implementing such measure, think about unintended applications and perhaps mitigate them, for example by requiring admin-approval for general area ban.
👍 1
flux commented 2023-04-24 20:06:13 +00:00
Member
Copy Link

perhaps we need to implement something similar that'd ban anyone (excluding staff) who's not added to the area.

This has a potential to be abused to troll by protecting some important area (like in middle of path for miocene move) and denying everybody right to passage. I'd be careful with implementing such measure, think about unintended applications and perhaps mitigate them, for example by requiring admin-approval for general area ban.

someone could already create such a troll area and ban common miocene movers, using existing mechanics. that's a social issue, and server staff will deal w/ it as such.

the request for secure private areas is a common one. cf. #1378, #2365, #3143

> > perhaps we need to implement something similar that'd ban *anyone* (excluding staff) who's not added to the area. > > This has a potential to be abused to troll by protecting some important area (like in middle of path for miocene move) and denying everybody right to passage. I'd be careful with implementing such measure, think about unintended applications and perhaps mitigate them, for example by requiring admin-approval for general area ban. someone could already create such a troll area and ban common miocene movers, using existing mechanics. that's a social issue, and server staff will deal w/ it as such. the request for secure private areas is a common one. cf. #1378, #2365, #3143
niceride commented 2023-04-25 16:41:42 +00:00
Copy Link

it's possible to ban a specific player from your area using the /area_ban command; perhaps we need to implement something similar that'd ban anyone (excluding staff) who's not added to the area.

This should be done with guild/faction semantics; Ban anyone who is not in the named guild/faction from entering, and if you don't have a specific guild/faction intended for that situation then a nil guild '' or lack of name will do the same as intended to keep other players out. We don't have guild/faction yet but that's how it would fit in to the area commands (when there is guild/faction support) I think?

> it's possible to ban a *specific* player from your area using the `/area_ban` command; perhaps we need to implement something similar that'd ban *anyone* (excluding staff) who's not added to the area. This should be done with guild/faction semantics; Ban anyone who is not in the named guild/faction from entering, and if you don't have a specific guild/faction intended for that situation then a nil guild '' or lack of name will do the same as intended to keep other players out. We don't have guild/faction yet but that's how it would fit in to the area commands (when there is guild/faction support) I think?
AliasAlreadyTaken added the
1. kind/enhancement
 label 2023-04-26 05:32:58 +00:00
AliasAlreadyTaken commented 2023-04-26 05:35:01 +00:00
Owner
Copy Link

We already have a ban mechanic and I'd like to add a "ban all except owner"

We already have a ban mechanic and I'd like to add a "ban all except owner"
sixer commented 2023-04-27 08:30:20 +00:00
Copy Link

If "ban everybody" would be easily available, it will likely get overused - i.e. ban would be useful to protect 20x20 house in the wild, but entire area 64x64 would likely receive it, with negative consequences if you settle near a road, tight mountain passage or alike (and, as a side effect, it could make trolling much easier, not sure if there is any other way that could easily block everybody from an arbitrary 64x64 area).

If "ban everybody" would be easily available, it will likely get overused - i.e. ban would be useful to protect 20x20 house in the wild, but entire area 64x64 would likely receive it, with negative consequences if you settle near a road, tight mountain passage or alike (and, as a side effect, it could make trolling much easier, not sure if there is any other way that could easily block everybody from an arbitrary 64x64 area).
👍 1
flux added the
2. prio/elevated
4. step/discussion
 labels 2023-04-29 01:09:23 +00:00
flux added this to the flux's TODO list project 2023-04-29 14:59:56 +00:00
johanlegend commented 2023-05-01 13:16:27 +00:00
Copy Link

i'm guessing that STEALTH got over the wall by using the "place a node and jump on it before it disappears" glitch. he's on mobile, which apparently makes that much easier. he's demonstrated that he's able to do that by getting on top of the bunny maze in haven.

I've had a friendly conversation with him and he was really helpful, even wanted to give things back (which i refused because someone told the missing items would be restored eventually and then I would have the items twice.) I still don't think he would deserve a ban only for this one incident. (I know there supposed to be others but that's not of my concern.) The real setback was that I almost missed the build project deadline because of the missing materials, but I found a way to complete it anyways.

He revealed the trick: quickly dig 2 blocks on the wall and run past the hole real fast, before the protection mechanics replaced the removed blocks. (He thought the wall was fill height up until the ceiling.) I describe this here in case someone possibly wanted to fix that loophole.

> > i'm guessing that STEALTH got over the wall by using the "place a node and jump on it before it disappears" glitch. he's on mobile, which apparently makes that much easier. he's demonstrated that he's able to do that by getting on top of the bunny maze in haven. > I've had a friendly conversation with him and he was really helpful, even wanted to give things back (which i refused because someone told the missing items would be restored eventually and then I would have the items twice.) I still don't think he would deserve a ban only for this one incident. (I know there supposed to be others but that's not of my concern.) The real setback was that I almost missed the build project deadline because of the missing materials, but I found a way to complete it anyways. He revealed the trick: quickly dig 2 blocks on the wall and run past the hole real fast, before the protection mechanics replaced the removed blocks. (He thought the wall was fill height up until the ceiling.) I describe this here in case someone possibly wanted to fix that loophole.
johanlegend commented 2023-05-22 06:53:35 +00:00
Copy Link

See report #577 for further on disciplinary action.

That's Error 404 (not found or I have no access rights to read it)

> See report [#577](https://gitea.your-land.de/your-land/reports/issues/577) for further on disciplinary action. > That's Error 404 (not found or I have no access rights to read it)
johanlegend commented 2023-05-22 06:58:19 +00:00
Copy Link

Is there a way to restore the contents of the chest and table saw before the incident?

I'm not even sure what was in them but I could use them in future constructions.

Is there a way to restore the contents of the chest and table saw before the incident? I'm not even sure what was in them but I could use them in future constructions.
AliasAlreadyTaken commented 2023-05-22 16:33:17 +00:00
Owner
Copy Link

See report #577 for further on disciplinary action.

That's Error 404 (not found or I have no access rights to read it)

Reports against people are not public, that's why you can't see it.

If we refund the items, they will exist two times in the game.

If STEALTH wants to help, he should give the items back.

> > See report [#577](https://gitea.your-land.de/your-land/reports/issues/577) for further on disciplinary action. > > > > That's Error 404 (not found or I have no access rights to read it) Reports against people are not public, that's why you can't see it. If we refund the items, they will exist two times in the game. If STEALTH wants to help, he should give the items back.
johanlegend commented 2023-05-22 20:53:00 +00:00
Copy Link

You can delete the items from his inventory so it would not be duplicated.

Without seeing the logs I can't even know what went missing. Is this the state of law and order in Your Land? Stolen items can be given back IF and ONLY if the thief wants to help? This feels deeply unjust.

Some staiff/bailiff said to me not to worry because noone can be stripped in this server from the items that is rightfully theirs. Seems like I should start to worry now...

You can delete the items from his inventory so it would not be duplicated. Without seeing the logs I can't even know what went missing. Is this the state of law and order in Your Land? Stolen items can be given back IF and ONLY if the thief wants to help? This feels deeply unjust. Some staiff/bailiff said to me not to worry because noone can be stripped in this server from the items that is rightfully theirs. Seems like I should start to worry now...
AliasAlreadyTaken commented 2023-05-22 21:08:50 +00:00
Owner
Copy Link

You can delete the items from his inventory so it would not be duplicated.

Without seeing the logs I can't even know what went missing. Is this the state of law and order in Your Land? Stolen items can be given back IF and ONLY if the thief wants to help? This feels deeply unjust.

Since STEALTH offered to help, I assumed he'd still want to. If he does not or want to keep the items just "because he can't remember", then we'll need to take the items off of him. I'd rather have him return the stuff and properly apologize than a staff action.

Some staiff/bailiff said to me not to worry because noone can be stripped in this server from the items that is rightfully theirs. Seems like I should start to worry now...

No. those items are yours and they will return to you one way or another.

> You can delete the items from his inventory so it would not be duplicated. > > Without seeing the logs I can't even know what went missing. Is this the state of law and order in Your Land? Stolen items can be given back IF and ONLY if the thief wants to help? This feels deeply unjust. Since STEALTH offered to help, I assumed he'd still want to. If he does not or want to keep the items just "because he can't remember", then we'll need to take the items off of him. I'd rather have him return the stuff and properly apologize than a staff action. > Some staiff/bailiff said to me not to worry because noone can be stripped in this server from the items that is rightfully theirs. Seems like I should start to worry now... No. those items are yours and they will return to you one way or another.
johanlegend commented 2023-05-22 21:17:19 +00:00
Copy Link

OK, I understand the idea, but I think we can't reasonably expect him to remember every single item in the chest and the table saw he took. Then again, even if he still wants to give back how can we be sure everything got returned? What would you do to solve this?

OK, I understand the idea, but I think we can't reasonably expect him to remember every single item in the chest and the table saw he took. Then again, even if he still wants to give back how can we be sure everything got returned? What would you do to solve this?
AliasAlreadyTaken commented 2023-05-22 21:53:58 +00:00
Owner
Copy Link

Next to every item movement is logged, so we can find what's going on.

The items were refunded, let's discuss the "area ban" feature elsewhere: #4578

Next to every item movement is logged, so we can find what's going on. The items were refunded, let's discuss the "area ban" feature elsewhere: #4578
AliasAlreadyTaken added the
5. result/fixed
 label 2023-05-22 21:57:03 +00:00
johanlegend commented 2023-05-23 00:01:03 +00:00
Copy Link

Next to every item movement is logged, so we can find what's going on.

The items were refunded, let's discuss the "area ban" feature elsewhere: #4578

Thank you!

> Next to every item movement is logged, so we can find what's going on. > > The items were refunded, let's discuss the "area ban" feature elsewhere: #4578 Thank you!
flux removed this from the flux's TODO list project 2023-12-22 20:13:34 +00:00
AliasAlreadyTaken was unassigned by flux 2023-12-22 20:13:36 +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
Assignees
Clear assignees
No Assignees
7 Participants
Notifications
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#4254
No description provided.
Delete Branch "%!s(<nil>)"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?