sixer reports: major flaw in new woodcutting: ... #4277
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
6 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: your-land/bugtracker#4277
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?
sixer reports a bug:
Player position:
Player look:
Player information:
Player meta:
Log identifier
Profiler save:
Status:
Teleport command:
Compass command:
"enabled by default" is intended. you can toggle this behavior w/
/toggle_choppy
.Too late now, but probably this should have been disabled by default for existing accounts.
probably a better behavior would be to throw up a formspec when a player uses it for the first time, asking them whether they want it on by default, or off by default. but i'm terrible at formspecs.
Sounds like yl_settings could help with that, but the question remains: Should it be enabled or disabled by default?
Someone also suggested to start the chopping slower and then when no panic shift stopping happens it can increase speed.
Disabled by default to avoid noobs (or anyone else who doesn't know about this mechanic yet) destroying beautiful landscapes accidently.
Agree with the speed increase thing.
am I missing something but theres no real way to disable it as the shift is just a toggle of how shift is used?/.
You can disable it with
/toggle_choppy
and you can stop it with shift.it's mentioned elsewhere, but not here, that the purpose of having it on by default is to inform new players about the mechanic w/out them having to learn an esoteric command. i agree it is a problem for existing players who expect behavior to never change, but i didn't come up w/ a good solution before this was released. i think adding a formspec to ask players whether they want it on or off by default is a good compromise, i'll try to get around to doing that.
Sounds like an application for yl_settings to be honest. As in "first time they start chopping a tree, they get a question to decide on the setting and where to alter it in case they reconsider". /choppy_toggle would toggle the setting, too.
unfortunately i can't rely on yl_settings, because (1) it doesn't exist (2) what's the timeline for when the code would become public?
implemented a prompt in
fba67d148e
Needs two additional modes where (1) we can sneak or not sneak and not have choppy active at all. This was lacking from the woodcutting mod, which forced woodcutting on us and should be possible to disable totally any auto-cutting now that it is replaced by choppy. Also (2) a mode that emulates the latching behavior of woodcutting, because you need to be able to eat or switch axes without having to continually hold down sneak. That covers all uses.
Modes:
"press & hold sneak when cutting to use choppy."
"press sneak when cutting to start choppy; press again sneak to stop choppy."
"choppy is on! press sneak to stop choppy."
"choppy is off. Use /toggle_choppy to enable"
The unique non-alphanumeric character in each message is intentional so the user doesn't have to read it they can scan for that one character '&', ';', '!', '/'.
/toggle_choppy
command should show the formspec for (above) choices of choppy mode, and this should be shown to users the first time they trigger the pre-conditions for choppy to possibly be in effect (i.e. axe + natural tree trunk). If you use the command and make a selection before the formspec is shown from a "first timer" hook it should not ask you to make a choice again after you have made your choice.the prompt has been live for a while. niceride's additional suggestions can become another issue if someone wants to propose them.
Since I never heard any similar suggestions or people being unhappy with choppy, let's not implement those suggestions for now