Murmel reports: Massive forrest build right ne ... #4372
Labels
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
No Milestone
No project
No Assignees
5 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: your-land/bugtracker#4372
Loading…
Reference in New Issue
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?
Murmel reports a bug:
Player position:
Player look:
Player information:
Player meta:
Log identifier
Profiler save:
Status:
Teleport command:
Compass command:
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?
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.
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!
extent of the damage:
sixer's base is in the lower-center, walstrand is in the upper-right
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.
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.
@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.
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.
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.
the forest seems to have been successfully trimmed, closing this