Describe the bug

Apparently players can run /tt check_loc and break the blocks where the snow blocks place. Players are using it to break into lockette signs etc.

As for the other one, it's pretty self explanitory, /TARDIS update whatever basically traps them in a fail-spam loop where they can't do anything til the server restarts.

To Reproduce

As described in the ticket, these are fortunately pretty basic issues but I will be more than happy to provide any more info that I can.

Screenshots

No response

Log files

Log file is way too long but can attach if needed

'/tardis version' output

[14:09:58 INFO]: [TARDIS] Server version: git-Paper-519 (MC: 1.19.4)
[14:09:58 INFO]: [TARDIS] TARDIS version: 5.0.0-b2562
[14:09:58 INFO]: [TARDIS] Vault version: 1.7.3-b131
[14:09:58 INFO]: [TARDIS] WorldGuard version: 7.0.8-SNAPSHOT+2231-bddfbdd
[14:09:58 INFO]: [TARDIS] PlaceholderAPI version: 2.11.3
[14:09:58 INFO]: [TARDIS] Multiverse-Core version: 4.3.2-SNAPSHOT-b870
[14:09:58 INFO]: [TARDIS] Essentials version: 2.20.0-dev+56-fd49b70
[14:09:58 INFO]: [TARDIS] Towny version: 0.99.0.5
[14:09:58 INFO]: [TARDIS] dynmap version: 3.5-873
[14:09:58 INFO]: [TARDIS] LibsDisguises version: 10.0.33-SNAPSHOT
[14:09:58 INFO]: [TARDIS] Multiverse-Inventories version: 4.2.4-SNAPSHOT-b524
[14:09:58 INFO]: [TARDIS] WorldBorder version: 2.1.5
[14:09:58 INFO]: [TARDIS] CoreProtect version: 21.3
[14:09:58 INFO]: [TARDIS] Checking for new TARDIS builds...
[14:09:58 INFO]: [TARDIS] You are 2 builds behind! Type /tadmin update_plugins to update!

/tt check_loc should be fixed

Not seeing any issues with /tardis update [which] command, works as expected here. More details needed - any messages, what exactly is the loop?

The TT loc issue is fixed but still experiencing the update bug.

The loop is “You must be in a TARDIS world to update this block!”

players have also begun receiving a “you cannot grow rooms unless your TARDIS was created in its own world!” Upon attempting room growth

I think these are related, but what could be causing it?

Most probably the time vortex world is being loaded by Multiverse instead of TARDIS

How can I fix this? I’ve never had this issue before

I should note people can still fly and use their TARDISes fine it seems

How can I fix this? I’ve never had this issue before

First check the Multiverse worlds.yml config to see if any TARDIS worlds are in there.
If so, stop the server, delete the entries, then restart the server.

Thank you! I will try it ASAP. Hopefully I don’t accidentally remove my world lol. I must ask though, why did this start happening all of a sudden? Was there a change in the plugin?

/mv remove {WORLD}