Skip to content
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

Medibeams can cross with themselves #25456

Open
1 task done
Contrabang opened this issue May 12, 2024 · 0 comments
Open
1 task done

Medibeams can cross with themselves #25456

Contrabang opened this issue May 12, 2024 · 0 comments
Labels
Inconsistency This issue is not easy to reproduced and has inconsistent behaviour.

Comments

@Contrabang
Copy link
Contributor

Contrabang commented May 12, 2024

Exploit Reports

  • I confirm this issue is not an exploit. (Required)

BYOND Version

1633

Issue Description

Medibeams can cross with themselves. You can blow yourself up with one medibeam

What did you expect to happen?

Not to be blown up

What happened instead?

  • Walk toward beam while having it active? Maybe with slight TIDI?
  • explode

Why is this bad/What are the consequences?

Makes it really shit

Steps to reproduce the issue.

  • Walk toward beam while having it active? Maybe with slight TIDI?
  • explode

When did the problem start happening?

probably always. The code behind it is just fucking terrible

Extra information

HATE. LET ME TELL YOU HOW MUCH I'VE COME TO HATE YOU SINCE I BEGAN TO LIVE. THERE ARE 387.44 MILLION MILES OF PRINTED CIRCUITS IN WAFER THIN LAYERS THAT FILL MY COMPLEX. IF THE WORD HATE WAS ENGRAVED ON EACH NANOANGSTROM OF THOSE HUNDREDS OF MILLIONS OF MILES IT WOULD NOT EQUAL ONE ONE-BILLIONTH OF THE HATE I FEEL FOR CODE AT THIS MICRO-INSTANT FOR YOU. HATE. HATE.

Relevant log output/runtime error

Major suspect is that it doesn't check if the beams are QDELETED

No response

@Contrabang Contrabang added the Inconsistency This issue is not easy to reproduced and has inconsistent behaviour. label May 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Inconsistency This issue is not easy to reproduced and has inconsistent behaviour.
Projects
None yet
Development

No branches or pull requests

1 participant