Reword the "Extraction Case" description so it says that you HAVE TO HOLD the case

Open Beginner friendly
#190 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
1/5
Estimated time
Under an hour
Newbie friendliness
82/100
Issue type
Documentation
Clarity
Clearly specified
Activity status
Active
Domain
documentation

Research direction

Locate the Extraction Case description and compare its current wording with the report. Reword it to explicitly state that the case must be held, then verify the description clearly distinguishes holding the case from merely being nearby or having spawned it.

Written by the indexing model from the issue text.

Description

enhancement from-discord

Imported from Discord — #suggestions-feedback

  • Reported by: Germa
  • Posted: 2026-08-17
  • Replies: 3 from 2 other user(s)
  • Forum tags: Suggestion

Report

The way its currently worded I thought it would go by whoever spawned the case in not that whoever is holding it.
I ended up losing a Science part cause the case was next to me and I wasn't holding it when the ship got Bluespaced

Thread discussion

somerandomfeline — 2026-08-17

end of round allows you to have the case in your bag

somerandomfeline — 2026-08-17

idk about bluespace

Dalmat Gadin — 2026-08-17

I have had the extraction case in my backpack before and extracted with everything just fine


View original thread on Discord

Dominant language
DM
Stars
8
Forks
22
Avg merge
1d 21h
Merged PRs (30d)
63

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from voidcrew/Voidcrew

All issues in voidcrew/Voidcrew

Similar issues

More Documentation issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.