pups reports: Please, add an option to turn ... #6006
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
source/testserver
ugh/petz
ugh/QA main
ugh/QA NOK
ugh/QA OK
No Milestone
No project
No Assignees
8 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: your-land/bugtracker#6006
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
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?
pups reports a bug:
Player position:
Player look:
Player information:
Player meta:
Log identifier
Profiler save:
Status:
Teleport command:
Compass command:
Why?
Some people prefer not to use choppy under any circumstances
using shift(crouch) to stay on a node if you work somewhere high up risks activating choppy accidently
I understand that. You don't have to. But why should you hold the axe with left-click and press Shift at the same time?
building on a tower made of wood for example.
Ok, the previous answer was still about Alias. Bla was very fast.
Of course, when you're working at heights, you always have to be careful. Ok, and with Shift you have more security. But why should you work with an axe at the same time? If you want to be on the safe side, then you just put a block under you that is not made of wood and have a secure footing even with the axe.
For example, if you're making part of a house from wood trunks, and misplace a block, it's very easy to forget that removing one block quickly with an axe will start destroying more parts of your house...
choppy won't target any nodes that the player places themself, though that only counts for blocks placed after choppy was installed.
Ah, nice, I was confusing it with how the previous mod worked then...
Then mostly it's the problem when you forget you have it on (like I often do) and need to carefully prune some trees (which I rarely do).
How can choppy recognize such blocks? But it is still valid to have option to disable it completely, like when you prune trees, build a tree house, or adjust wall/fence from trees, etc...
Just use your sword for such rare situations.
Those maybe rare, but sometimes you need to cut many nodes and the sword is very slow for wood
being solid opaque nodes, tree trunks don't define a paramtype, so i'm free to use that as an indicator. i add a callback that sets
param1=1
when a player places the node, and have choppy check for that. technically someone else could try to use param1 for some conflicting behavior, but i've only ever seen it used for this exact thing ("placed by player").this isn't the first time this feature has been requested, and i've been hesitant to add it because i think it complicates the user interface, but i suppose i should add it.
One example where this may be useful is if you incorporate actual live trees in your architecture. Like the city that is near 5100,0,-15500 where live trees were used to construct city walls. And if you want to cut corridors, ladders, walkways or gates in the wooden mass ... disabling choppy would be needed, especially as key to climb down ladder (when moving around the construction) = sneak key
Use an alt for this very very special work.
Not everyone wants to make an alt just to do special cases.
Yes, you can certainly wish for all kinds of improvements for very special needs or you can go the easy way. Ultimately, this is decided by the few who are able to implement these changes in the code. Until then, you can at least consider the easy way ...
Is there any important reason why choppy shouldn´t get a on/off toggle?
Cause suggesting alts seems a bit extrem just to prevent that, especially because in that case it won´t even help.
If you want to cut a path through a forest or build a treehouse into an existing tree both require unprotected or an area which results in choppy working.
mostly because i though it would make the user interface more complicated than it needed to be. but as i mentioned above, i do think i should add it now, because it's been requested several times.
I understand your reason completly but more interested in why Boot is trying everything to prevent something simple like a chat command to toggle choppy on/off. Especially cause it doesn´t have any effect(no impact on node limit or media download etc) on those that don´t want to use it.
You want to look into the brain of Boot? Do you remember when choppy came on the server? That didn't work at first and then too well. You got tons of XP while the axe was automatically dancing. This was then fixed and since then it has been running wonderfully and fast. So why change something that works, the boot thinks. As a layman, I cannot know what effort and risks are associated with a change. If you say that the flag can be changed easily and without danger with a chat command, then of course you have my blessing.
Because that happens with all mods the whole time, some things get fixed/changed/improved/extented
For example see # 6060 your request to improve editing FAQ entries, editing works you just correctly state that its cumbersome.
choppy works too but just like with editing you can slip up and make a mistake.
Does this mean that the command
/toggle_woodcuting
is obsolete? Its still in the Help Volume 2.It's not even a command anymore.
i haven't implemented this yet, but my plan is to create a totally different command which will disable choppy entirely, no matter how you toggle it.
/disable_choppy
will fully disable it, independent of the usual toggle status.while it's seemingly simple, it's not a trivial change given how much depends on the current internal choppy API, so i probably won't get around to this soon. i'll need to set aside a bunch of time to ensure the changes don't break anything.
implemented
/disable_choppy
. it wasn't hard.9571c167d4
Fixed and on main.