daydream reports: I just teleport tube many thin ... #4489
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
7 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: your-land/bugtracker#4489
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?
daydream reports a bug:
Player position:
Player look:
Player information:
Player meta:
Log identifier
Profiler save:
Status:
Teleport command:
Compass command:
This happened yesterday or the day before too :(
i'm not sure i trust teleport tubes to make things travel long distances into possibly unloaded areas, but other players seem to do it w/out major issues.
It's not the first time I heard something like that, so far without 100% repro
Can you look on log and refund? I spent a long time (all my play time yesterday) to gather things and now I don't have them.
This is how vacuum tubes log:
2023-05-15 09:31:23: ACTION[Server]: [yl_commons] "AliasAlreadyTaken" dropped "pipeworks:teleport_tube_1" at pos "(2011.49609375,14.5,1170.4919433594)"
2023-05-15 09:31:23: ACTION[Server]: [yl_commons] AliasAlreadyTaken takes "pipeworks:teleport_tube_1" from {"name":"AliasAlreadyTaken","type":"player"} [main]
2023-05-15 09:31:23: ACTION[Server]: [yl_commons] [__builtin:item] removing "ghost of pipeworks:teleport_tube_1" dropped by AliasAlreadyTaken @ (2010,15,1171) 0.6s ago
There appears to be no log for the teleport tube :-(
Not sure if that is a repro for the current situation, since WorldEdit is needed...
The Items will be dropped to the ground where the receiver was.
If there are other existing receivers, some items will go to them, others go to the removed one.
Not sure how more complex systems are affected, but I heared from Chache that their items went to old Puerto del Sol after it was moved...
Sounds like we need to find where teleport tubes store their data and clean that up soemhow
Until then let's refund what was lost, it's in the log at least when it's taken out of a chest.
i should add logs to the teleport tubes. i hate pipeworks code, but i should be able to do that.
Do I understand correctly that you then also get back the things that were lost because of burnt tubes?
Burnt tubes are a mechanic that defends against lagging the server due to too many items. It's the players' responsibility to make sure their machines are in working order.
This issue deals not with broken tubes and spilled items, but with a bug that caused the vanishing of items altogether.
upstream PR to log teleportation: https://github.com/mt-mods/pipeworks/pull/66
this doesn't resolve the current issue though.
But it provides insight into the magnitude of the problem. It's not the first time I heard of vanishing items, although most often when investigated the items mysteriously turned up in some unexpected chest.
@daydream there is a second receiving tube for
daydream:base
@ (5417,8,7762), in an area called "desert dry". possibly the items got sent there? there would have been no-where for them to go, so they would have been despawned. @AliasAlreadyTaken, can you see if items despawned at that location in the right timeframe?Plenty. Telltale:
But also a lot of petz.
For peace of mind, could we have a way to check a tp tube that would give the coordinates for all receivers it could send to?
I went to that location and the items were not there... I did change the sender to not receiving though. The way that is set up I think they would have despawned if they were there as the chest is on the left side past the stack injector.
I put all my incoming tubes on the left of the chest to store them and all my outgoing tubes on the right. This should control what direction things go even more than a tube setting in my mind.
yup, i went to the location to see what was there, and alias noted from the logs that when i did, that, the items re-loaded and immediately expired and despawned.
upstream code to log when items go through teleport tubs is merged.
note that it requires
pipeworks_log_teleport_tubes = true
to be set in minetest.conf.Then let's rate this "bug", refund the items and prepare an early 1.1.120
QA for "early" 1.1.120: I added the value to the testserver and the itemtransfer is logged.
QA: Nice. Works for laoded and unloaded mapblocks as far as I can tell
I don't think I got anything back but by now i can't remember if I even cared or not - I maybe did at the time but I'm over it by now anyways.
this is presumably live, though i can't see the logs
It's not only life, it already helped us track down stuff in three separate cases