shanish2 reports: shanish:tree tele-tube stop re ... #2886
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#2886
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?
shanish2 reports a bug:
Player position:
Player look:
Player information:
Player meta:
Log identifier
Profiler save:
Status:
Teleport command:
Compass command:
verified that all tubes were within a single mapblock, so that's not it.
i think this might have something to do w/ the fact that
active_object_send_range_blocks = 3
andactive_block_range = 1
. solution: replace pipeworks w/ something that doesn't rely on entities to move things beteen inventories.wait no this isn't about stuck items, this is about the receive tube not receiving...
state of the receive tube currently:
@AliasAlreadyTaken which
mod_storage_backend
(specified in world.mt) is the server using?verified that the target node is not in the tp_tube_db, which is stored in mod_storage, which makes me suspect the old "too many things to serialize to disk" issue.
There is no backend spcified, so I'd guess we still use files. With 1.1.116 we'll switch to sqlite: #2637
yeah, i'm guessing that's the reasons the tubes forget then. for send tubes, they get re-initialized when an object reaches them and they aren't initialized, but the receive tubes can't benefit from that mechanic, so they remain unknown.
verified we're using the sqlite3 backend