Problem with Safe Zone Lockers

[Long Beard 5]

Got a wee problem on my server. Players who access the lockers in the safe zone report the window opens for a couple of seconds then closes.

Anyone else experiencing this or have an idea on what's causing it and how to resolve it?

Many thanks.

[Mr Health And Safety 106]

If you have infistar running, have you updated it? sounds like it could be infistar closing the menu

[Long Beard 5]

1 hour ago, Mr Health And Safety said:

If you have infistar running, have you updated it? sounds like it could be infistar closing the menu

Yes running latest version.  Will check the logs.

[devilFaust 13]

I was just about to post the same problem. I have two players so far that reported this to me. Same thing. They go to access the locker and it shuts the menu on them fast. (I have the latest everything installed btw and we did a fresh DB on the upgrade to .9.8)

This stood out in the RPT:

10:04:56 Client: Object 2:1719 (type Type_104) not found.
10:04:56 Server: Object 2:1732 not found (message Type_120)
10:04:57 Server: Object 2:1731 not found (message Type_120)
10:05:03 Server: Object 2:1962 not found (message Type_92)

(Myself and the two other admin access it just fine btw)

Edited July 3, 2016 by devilFaust

[Razor77 151]

Check infistar settings I had it doing the same and I updated infistar and it's ok, it was blocking the menu for the lockers. 

[Mr Health And Safety 106]

If you disable infistar you will know for sure if its the casuse

[Long Beard 5]

Yep it was infistar.

I watched the live server logs and got someone to try locker. Threw up an error with IDD 24029.

I added 24029 to the infistar white list and it fixed it.  I would suggest you guys do the same in case it's a different IDD number for you.

[devilFaust 13]

4 hours ago, Long Beard said:

Yep it was infistar.

I watched the live server logs and got someone to try locker. Threw up an error with IDD 24029.

I added 24029 to the infistar white list and it fixed it.  I would suggest you guys do the same in case it's a different IDD number for you.

Same here, added it to the white list and it fixed it right up.

Thanks.