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.1623
Issue Description
The "near station" area marker has perma gravity, that isn't effected by the gravity generator, leading to lots of Gravity! stuns, mostly noticeable on cerebron with the lots of near station plating.
What did you expect to happen?
It to not have gravity/be effected by the gravity generator
What happened instead?
Gravity!!
Why is this bad/What are the consequences?
Not consistent, random gravity tiles on station sector is very /very/ immersion breaking, and can ruin rounds if the main gravity is down due to the 6 second Gravity! stun.
Steps to reproduce the issue.
turn off gravity
step on a "near station" marked area, this is mostly used for the grills in space, and tiling in space, thats near the station
Gravity!
When did the problem start happening?
No idea, been an issue for as long as i remember
Extra information
No response
Relevant log output/runtime error
No response
The text was updated successfully, but these errors were encountered:
Exploit Reports
BYOND Version
515.1623
Issue Description
The "near station" area marker has perma gravity, that isn't effected by the gravity generator, leading to lots of Gravity! stuns, mostly noticeable on cerebron with the lots of near station plating.
What did you expect to happen?
It to not have gravity/be effected by the gravity generator
What happened instead?
Gravity!!
Why is this bad/What are the consequences?
Not consistent, random gravity tiles on station sector is very /very/ immersion breaking, and can ruin rounds if the main gravity is down due to the 6 second Gravity! stun.
Steps to reproduce the issue.
When did the problem start happening?
No idea, been an issue for as long as i remember
Extra information
No response
Relevant log output/runtime error
No response
The text was updated successfully, but these errors were encountered: