Junk TARDIS leaves it's exterior behind?
MaketendoDev opened this issue · 5 comments
Describe the bug
Somehow randomly when we were exploring galifray we tried to return back using our junk tardis to find out that it just didn't take us back none of the buttons, levers and comparators, etc... just acted normal. We then used the return to home command but that also didn't move the junk tardis. As we /home we found out the junk tardis was right there somehow - I'm theorising that either somehow the junk tardis returned home without removing the remaining blocks but we didn't enable it to automatically go home.
To Reproduce
- go to galifray
- explore a lot (there was also a restart so i'm not sure if that also would be a part of it)
- random so yeah 🤷
Screenshots
No response
Log files
don't have access to them 🤷
'/tardis version' output
[System] [CHAT] [TARDIS] Server version: 1.21.5-2424-8c77678 (MC: 1.21.5)
[System] [CHAT] [TARDIS] TARDIS version: 6.1.0-b3106
[System] [CHAT] [TARDIS] Vault version: 1.7.3-b131
[System] [CHAT] [TARDIS] Multiverse-Core version: 4.3.16
[System] [CHAT] [TARDIS] floodgate version: 2.2.4-SNAPSHOT (b116-0e3163c)
[System] [CHAT] [TARDIS] CoreProtect version: 23.1
[System] [CHAT] [TARDIS] Checking for new TARDIS builds...
[System] [CHAT] [TARDIS] You are 3 builds behind! Type /tadmin update_plugins to update!
Probably going to be difficult to reproduce this if it happens at random. Can you have a server admin look for log entries around that time? Are there any plugins that would cause the chunks to be unloaded? Or maybe the chunk got rolled back due to a backup job running or the world didn't save properly?
May have accidentally reproduced this issue, except where I'm standing here is the junk tardis's home location. According to /tjunk find, the tardis is several hundred blocks away
Not sure how this happened, but I was trying to test the auto return function. It seems like I might have the opposite problem here.
...and when I teleport to the supposed location of the junk tardis, it's not there. Almost like the database is failing to update when it goes home?
this is the same thing that happen with the ticket a few down on the list title is something like junk tardis not going home