BeeStation/BeeStation-Hornet

[Bug]: Anomaly Locked Modules not accepting anomaly cores

Open

#14323 opened on Apr 21, 2026

View on GitHub
 (0 comments) (0 reactions) (0 assignees)DM (215 stars) (728 forks)batch import
BugGood first issue

Description

BYOND Version

516.1681

Round Date

2026/04/21

Round ID

56124

Test merges

  • #14157

Describe the bug

Cannot put anomaly cores into Modsuit anomaly locked modules. Tried with both Kinesis and Antigrav modules, and with both Pyroclastic and Bioscrambler cores. When trying to use the core on either there is no feedback.

What did you expect?

When trying to insert a anomaly core into either the Kinesis or Antigrav module i expect them to accept it so it can be used.

Reproducible steps

  1. Get Core
  2. Try to put core into module

Contributor guide

Tech stack
None
Domain
backend
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
None
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
50
Research direction
Investigate the modsuit anomaly locked module code, likely in files related to modsuit modules and anomaly cores. The test merge #14157 may have introduced a regression. Check the insertion logic for anomaly cores into modules, and compare with expected behavior from previous versions.