-
Notifications
You must be signed in to change notification settings - Fork 46
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
Not gates act as Or gates #2835
Closed
Labels
Bug
Something isn't working correctly
Comments
HugoBDesigner
changed the title
[Bug] Triggers bypassing logic gates on connections
[Bug] Not gates act as Or gates
Oct 9, 2018
FrozenDragon0
changed the title
[Bug] Not gates act as Or gates
Not gates act as Or gates
Oct 9, 2018
@HugoBDesigner No need for the [Bug] Title. we stopped putting it in issues a long time ago since it was annoying. |
It might not be strictly necessary, but I don't see how that's a bad thing. Makes it easier to identify the nature of the issue, especially if seen from Discord's embeds, where there is no room for tags. |
TeamSpen210
added
the
Done in next release
This has been addressed in the next release
label
Nov 1, 2018
TeamSpen210
added a commit
that referenced
this issue
Nov 7, 2018
This was referenced Nov 10, 2018
Merged
TeamSpen210
removed
the
Done in next release
This has been addressed in the next release
label
Aug 19, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
If I connect a Trigger Once -> Not Gate -> Entity (for instance, a door, or an autoportal), the latter will only activate when I get through the fizzler, instead of being active until I get through the trigger.
The text was updated successfully, but these errors were encountered: