ParadiseSS13/Paradise

You can override enriched fuel rods in the Fuel Enrichment Centrifuge

Open

#32,405 opened on Aug 7, 2026

View on GitHubContributor guide
 (1 comment) (0 reactions) (0 assignees)DM (1,313 forks)batch import
Easily FixedGood First IssueOversight

Repository metrics

Stars
 (445 stars)
PR merge metrics
 (Avg merge 13d 5h) (90 merged PRs in 30d)

Description

BYOND Version

516.1664

Issue Description

You're not stopped from inserting a new fuel rod into the Fuel Enrichment Centrifuge if there already is one in there AND the machine is done centrifuging a previous fuel rod. This deletes the original fuel rod.

What did you expect to happen?

To get an error message saying "There is already a fuel rod in the Fuel Enrichment Centrifuge", and then be stopped from inserting the next rod.

What happened instead?

I overrode the already enriched rod and then I became sad.

Why is this bad/What are the consequences?

You shouldn't be able to delete items like this, especially when you have put effort into making the item.

Steps to reproduce the issue.

  1. Put a fuel rod that is ready to be enriched into the Fuel Enrichment Centrifuged (I used a Weak Plutonium rod that had been heat treated).
  2. Start the centrifuge.
  3. When the centrifuge is done, dont take out the rod, instead try and put a new rod in (I used another Weak Plutonium Rod).
  4. Notice that you now lost the first rod.

When did the problem start happening?

Noticed around 01.08.2026.

Extra information

No response

Relevant log output/runtime error

Contributor guide

Research direction
Locate the Fuel Enrichment Centrifuge code in the game files. Examine the machine's process and input handling to see where it accepts a new fuel rod without checking if one is already present. Add a check to reject insertion with a message when a rod already exists.
Tech stack
None
Domain
backendgame dev
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
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.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GitBYOND
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
75