I was able to recreate this only a few times using the command macros mod. However, the vast majority of players will likely never see this message due to the typing speed required to receive the error otherwise.

This is likely an intended feature as opposed to a bug, though. The travel bag database presumably needs a few moments to update across servers in the interests of preventing your items from being overwritten or destroyed between rapid cross-server travelbag commands.

 

Intended safety feature.

 

it saying it's still locked is really weird, I'll have to try and speak to Andrew to see if there is anything of more info hidden in the logs, but, that's odd; There is some logic that will unlock it when the server holding the lock restarts, but, the fact that it's still locked is scary...

There is some stuff coming in the pipeline which will solve a few more concerns with the TB system, however

 

Please try to reproduce this again after next maintenance and let us know what happens @BrokeMel

 

Please let us know if this happens again @BrokeMel

 

@BrokeMel let us know if this continues for you now.
We just made further changes :)

 

are you using a script to close travel and then open?
what are you putting in the bag?
is it locked "by main" again or another server?

just trying to help get some info so support higherups can have something to work with.

 

Please let us know if you can still reproduce this. @BrokeMel
We had some lag issues recently due to /seen and /rn but @electronicboy has since fixed those.

PS: Exact steps would be really useful.

 

@BrokeMel You're in aus still right? What does your connection/ping generally look like?

I wonder if the info saying you closed your travelbag is being dropped before it makes it back to the server

 

Thanks, we are looking into this. :)

 

@BrokeMel can you please give us exact reproduction steps, including information on which server you are on for each step.

 

If you ever get reproduction steps do let us know.
It's the only way we can diagnose this.

 

Ping might actually be playing a factor here...