-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Inverted Synchronization - opening one door closes another door #1
Comments
Thanks for the nice words. I'm glad you enjoy the module. Unfortunately syncing doors in a way that closes one when another one is opened isn't currently possible. I've been thinking about implementing this feature, however I'm not sure about what to do about locked doors. I see three ways to handle this:
I must say I'm not very fond of either of these possibilities, since all of these lead to a result that might break someones use case. Any ideas or suggestions for how to solve this problem are greatly appreciated. |
Also interested in this functionality. |
I maybe wrong, but I can offer an idea. Create a second field on the wall config. You can set a second group. This will work like the first one. Example. All doors closed. Player opens door A. Player closes Door B. Player opens Door B. Player closes Door A. |
a better solution be a toggle instead of setting true or false. |
Another possibility for locked doors in groups is if you toggle the group, all the doors but the locked one will change, and then if that door is ever unlocked it will automatically change to its proper opened/closed state. For example: So doors will always stay synchronized unless they are locked closed in which case they will stay there until unlocked no matter what the rest of the group does. |
I think a toggle work great (and yes I would be greatly interested in this functionality). |
Hi. You did a great module.
Is it possible to make a sync door open another at the same time it close another one?
This could allow the creation of amazing puzzles.
The text was updated successfully, but these errors were encountered: