Doors reopen when you close them

Hey Guys

this may have already been resolved but i cant find the answer . Does any one know how to fix it when you open it door it opens ... But when you close it it shows it being shut and it reopens

Any suggestions. anyone come across this

 

I don't know how to solve it, but we had a weird problem with cages on our server the other day.

It was open to me, but shut to my mate.
Then when I closed it, it was open to him and so on.

In the end, there was no way to tell if it was actually opened or closed! Ha!

 

lets pray for a hotfix from codehatch

 

Client issue, been happening randomly since at least Alpha 11

I have even seen Gates be invisible to one and be there and closed for another. That is why multiple doors, gates is key for security

 

Door's re-open for me too, we are hosted with fastpointgaming and installed through its installer.

You close the door and immediately springs back open, leave it for 5 minutes and the door automatically closes on it's own.

any idea whats causing this?

 

Is there any word on why the doors never shutting issue is occurring? Or any possible solutions?

I had originally assumed it was an issue with Alpha 16, but I test a door on an official Code}{atch server. It worked as intended..

 

doors work on the server i use most of the time. Sometimes they will show open for me and closed for another. If your server always has a door problem for everyone playing you might need to:

1. Back up your world data (located in the Saves folder.
2. re-install the server clean.
3. make some buildings and test doors.
4. install oxide
5. test doors again
6. add in one plugin at a time, testing doors to see what might be affecting them.

@Sydney says doors cannot be affected server side, it is a client side action. So not sure how plugins would affect it. But that would be the best way to rule out the issue.

 

There's really nothing we can do. Indeed the most logical thing to do would be to either reinstall the server or delete all world slots to start fresh. But I don't see how it helps because this bug starts somewhere and spreads across all doors. Hopefully A17 fixes this one.

 

Found out how to fix this problem, update oxide. I had this same problem on my server all I needed to do was update oxide.

 

You, sir, are a gentleman and a scholar. I actually did this a few minutes ago and it worked.

I guess everyone else on here just automatically installs every snapshot that comes out. I only install the open releases of the Oxide download when it becomes available. It was only my desperation that led me to seek out snapshots.