[Uleat]

(You should try having two or more clients at the lift with the test code enabled, but the type 40 check disabled
in the Process() procedure..you think it has erratic behavior with one client..hah!)


If you're using only the lever actuator, I saw only one problem that required two clicks. I'm pretty sure your script
is right. The problem lies in ForceOpen and ForceClose.

I'm working on those, but I think this is the problem:

ForceOpen - we want to force a door open no matter what. The action for an open door case should be to
restart the timer, not to close the door. This creates dis-syncronous operation between the server and client
(we just sent an open door command to the client..why do we want the server to think it's shut now?)

ForceClose - your catch on the 'open door' action was correct. With that, and Trev's suggested fix, the only thing
that might need to be done is to add a zone 'close' broadcast to ensure a closed door really is closed.

I'm still looking at these, which is why they didn't make my patch. I don't want the changes to interefere with
any working scripts that have already accounted for a broken 'ForceClose.'

I didn't make the changes in the database that you suggested yet, which is probably why I can still click a rope and
have it activate alone.


U