cmss13-devs / cmss13-devs/cmss13
Synthetic reset keys don't seem to be functioning in specific scenarios.
- Dominant language
- DM
- Stars
- 170
- Forks
- 940
- Avg merge
- 5d 16h
- Merged PRs (30d)
- 61
Description
### Testmerges
#11075: 'Ticket Panel (Adminhelps & Mentorhelps)' by GeneriedJenelle at commit 4ad8d0cf87 #12174: 'Yautja Armor Sets' by realforest2001 at commit 90c66798ed #10414: 'Port: Harm Intent uses Auto-Fire instead of PB' by MistChristmas at commit d44502d495 #12361: 'pride scarfs in loadout' by Detective-Google at commit 6ddcf88cb8 #12140: 'Tyrargo Rift - Various Alterations' by Steelpoint at commit 13c4e6de58 #10696: '[code bounty] Sentinel rework' by cuberound at commit 2c8e5c147c #11698: 'SHARP Resharpening: Design Improvements' by MPhonks at commit 3afad4e3e6 #12464: 'LV1021: Operation Falcon's Fury - Ground Map' by Steelpoint at commit ec73bfda15
### Round ID
34971
### Description of the bug
While buckle cuffed to a chair as a dead generation 1 synthetic, multiple attempts to defib using various different types of reset keys proved ineffective.
Notably, the reset keys reportedly did not lose charge when attempting the defib, and the synthetic was below the damage threshold.
### What's the difference with what should have happened?
It probably should've revived the synth and needed to be reset.
### How do we reproduce this bug?
1.Kill a gen 1 synthetic
2.Buckle cuff it to a chair
3.Attempt to defib it with a reset key
4. Its.. Not working?
### Issue Bingo
- [ ] Issue could be reproduced at least once
- [x] Issue happened in a recent (less than 7 days ago) round
- [x] Couldn't find an existing issue about this (https://github.com/cmss13-devs/cmss13/issues)
Contributor guide
Research direction
Start by reproducing the reported scenario in-game: kill a gen 1 synthetic, buckle-cuff it to a chair, and try each reset-key type while it is below the damage threshold. Trace the reset-key defibrillation handling and verify that an eligible synthetic is revived and the key requires resetting afterward.
Written by the indexing model from the issue text.
Assessment
- Domain
- game-dev
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100