flux reports: maybe everything (or most node ... #4062
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#4062
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?
flux reports a bug:
Player position:
Player look:
Player information:
Player meta:
Log identifier
Profiler save:
Status:
Teleport command:
Compass command:
this could potentially have far-ranging consequences, i'd like to hear other people's opinions before doing anything.
What could be those far-ranging consequences?
I was actually thinking about this in the past and how neat it would be. So I'd definitely like that feature!
i can't think of any downsides off the top of my head, but i'm currently wary of things that change basic game mechanics. would this result in speed-placing of lava sources? i'm not sure that matters. but given the vast range of nodes in the game, it's possible something would result in a weird and undesirable advantage.
also, people perhaps depend on the built-in game mechanics to keep them from placing more nodes than they want to - if your hand automatically refills, you might put down more dirt than you wanted to, and digging dirt may result in you getting a bone and losing the dirt. the crystal shovel obviates that, but the problem is more general than that single case.
I could see, for example, wanting to take stacks of a certain number and being able to stop automatically and control when/where I place the next one, etc. something like that - sounds great - but truth is - as nice as the concept is - I have never done it - so I suspect changing this seems like more of an issue than it will really be in practice.
I would just hit up chat when 30+ players are on and ask - just to make sure to give real chance for opinions as not all read bugtracker.
Worst case scenario: Someone may demand a setting, like for woodcutting. Let them bring up their yl_settings, choose the value, done.
sounds mostly positive. i'll add creating a demo of this to the todo list.
Other servers may be interested in this, too.
Also, when building, don't at least some blocks autorefill? As in "if you have a stack in your inv but the one in your hand runs dry, that other stack is placed in your hand" ?