cmss13-devs/cmss13

Escape Pod Examine Message Typo?

Open

#7,628 opened on Nov 19, 2024

View on GitHub
 (1 comment) (0 reactions) (0 assignees)DM (903 forks)batch import
Confirmed BugGood First IssueOversight

Repository metrics

Stars
 (169 stars)
PR merge metrics
 (Avg merge 23d 15h) (111 merged PRs in 30d)

Description

Testmerges

#7242: 'WIP Yautja Clan TGUI Menu' by realforest2001 at commit 0f24fabd69#6334: 'Xenomorph Endgame' by Git-Nivrak at commit 6ab61a7c45#7521: 'Human Resprites & Tweaks - Marines looking awesome' by Nanu308 at commit 3d25ec63f8#7511: 'Weyland-Yutani Intranet Terminal' by realforest2001 at commit df2219bffb#7165: 'Fax Responders TestMerge Collection' by realforest2001 at commit 7728f59e28#7582: 'Flare Rework: Dying Light' by MaximusRexCM at commit 2493bccdf2#7611: 'Lift more weed restrictions' by Drulikar at commit 51feb5ba11#6248: 'New Map: LV-759 Hybrisa Prospera' by Zenith00000 at commit c9750e678f#7619: 'Xenos no longer have capped damage' by Drulikar at commit 78aa56e252#7620: 'Adds temporary missing icon_state for gauss sentry holders' by Drulikar at commit 41cc81f618

Round ID

24890

Description of the bug

Examining escape pod cyro pods describes them as "It does not appear to be working."

What's the difference with what should have happened?

Different description

How do we reproduce this bug?

Launch escape pod Examine Cyro Tube

Attached logs

N/A

Additional details

  • Author: Sunken_Grove
  • Admin: Tysonix1
  • Note: None

Contributor guide

Research direction
The bug is a simple typo in the examine message of escape pod cryo tubes. Locate the relevant .dm file containing the examine text for objects, likely in the codebase under a path like 'code/game/objects/structures/cryo.dm' or 'code/game/machinery/escape pod.dm'. Search for the string 'cyro' and correct it to 'cryo' or adjust the description as intended. No additional context or maintainer response is needed.
Tech stack
None
Domain
frontend
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
1
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Under 1 hour
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.
95