You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I confirm this issue is not an exploit. (Required)
BYOND Version
515.1635
Issue Description
I am unsure if this is actually intended or a bug, but the energized anomolies that the engine creates can stop emitter beams.
What did you expect to happen?
To go through the energetic anomoly, like other created anomolies
What happened instead?
It was stopped
Why is this bad/What are the consequences?
While technically a good thing as it can calm the engine, its inconsistent and can make more complicated engine setups annoying to manage if they require it to be above 5k EER. Its almost never an issue in ANY other situation, so I cant imagine it can be relevant in any other situation. You cant prevent them either, as walling off the way to the crystal wont matter. It will spawn inside of the path and just block it longer.
Steps to reproduce the issue.
Have an engine above 5k EER to spawn anomolies
have emitters online
have the emitter fire when an anomoly is in front of it
When did the problem start happening?
Forever, probably
Extra information
No response
Relevant log output/runtime error
No response
The text was updated successfully, but these errors were encountered:
This is currently intended behavior, I'll leave it up with the feature request tag in case someone wants to tackle this later. It shouldn't be too much of a hassle to add.
Exploit Reports
BYOND Version
515.1635
Issue Description
I am unsure if this is actually intended or a bug, but the energized anomolies that the engine creates can stop emitter beams.
What did you expect to happen?
To go through the energetic anomoly, like other created anomolies
What happened instead?
It was stopped
Why is this bad/What are the consequences?
While technically a good thing as it can calm the engine, its inconsistent and can make more complicated engine setups annoying to manage if they require it to be above 5k EER. Its almost never an issue in ANY other situation, so I cant imagine it can be relevant in any other situation. You cant prevent them either, as walling off the way to the crystal wont matter. It will spawn inside of the path and just block it longer.
Steps to reproduce the issue.
Have an engine above 5k EER to spawn anomolies
have emitters online
have the emitter fire when an anomoly is in front of it
When did the problem start happening?
Forever, probably
Extra information
No response
Relevant log output/runtime error
No response
The text was updated successfully, but these errors were encountered: