Bond007 reports: Just here, just now (2mins bac ... #2830
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#2830
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?
Bond007 reports a bug:
Player position:
Player look:
Player information:
Player meta:
Log identifier
Profiler save:
Status:
Teleport command:
Compass command:
possibly it got sucked up by another vacuum tube? but it should have gone into the player's inventory...
2022-10-08 19:13:36: ACTION[Server]: PM from Bond007 to AliasAlreadyTaken: oooh...the vacuum tube mysteriously appeared at the same place where it was supposed to be :P
So I think we ccould close this. However there's still something odd: Why did the tube "reappear" so much later? Is there a repair mechanic in pipeworks?
there actually is a repair mechanic in pipeworks that i was never aware of - whack the broken tube w/ a hammer (though there are bugs w/ that)
however, i think this was an issue w/ the client predicting that the node was dug when it wasn't, and the server not informing the client that it was still there until the client flushed its cache. "client digs something, doesn't get it, and it re-appears later" is a long-standing bug. not sure there's an upstream issue about it, i've certainly never found a way to replicate it reliably, but it's happened to me a couple times.
closing this, as there's not really anything we can do.