flux reports: is it possible to define allow ... #3389
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
4 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: your-land/bugtracker#3389
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:
implemented in
25fa513484
It's an improvement :)
Not sure, but maybe MTG upstream may be interested?
Unfortunately this lead to ambiguous items not only ending up in the fuel slot when you shiftclick them, but ALSO when you drag them in?
Repro:
Expected: ethereal:palmleaves end up in the upper slot
Is wrong: ethereal:palmleaves end up in the lower slot
given that MTG is "feature complete" and even my bugfixes don't get accepted, probably not.
there's no way for the game to tell whether you shift-clicked something or click-and-drag, but i do think you're right that the default behavior should be what you're proposing. if something is cookable and a fuel, and you put it in the cooking slot, it should stay there.
i've also added support to the public furnace while i was looking at this again (though not the locked furnace, i fear there's more going on there).
40640753ce
flux wrote:
The furnace from my locks mod is based on an older version of the furnace from MTG. It needs to be updated. The old version still uses an abm while the new version in MTG works with timers.
I'm just not sure if the furnace from my locks mod is still needed. The one in MTG also got updated so that others can't take out things.
There are people who use locked furnaces. At least 384 lines of log deal with people placing those or adding items in and out.
Maybe we should maintain at least a fixed version of MTG
this is live