copper248 reports: immortal ghost items can be cr ... #4219
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
3 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: your-land/bugtracker#4219
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?
copper248 reports a bug:
Player position:
Player look:
Player information:
Player meta:
Log identifier
Profiler save:
Status:
Teleport command:
Compass command:
hooray
upstream PR https://github.com/minetest-mods/mesecons/pull/639
Is there a legit usecase where one would require a pedestal (/itemframe) to be moved?
the pedestal/itemframe cannot be moved, just the entity associated w/ a pedestal. e.g.
Would it make sense to create an unmovable, invisible and otherwise non-interactable block on top of the pedestal? Like doors?
that's an option. but if my (trivial this time!) mesecons PR gets rejected, i'd first petition Tenplus1 to add the pedestal entity to the list of blacklisted entities for mesecons MVPS actions, and if that's rejected, just put that into our integration code. for one, we'd need some way to update old pedestals, and old pedestals can have nodes directly over them, complicating any such solution....