Murmel reports: Massive forrest build right ne ... #4372

Closed
opened 2023-05-01 10:51:10 +00:00 by yourland-report · 18 comments

Murmel reports a bug:

Massive forrest build right next to Walstrand

Player position:

{
	x = 2585.3239746094,
	y = 4,
	z = 4272.1728515625
}

Player look:

{
	x = 0.22172346711159,
	y = 0.41151434183121,
	z = 0.88402187824249
}

Player information:

{
	max_jitter = 0.20199999213219,
	avg_jitter = 0,
	connection_uptime = 6007,
	patch = 0,
	major = 5,
	version_string = "5.7.0",
	lang_code = "de",
	minor = 7,
	protocol_version = 41,
	state = "Active",
	serialization_version = 29,
	formspec_version = 6,
	max_rtt = 0.22699999809265,
	ip_version = 6,
	min_rtt = 0.014000000432134,
	avg_rtt = 0.016000000759959,
	min_jitter = 0
}

Player meta:

{
	fields = {
		["3d_armor_inventory"] = "return {\"3d_armor:chestplate_crystal 1 20560\", \"shields:shield_rainbow 1 10936\", \"3d_armor:helmet_crystal 1 10160\", \"3d_armor:leggings_crystal 1 22300\", \"3d_armor:boots_crystal 1 16540\", \"\"}",
		bitten = "0",
		digged_nodes = "497570",
		["unified_inventory:bags"] = "return {\"unified_inventory:bag_large\", \"unified_inventory:bag_large\", \"unified_inventory:bag_large\", \"unified_inventory:bag_large\"}",
		partychat = "party",
		["petz:old_override_table"] = "return {[\"sneak_glitch\"] = false, [\"new_move\"] = true, [\"jump\"] = 1.5, [\"gravity\"] = 1, [\"sneak\"] = true, [\"speed\"] = 2}",
		["ocean_build.last_warning"] = "1.67001e+09",
		xp = "380876",
		["ocean_build.ocean_built"] = "9",
		jointime = "1663422013",
		inflicted_damage = "425024",
		["petz:werewolf_clan_idx"] = "1",
		punch_count = "19761",
		placed_nodes = "82828",
		died = "27",
		crafted = "19875",
		["petz:werewolf_vignette_id"] = "5",
		repellant = "0",
		["signslib:pos"] = "(2627,-15,4177)",
		yl_commons_player_created = "1663422013",
		yl_commons_player_joined = "1682932296",
		["petz:werewolf"] = "0",
		hud_state = "on",
		["petz:lycanthropy"] = "0",
		yl_commons_thankyou = "34",
		["stamina:level"] = "19",
		yl_church = "return {[\"last_death\"] = {[\"x\"] = 2607, [\"y\"] = -25, [\"z\"] = 4178}, [\"last_death_portal\"] = 1681496945}",
		["stamina:poisoned"] = "no",
		yl_unified_trash_review = "return {\"cblocks:micro_stonebrick_white 6\", \"default:cobble 2\", \"\", \"\"}",
		["stamina:exhaustion"] = "155.5",
		played_time = "6242582",
		arenalib_infobox_arenaID = "0"
	}
}

Log identifier


[MOD] yl_report log identifier = chNpvDSTaVM7rwLkWBjc4xfYAsecIOQ2

Profiler save:

profile-20230501T105110.json_prettyEE

Status:

# Server: version: 5.6.1-yl | game: Minetest Game | uptime: 20h 36min 4s | max lag: 0.678s | clients (26/52): 9T9, AliasAlreadyTaken, Alinia, Azelf, Bailiff, Chameleon, daydream, deyzorein404, Dirac, drgn, Flippster, flux, Halvar, HorusDamocles, JeCel, laira, mahou, Maumau, MineWorlds, Miwasso, Murmel, niceride, NodeBreaker, pata123, Ravise, Service

Teleport command:

/teleport xyz 2585 4 4272

Compass command:

/give_compass Construction chNpvDSTaVM7rwLkWBjc4xfYAsecIOQ2 D2691E 2585 4 4272
Murmel reports a bug: > Massive forrest build right next to Walstrand Player position: ``` { x = 2585.3239746094, y = 4, z = 4272.1728515625 } ``` Player look: ``` { x = 0.22172346711159, y = 0.41151434183121, z = 0.88402187824249 } ``` Player information: ``` { max_jitter = 0.20199999213219, avg_jitter = 0, connection_uptime = 6007, patch = 0, major = 5, version_string = "5.7.0", lang_code = "de", minor = 7, protocol_version = 41, state = "Active", serialization_version = 29, formspec_version = 6, max_rtt = 0.22699999809265, ip_version = 6, min_rtt = 0.014000000432134, avg_rtt = 0.016000000759959, min_jitter = 0 } ``` Player meta: ``` { fields = { ["3d_armor_inventory"] = "return {\"3d_armor:chestplate_crystal 1 20560\", \"shields:shield_rainbow 1 10936\", \"3d_armor:helmet_crystal 1 10160\", \"3d_armor:leggings_crystal 1 22300\", \"3d_armor:boots_crystal 1 16540\", \"\"}", bitten = "0", digged_nodes = "497570", ["unified_inventory:bags"] = "return {\"unified_inventory:bag_large\", \"unified_inventory:bag_large\", \"unified_inventory:bag_large\", \"unified_inventory:bag_large\"}", partychat = "party", ["petz:old_override_table"] = "return {[\"sneak_glitch\"] = false, [\"new_move\"] = true, [\"jump\"] = 1.5, [\"gravity\"] = 1, [\"sneak\"] = true, [\"speed\"] = 2}", ["ocean_build.last_warning"] = "1.67001e+09", xp = "380876", ["ocean_build.ocean_built"] = "9", jointime = "1663422013", inflicted_damage = "425024", ["petz:werewolf_clan_idx"] = "1", punch_count = "19761", placed_nodes = "82828", died = "27", crafted = "19875", ["petz:werewolf_vignette_id"] = "5", repellant = "0", ["signslib:pos"] = "(2627,-15,4177)", yl_commons_player_created = "1663422013", yl_commons_player_joined = "1682932296", ["petz:werewolf"] = "0", hud_state = "on", ["petz:lycanthropy"] = "0", yl_commons_thankyou = "34", ["stamina:level"] = "19", yl_church = "return {[\"last_death\"] = {[\"x\"] = 2607, [\"y\"] = -25, [\"z\"] = 4178}, [\"last_death_portal\"] = 1681496945}", ["stamina:poisoned"] = "no", yl_unified_trash_review = "return {\"cblocks:micro_stonebrick_white 6\", \"default:cobble 2\", \"\", \"\"}", ["stamina:exhaustion"] = "155.5", played_time = "6242582", arenalib_infobox_arenaID = "0" } } ``` Log identifier ``` [MOD] yl_report log identifier = chNpvDSTaVM7rwLkWBjc4xfYAsecIOQ2 ``` Profiler save: ``` profile-20230501T105110.json_prettyEE ``` Status: ``` # Server: version: 5.6.1-yl | game: Minetest Game | uptime: 20h 36min 4s | max lag: 0.678s | clients (26/52): 9T9, AliasAlreadyTaken, Alinia, Azelf, Bailiff, Chameleon, daydream, deyzorein404, Dirac, drgn, Flippster, flux, Halvar, HorusDamocles, JeCel, laira, mahou, Maumau, MineWorlds, Miwasso, Murmel, niceride, NodeBreaker, pata123, Ravise, Service ``` Teleport command: ``` /teleport xyz 2585 4 4272 ``` Compass command: ``` /give_compass Construction chNpvDSTaVM7rwLkWBjc4xfYAsecIOQ2 D2691E 2585 4 4272 ```
AliasAlreadyTaken was assigned by yourland-report 2023-05-01 10:51:10 +00:00

It seems sixer has build a massive forrest right next to Walstrand without asking and without permission.
We do not want this here and demand that this will be removed.

It seems sixer has build a massive forrest right next to Walstrand without asking and without permission. We do not want this here and demand that this will be removed.

I can cut the forest that is too close to walstrand. What forest boundary would be acceptable?

I can cut the forest that is too close to walstrand. What forest boundary would be acceptable?

![](https://gitea.your-land.de/attachments/0fab1307-ae36-4e09-9be0-26de400de34f)

You did not. It's still full of trees! Pleas don't do any terraforming, woodbuilding or anything at least 150 m next to Walstrand.

You did not. It's still full of trees! Pleas don't do any terraforming, woodbuilding or anything at least 150 m next to Walstrand.

I have not started yet, I'll get back to stable internet in the evening to perform the removal, the forest goes all the way to my house, so I'd like to ask how far from the Walstrand is the line where the removal should be done.

I have not started yet, I'll get back to stable internet in the evening to perform the removal, the forest goes all the way to my house, so I'd like to ask how far from the Walstrand is the line where the removal should be done.

Ok, i'll try to restore the original landscape within 150m of walstrand in few hours once I get back home (keep original trees, removing newly planted ones)

Ok, i'll try to restore the original landscape within 150m of walstrand in few hours once I get back home (keep original trees, removing newly planted ones)

Why do you think anyone could be happy with that?
You build giant trees about 5 or 10 blocks from out village walls.
We are not happy with your crystal biome just in front of the jungle, bit thats near to your own home. But that giant forest was really to much!

Why do you think anyone could be happy with that? You build giant trees about 5 or 10 blocks from out village walls. We are not happy with your crystal biome just in front of the jungle, bit thats near to your own home. But that giant forest was really to much!
AliasAlreadyTaken added the
1. kind/griefing
label 2023-05-01 18:25:36 +00:00
Member

extent of the damage: image

sixer's base is in the lower-center, walstrand is in the upper-right

extent of the damage: ![image](/attachments/4650a0ff-4824-4479-8698-35d1b12404dd) sixer's base is in the lower-center, walstrand is in the upper-right
866 KiB
Member

i need to augment WE w/ some tools to break up large jobs so as not to lag out the server, the way i did w/ //grepblocks from debuggery.

i'm willing to WE all the sequoia trees to oblivion, but it'd create a several-minute lag spike if i did it all in one command.

i need to augment WE w/ some tools to break up large jobs so as not to lag out the server, the way i did w/ `//grepblocks` from debuggery. i'm willing to WE all the sequoia trees to oblivion, but it'd create a several-minute lag spike if i did it all in one command.

Alias has extended Walstrand-Area, so many of the sequoia trees are now part of our protected area.
All sequoia on this area will removed by Marmel, probably Tute and me. (Chests for removal are already prepared).
It's not my business what you do with the sequoia outside our area.

Alias has extended Walstrand-Area, so many of the sequoia trees are now part of our protected area. All sequoia on this area will removed by Marmel, probably Tute and me. (Chests for removal are already prepared). It's not my business what you do with the sequoia outside our area.

It's still your area - state your wishes :)

If you want them gone, we'll remove them, if you want them stay, they will stay.

It's still your area - state your wishes :) If you want them gone, we'll remove them, if you want them stay, they will stay.
Member

@Murmel staff will happily remove the sequoias in your area if you want, it's no trouble at all

@Murmel staff will happily remove the sequoias in your area if you want, it's no trouble at all

@Murmel staff will happily remove the sequoias in your area if you want, it's no trouble at all

Marmel was happy to use choppy on them. I think she made 12 levels by this. I think it's too easy to gain XP by that.
Tute removed the remaining parts in the air.
I think it's a problem when big trees are too close to each other. Then choppy starts to chop more than one tree at the time and then you get leftovers which you only can chop by building up again (or fly or WE if you hav approriate privs).
If staff has no problems with the alteration of the coast line and the oak trees ind sequias in tha jungle outside Walstrand area, this will be fine for me.
Just have to collect the chests with the leaves now.

> @Murmel staff will happily remove the sequoias in your area if you want, it's no trouble at all Marmel was happy to use choppy on them. I think she made 12 levels by this. I think it's too easy to gain XP by that. Tute removed the remaining parts in the air. I think it's a problem when big trees are too close to each other. Then choppy starts to chop more than one tree at the time and then you get leftovers which you only can chop by building up again (or fly or WE if you hav approriate privs). If staff has no problems with the alteration of the coast line and the oak trees ind sequias in tha jungle outside Walstrand area, this will be fine for me. Just have to collect the chests with the leaves now.

I've cut some leftover trees between the protected area and my base, so there should be no half-cut sequoias now.

You can solve floating remains by building stack of blocks under it under your feet, then cutting the floater via choppy, then cutting the stack of blocks again once choppy is done, landing back on the ground.

I've cut some leftover trees between the protected area and my base, so there should be no half-cut sequoias now. You can solve floating remains by building stack of blocks under it under your feet, then cutting the floater via choppy, then cutting the stack of blocks again once choppy is done, landing back on the ground.

I've cut some leftover trees between the protected area and my base, so there should be no half-cut sequoias now.

You can solve floating remains by building stack of blocks under it under your feet, then cutting the floater via choppy, then cutting the stack of blocks again once choppy is done, landing back on the ground.

sixer I know that, thats how we did, but as choppy is new, flux might be interested on what causes remaining floating treetops

> I've cut some leftover trees between the protected area and my base, so there should be no half-cut sequoias now. > > You can solve floating remains by building stack of blocks under it under your feet, then cutting the floater via choppy, then cutting the stack of blocks again once choppy is done, landing back on the ground. sixer I know that, thats how we did, but as choppy is new, flux might be interested on what causes remaining floating treetops

on big trees choppy seem to start close to top and progressing both ways towards top and bottom. If you are forced to interrupt choppy due to hunger or to defend from monsters, some part of tree can disconnect from the trunk. On resuming, it will not be seen as part of tree to be cut down.

on big trees choppy seem to start close to top and progressing both ways towards top and bottom. If you are forced to interrupt choppy due to hunger or to defend from monsters, some part of tree can disconnect from the trunk. On resuming, it will not be seen as part of tree to be cut down.
Member

If you are forced to interrupt choppy due to hunger or to defend from monsters, some part of tree can disconnect from the trunk. On resuming, it will not be seen as part of tree to be cut down.

i've addressed this in an update to choppy which pauses the process when you select something other than an axe, instead of aborting it entirely.

> If you are forced to interrupt choppy due to hunger or to defend from monsters, some part of tree can disconnect from the trunk. On resuming, it will not be seen as part of tree to be cut down. i've addressed this in an update to choppy which *pauses* the process when you select something other than an axe, instead of aborting it entirely.
flux added the
5. result/fixed
3. source/ingame
labels 2023-05-07 16:17:20 +00:00
Member

the forest seems to have been successfully trimmed, closing this

the forest seems to have been successfully trimmed, closing this
flux closed this issue 2023-05-07 16:17:41 +00:00
Sign in to join this conversation.
No Milestone
No project
No Assignees
5 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#4372
No description provided.