AliasAlreadyTaken reports: Clean up North Haven ... #4877

New Issue

yourland-report · 2023-07-02T07:43:31Z

yourland-report commented

2023-07-02 07:43:31 +00:00

AliasAlreadyTaken reports a bug:

Clean up North Haven

Player position:

{
	y = 20.5,
	z = 1640.4260253906,
	x = 2060.5729980469
}

Player look:

{
	y = -0.29454070329666,
	z = -0.95562493801117,
	x = 0.0051715457811952
}

Player information:

{
	formspec_version = 6,
	lang_code = "de",
	protocol_version = 42,
	ip_version = 6,
	min_rtt = 0.01799999922514,
	avg_rtt = 0.050999999046326,
	min_jitter = 0,
	max_jitter = 0.61699998378754,
	avg_jitter = 0.031999997794628,
	connection_uptime = 29578,
	patch = 0,
	state = "Active",
	version_string = "5.8.0-yl_dev-ff498fc20",
	max_rtt = 0.63800001144409,
	serialization_version = 29,
	major = 5,
	minor = 8
}

Player meta:

{
	fields = {
		["stamina:level"] = "0",
		xp = "0",
		["stamina:poisoned"] = "no",
		["stamina:exhaustion"] = "90.5",
		hud_state = "on",
		digged_nodes = "140060",
		placed_nodes = "180861",
		died = "1590",
		crafted = "4779",
		yl_commons_player_joined = "1688254240",
		["signslib:pos"] = "(2134,16,1298)",
		["petz:old_override_table"] = "return {[\"speed\"] = 1, [\"new_move\"] = true, [\"sneak_glitch\"] = false, [\"gravity\"] = 1, [\"jump\"] = 1, [\"sneak\"] = true}",
		["arena_lib_editor.players_number"] = "0",
		["petz:werewolf_clan_idx"] = "4",
		["arena_lib_editor.team_ID"] = "0",
		["unified_inventory:bags"] = "return {\"unified_inventory:bag_large\", \"unified_inventory:bag_large\", \"unified_inventory:bag_large\", \"unified_inventory:bag_large\"}",
		repellant = "0",
		lagometer = "1",
		xp_redo_hud_color = "0xFFFF00",
		szutil_watch = "return {}",
		["arena_lib_editor.spawner_ID"] = "0",
		["ocean_build.ocean_built"] = "12",
		arenalib_watchID = "0",
		["petz:werewolf_vignette_id"] = "19",
		["ocean_build.last_warning"] = "1.67421e+09",
		["petz:werewolf"] = "0",
		arenalib_infobox_arenaID = "0",
		yl_church = "return {[\"last_death\"] = {[\"z\"] = 1710, [\"x\"] = 2032, [\"y\"] = 34}, [\"last_death_portal\"] = 1683839371, [\"last_heal\"] = 1683837139}",
		yl_audio_state = "off",
		["ethereal:fly_timer"] = "-99",
		bitten = "0",
		punch_count = "64320",
		partychat = "party",
		inflicted_damage = "2886200",
		team = "STAFF",
		played_time = "84852131",
		["3d_armor_inventory"] = "return {\"\", \"\", \"\", \"\", \"\", \"\"}",
		yl_commons_thankyou = "1077",
		["sethome:home"] = "(1983.4349365234,17.5,1183.5950927734)",
		["petz:lycanthropy"] = "0",
		["ocean_build.forbidden"] = "true"
	}
}

Log identifier


[MOD] yl_report log identifier = t2l1P6TELmiNm1GRGYeDXa7WojMGhuhH

Profiler save:

profile-20230702T074331.json_prettyEE

Status:

# Server: version: 5.7.0-yl-thx-tmm | game: Minetest Game | uptime: 2d 23h 53min 48s | max lag: 0.675s | clients (22/52): AliasAlreadyTaken, axotot1, Azelf, Bailiff, Bond007, Boot, daydream, flux, Giacomo_Herobrain, HorusDamocles, IVARDI, LadyPixels, Mario84, MicaelStarfire, Murmel, NodeBreaker, Penelopee, Rasanu, Service, set, Shadow, Sysmatic

Teleport command:

/teleport xyz 2061 21 1640

Compass command:

/give_compass Construction t2l1P6TELmiNm1GRGYeDXa7WojMGhuhH D2691E 2061 21 1640

AliasAlreadyTaken reports a bug: > Clean up North Haven Player position: ``` { y = 20.5, z = 1640.4260253906, x = 2060.5729980469 } ``` Player look: ``` { y = -0.29454070329666, z = -0.95562493801117, x = 0.0051715457811952 } ``` Player information: ``` { formspec_version = 6, lang_code = "de", protocol_version = 42, ip_version = 6, min_rtt = 0.01799999922514, avg_rtt = 0.050999999046326, min_jitter = 0, max_jitter = 0.61699998378754, avg_jitter = 0.031999997794628, connection_uptime = 29578, patch = 0, state = "Active", version_string = "5.8.0-yl_dev-ff498fc20", max_rtt = 0.63800001144409, serialization_version = 29, major = 5, minor = 8 } ``` Player meta: ``` { fields = { ["stamina:level"] = "0", xp = "0", ["stamina:poisoned"] = "no", ["stamina:exhaustion"] = "90.5", hud_state = "on", digged_nodes = "140060", placed_nodes = "180861", died = "1590", crafted = "4779", yl_commons_player_joined = "1688254240", ["signslib:pos"] = "(2134,16,1298)", ["petz:old_override_table"] = "return {[\"speed\"] = 1, [\"new_move\"] = true, [\"sneak_glitch\"] = false, [\"gravity\"] = 1, [\"jump\"] = 1, [\"sneak\"] = true}", ["arena_lib_editor.players_number"] = "0", ["petz:werewolf_clan_idx"] = "4", ["arena_lib_editor.team_ID"] = "0", ["unified_inventory:bags"] = "return {\"unified_inventory:bag_large\", \"unified_inventory:bag_large\", \"unified_inventory:bag_large\", \"unified_inventory:bag_large\"}", repellant = "0", lagometer = "1", xp_redo_hud_color = "0xFFFF00", szutil_watch = "return {}", ["arena_lib_editor.spawner_ID"] = "0", ["ocean_build.ocean_built"] = "12", arenalib_watchID = "0", ["petz:werewolf_vignette_id"] = "19", ["ocean_build.last_warning"] = "1.67421e+09", ["petz:werewolf"] = "0", arenalib_infobox_arenaID = "0", yl_church = "return {[\"last_death\"] = {[\"z\"] = 1710, [\"x\"] = 2032, [\"y\"] = 34}, [\"last_death_portal\"] = 1683839371, [\"last_heal\"] = 1683837139}", yl_audio_state = "off", ["ethereal:fly_timer"] = "-99", bitten = "0", punch_count = "64320", partychat = "party", inflicted_damage = "2886200", team = "STAFF", played_time = "84852131", ["3d_armor_inventory"] = "return {\"\", \"\", \"\", \"\", \"\", \"\"}", yl_commons_thankyou = "1077", ["sethome:home"] = "(1983.4349365234,17.5,1183.5950927734)", ["petz:lycanthropy"] = "0", ["ocean_build.forbidden"] = "true" } } ``` Log identifier ``` [MOD] yl_report log identifier = t2l1P6TELmiNm1GRGYeDXa7WojMGhuhH ``` Profiler save: ``` profile-20230702T074331.json_prettyEE ``` Status: ``` # Server: version: 5.7.0-yl-thx-tmm | game: Minetest Game | uptime: 2d 23h 53min 48s | max lag: 0.675s | clients (22/52): AliasAlreadyTaken, axotot1, Azelf, Bailiff, Bond007, Boot, daydream, flux, Giacomo_Herobrain, HorusDamocles, IVARDI, LadyPixels, Mario84, MicaelStarfire, Murmel, NodeBreaker, Penelopee, Rasanu, Service, set, Shadow, Sysmatic ``` Teleport command: ``` /teleport xyz 2061 21 1640 ``` Compass command: ``` /give_compass Construction t2l1P6TELmiNm1GRGYeDXa7WojMGhuhH D2691E 2061 21 1640 ```

🎉 1 🚀 1

AliasAlreadyTaken was assigned by yourland-report

2023-07-02 07:43:31 +00:00

AliasAlreadyTaken added the

1. kind/construction

3. source/ingame

labels 2023-07-02 08:42:19 +00:00

AliasAlreadyTaken commented

2023-07-02 09:22:05 +00:00

Redesign Public Nether Portal
Extend road that goes by Nether portal along the blue fires, with exit somewhere lower
Store and remove Lour Yand's house #3990
Remove and renaturize HorusDamocle's area 2903
Review underground
Determine "legal status" of daydream's mall and what's around it
Remove all areas that were objected to
Store and remove livio's/BTS-'s base #2879
Hand over addiii's area 195 to either Glowark or Bishiro
Restore adr's area from backup 781
Move or store and remove Shadow's area and Laylem's hospital
Store and remove WAR_IS_AWESOME's ocean base 3065
Store and remove herohunter's ocean base 2122
Determine precedence of areas of Shadow, daydream, Peackachew, hmm, Catenjoyer, Jackcity
To note, Giuseppe+, glyman's, Sheepyfire's and JustShapesAndBeat's areas were added before the distance rules came into effect
Remove all personal blocks from Kuno's cave 322 entrance and renaturize
Determine mapblock footprint for ThinkSome's base 114
Fill in all the private and abandoned dropshafts people dug anywhere
Secure access or decide on removal of admin area 60 below "greek temple"
Fill in rabbit burrow underground

* [ ] Redesign Public Nether Portal * [x] Extend road that goes by Nether portal along the blue fires, with exit somewhere lower * [x] Store and remove Lour Yand's house #3990 * [x] Remove and renaturize HorusDamocle's area 2903 * [ ] Review underground * [x] Determine "legal status" of daydream's mall and what's around it * [ ] Remove all areas that were objected to * [x] Store and remove livio's/BTS-'s base #2879 * [ ] Hand over addiii's area 195 to either Glowark or Bishiro * [x] Restore adr's area from backup 781 * [ ] Move or store and remove Shadow's area and Laylem's hospital * [x] Store and remove WAR_IS_AWESOME's ocean base 3065 * [x] Store and remove herohunter's ocean base 2122 * [ ] Determine precedence of areas of Shadow, daydream, Peackachew, hmm, Catenjoyer, Jackcity * [x] To note, Giuseppe+, glyman's, Sheepyfire's and JustShapesAndBeat's areas were added before the distance rules came into effect * [ ] Remove all personal blocks from Kuno's cave 322 entrance and renaturize * [ ] Determine mapblock footprint for ThinkSome's base 114 * [ ] Fill in all the private and abandoned dropshafts people dug anywhere * [x] Secure access or decide on removal of admin area 60 below "greek temple" * [ ] Fill in rabbit burrow underground

AliasAlreadyTaken commented

2023-07-02 12:36:27 +00:00

12 and 13:

2023-07-02-northhaven-war_is_awesome
2023-07-02-havennorth-herohunter

12 and 13: ``` 2023-07-02-northhaven-war_is_awesome 2023-07-02-havennorth-herohunter ```

AliasAlreadyTaken commented

2023-07-02 13:40:11 +00:00

16:

!! Remove !!
all owned chests, anvils and blocks

Deadline: 15.8.2023

16: ``` !! Remove !! all owned chests, anvils and blocks Deadline: 15.8.2023 ```

AliasAlreadyTaken commented

2023-07-12 06:24:59 +00:00

17: ThinkSome's base has a mapblock footprint of 11 MB. Given that ThinkSome does not play here anymore, since more than two years and most likely doesn't intend to, let's send him an email and store and remove the base. Still, he has a right to this place, since it predates the area distances rules and if he actively starts playing again, we'll insert it back to where it was.

👍 1

AliasAlreadyTaken commented

2023-07-12 08:43:51 +00:00

2: Road will not be built, I removed the marker fire and shut the tunnel

👍 1

niceride commented

2023-07-14 00:53:38 +00:00

Comment removed 1/2.

niceride commented

2023-07-14 05:00:51 +00:00

Comment removed 2/2.

AliasAlreadyTaken commented

2023-07-14 06:39:40 +00:00

This is a false and misleading statement and was entirely given in a different tone to you ingame:

Also something like only half the rules were displayed when they did get made part of the areas command.

Let's examine the rest. For reference, here's the timeline:

22.08.2021 : Shadow
08.01.2022 : change of area rules
19.08.2022 : niceride
28.03.2022 : Password reset of Shadow
23.04.2023 : Buzz

I do seem to recall that the change of area rules was made prior to my playing as niceride but not announced to anyone until after starting to play on Your Land as niceride. Do I have that wrong? Also something like only half the rules were displayed when they did get made part of the areas command.

Yes, both of those statements are false and you know it. This was what I said ingame:

2023-07-14 02:41:24: ACTION[Server]: [MOD] CHAT : Administrator : Shadow: Not seeing warnings is what I get from a lot of people when I have the sad duty to tell them they built something awesome near someone else and now were objected to. The rules did not change, but we need to work on UI. Mobile users get a wholoe list of stuff in the chat at the same time, none of which they can read properly except the last 3 lines

2023-07-14 03:48:49: ACTION[Server]: [MOD] CHAT : Administrator : Oh my. This history lesson regarding areas is more complex than anticipated .... we even changed the wording of the warning halfway through :D

No, we didn't display only half the rules. We clarified the wording. That made it slightly more complex to search for the event, nothing more.

You started playing as niceride on 19.08.2022, the area rules came into effect way before that, around 08.01.2022.

"except the last 3 lines": Even in those last 3 lines (in both the old and the new wording) it is pretty clear people cannot build there.

Regardless of displaying the rules to players, would appreciate some timeline of what rules applied and when they were changed.

Will the timeline posted above suffice?

Also agree 100% that "areas of Shadow" will be brought into compliance with the rules once it is shown what they are and when they were established. As from my notes it is not possible that the "areas of Shadow" under Giuseppe+ existed prior to the stated change of area rules date of 2022-01-08.

The log supports that, there is the creation of the Shadow account on 22.8.2021, but no further login at least until the rules came into effect. Means: In any of the cases found where you chose to not comply with the rules, you did it knowingly.

The "Shadow" area under Giuseppe+ is an odd situation. I reviewed with Giuseppe today and there is no problem with it being there from them.

All the people on the list of warnings (read: your neighbours) have a say in whether you can create an area there or not. If only one objects, staff is forced to remove the area. You were told ingame so please do not pretend here you do not know this.

When n people may say no but one of them says yes, then still n-1 people can say no. daydream and Giuseppe may have allowed what you did, but one of the n did not.

So can it remain in some modified form under the Giuseppe+ area or does it have to be removed wholesale? Are (nether portals) there other concerns that could be addressed to allow it?

With a report targeting all illicit areas except few that were expressly greenlit, we are forced to remove all of them.

I am responsible for this as a Three Old Bees guild area for several players, so while I'm not emotionally attached to this build it is my responsibility to ask these questions as it affects more players than just myself.

None of them can hold you accountable for any service you provide them. If anyone paid (in advance) to use those services, you may want to refund them. As far as rules are concerned you are the holder of those areas and neither

The direction and permission to protect an area there was verbal with staff and if that was wrong, so be it. Mistakes happen. Looking to minimize disruption to the community.

Please add when this permission happened, what staff was involved and if possible what you can remember of grep-able expressions, so I can find the event. If this happened in a private chat or in DM, I need permission of all sides involved before I can access them.

This is a false and misleading statement and was entirely given in a different tone to you ingame: > Also something like only half the rules were displayed when they did get made part of the areas command. Let's examine the rest. For reference, here's the timeline: 22.08.2021 : Shadow 08.01.2022 : change of area rules 19.08.2022 : niceride 28.03.2022 : Password reset of Shadow 23.04.2023 : Buzz > I do seem to recall that the change of area rules was made prior to my playing as niceride but not announced to anyone until after starting to play on Your Land as niceride. Do I have that wrong? Also something like only half the rules were displayed when they did get made part of the areas command. Yes, both of those statements are false and you know it. This was what I said ingame: ``` 2023-07-14 02:41:24: ACTION[Server]: [MOD] CHAT : Administrator : Shadow: Not seeing warnings is what I get from a lot of people when I have the sad duty to tell them they built something awesome near someone else and now were objected to. The rules did not change, but we need to work on UI. Mobile users get a wholoe list of stuff in the chat at the same time, none of which they can read properly except the last 3 lines 2023-07-14 03:48:49: ACTION[Server]: [MOD] CHAT : Administrator : Oh my. This history lesson regarding areas is more complex than anticipated .... we even changed the wording of the warning halfway through :D ``` No, we didn't display only half the rules. We clarified the wording. That made it slightly more complex to search for the event, nothing more. You started playing as niceride on 19.08.2022, the area rules came into effect way before that, around 08.01.2022. "except the last 3 lines": Even in those last 3 lines (in both the old and the new wording) it is pretty clear people cannot build there. > Regardless of displaying the rules to players, would appreciate some timeline of what rules applied and when they were changed. Will the timeline posted above suffice? > Also agree 100% that "areas of Shadow" will be brought into compliance with the rules once it is shown what they are and when they were established. As from my notes it is not possible that the "areas of Shadow" under Giuseppe+ existed prior to the stated change of area rules date of 2022-01-08. The log supports that, there is the creation of the Shadow account on 22.8.2021, but no further login at least until the rules came into effect. Means: In any of the cases found where you chose to not comply with the rules, you did it knowingly. > The "Shadow" area under Giuseppe+ is an odd situation. I reviewed with Giuseppe today and there is no problem with it being there from them. All the people on the list of warnings (read: your neighbours) have a say in whether you can create an area there or not. If only one objects, staff is forced to remove the area. You were told ingame so please do not pretend here you do not know this. When n people may say no but one of them says yes, then still n-1 people can say no. daydream and Giuseppe may have allowed what you did, but one of the n did not. > So can it remain in some modified form under the Giuseppe+ area or does it have to be removed wholesale? Are (nether portals) there other concerns that could be addressed to allow it? With a report targeting all illicit areas except few that were expressly greenlit, we are forced to remove all of them. > I am responsible for this as a Three Old Bees guild area for several players, so while I'm not emotionally attached to this build it is my responsibility to ask these questions as it affects more players than just myself. None of them can hold you accountable for any service you provide them. If anyone paid (in advance) to use those services, you may want to refund them. As far as rules are concerned you are the holder of those areas and neither > The direction and permission to protect an area there was verbal with staff and if that was wrong, so be it. Mistakes happen. Looking to minimize disruption to the community. Please add when this permission happened, what staff was involved and if possible what you can remember of grep-able expressions, so I can find the event. If this happened in a private chat or in DM, I need permission of all sides involved before I can access them.

👍 1

sixer commented

2023-07-14 16:08:05 +00:00

how would the area priority work if area is recreated with different parameters?

for example area A is created, far enough from anybody.
Later someone else creates area B that is too close to A and violating the 150-rule.

Even later, owner of A creates same area as A in x/z coords, just slightly moved in y (i.e change from 0 ... 128 to -60 ... 68) - lets call it A1 and then deletes the original area A.

Can B demand removal of A1? Can A demand removal of B? who has priority? can logs detect this situation?

how would the area priority work if area is recreated with different parameters? for example area A is created, far enough from anybody. Later someone else creates area B that is too close to A and violating the 150-rule. Even later, owner of A creates same area as A in x/z coords, just slightly moved in y (i.e change from 0 ... 128 to -60 ... 68) - lets call it A1 and then deletes the original area A. Can B demand removal of A1? Can A demand removal of B? who has priority? can logs detect this situation?

Boot commented

2023-07-14 16:22:55 +00:00

Alias, part of the north tunnel of the public mine, is now also in the cleanup zone. Please do not delete accidentally.

👍 1

AliasAlreadyTaken commented

2023-07-20 01:07:10 +00:00

how would the area priority work if area is recreated with different parameters?

for example area A is created, far enough from anybody.
Later someone else creates area B that is too close to A and violating the 150-rule.

Sounds like A can demand removal of B.

Even later, owner of A creates same area as A in x/z coords, just slightly moved in y (i.e change from 0 ... 128 to -60 ... 68) - lets call it A1 and then deletes the original area A.

Can B demand removal of A1? Can A demand removal of B? who has priority? can logs detect this situation?

That's pretty hard to detect, but yes, we can do that. We don't push a magic button and out comes a verdict who is in the right, based on some technical values. We need to look at every case individually, most often helped by the people involved. It is rare that someone who is about to be removed demands proof, most often they already know that they were too close. However, proving such a situation is well within their rights.

> how would the area priority work if area is recreated with different parameters? > > for example area A is created, far enough from anybody. > Later someone else creates area B that is too close to A and violating the 150-rule. Sounds like A can demand removal of B. > Even later, owner of A creates same area as A in x/z coords, just slightly moved in y (i.e change from 0 ... 128 to -60 ... 68) - lets call it A1 and then deletes the original area A. > > Can B demand removal of A1? Can A demand removal of B? who has priority? can logs detect this situation? That's pretty hard to detect, but yes, we can do that. We don't push a magic button and out comes a verdict who is in the right, based on some technical values. We need to look at every case individually, most often helped by the people involved. It is rare that someone who is about to be removed demands proof, most often they already know that they were too close. However, proving such a situation is well within their rights.

👍 1

Sign in to join this conversation.