Daily limits not resetting

Anyone else having an issue where the teleports are not resetting after 24 hours?  Thanks

no...

I've had a few complaints today actually. That is why I am here browsing.

Well this is not very helpful. What version are you even using?

/tpinfo might be a good start.

oxide log?

What changed recently?

Did you try going back a version to test?

1.6.1 - had no issues for months.
Upgraded to 1.6.9 this wipe.

Nothing in the logs at all.

Daily resets are not resetting for us any longer.



Merged post

Another thing I noticed:  bandit and outpost coords are not automatically updating.
I had to manually set these locations at wipe.  First time I've ever had to do this.

Again, this issue is only found in 1.6.9. Thanks

i got the same problem. since last wipe and the new 1.6.9 version.

64JDxMQ0JxoKvs8 Belvo

i got the same problem. since last wipe and the new 1.6.9 version.

Had to wait for 12.01 am to check , but it reset back to maximum amount of tp's.
No problems since start of wipe, setting homes ok, Tpa and Tpr working, cooldowns working , /sethome and /removehome working.

Yes, I've been having complaints, I'm on 1.6.9

3hc4LQNUPIfyCYn.png harland555

Yes, I've been having complaints, I'm on 1.6.9

Yes.  This is broken.

I just went back to 1.6.8 and it seesm to be fine now. Not sure what's up with the other.

I reverted to 1.6.8 - hopefully at midnight things get fixed 

codepimp1234

I reverted to 1.6.8 - hopefully at midnight things get fixed 

I am on 1.6.9 and again the tp's reset after midnight tonight as they did last night, might be a config error on your part



Merged post

And they reset again today, no problems so far,

I wouldn't think we all messed up the config haha. Who knows though, very odd.

and who would ever know, no one can give any good information, no one is posting any datafile snips, or /tpinfo screenshots. you dont even know what a config is, you try to edit plugin code. 'anyone else' or 'don't work' posts piss me off.

no problems with v1.6.8?

hi this is fixed in the next update. thanks