cmss13-devs / cmss13-devs/cmss13
Crate loses collision after passing though open wooden crate
- Dominant language
- DM
- Stars
- 170
- Forks
- 940
- Avg merge
- 5d 16h
- Merged PRs (30d)
- 61
Description
## Testmerges
#12627: 'Tyrargo Rift (2) - Various Alterations' by Steelpoint at commit 73b8f408b2
#12640: 'Fuel pumps have health during hijack + bullet ping fix + trapper shotgun flag fix' by Drulikar at commit 77b1edf932
#12721: 'Assorted Sound Fixes' by fira at commit 85e10735bf
#12824: 'Bundles Wound Overlay Updates' by fira at commit 6b48f2d5f1
#12825: 'Optimize /datum/controller/subsystem/minimaps/proc/add_marker' by fira at commit 1a869a8443
#11085: 'Surgery QOL update (better descriptions, better sprites, more pain and screaming, add sounds to procedures that did not have any)' by Puckaboo2 at commit 696154c2e0
#12753: 'PR Stack - Movement Optimizations' by fira at commit 3082e3cb2b
#12322: 'Fort McNeil - (Lowpop) Ground Map' by Steelpoint at commit d16cb3bb7b
## Round ID
35753
## Description of the bug
After pushing closed crate through wooden chest, closed crate stops having collision, cannot be pushed. Only after opening/closing or grabbing it and moving manually it regains collision
## What's the difference with what should have happened?
Crate should only lose collision after being opened
## How do we reproduce this bug?
1. Take wooden crate
2. Take normal crate that can be repackaged (i got it working with parachute crate)
3. Open wooden crate
4. Push normal crate through open crate
5. You cannot move normal crate anymore until its opened/closed or grabbed
## Attached logs
```
N/A
```
## Additional details
- Author: CRPL1000
- Admin: Thespy24574
- Note: None
Contributor guide
Research direction
No file or test is named. Reproduce the issue using the listed crate and wooden-crate steps, then trace the crate collision handling; it is done when pushing a normal crate through an open wooden crate does not permanently remove its collision and the reproduction succeeds without manual recovery.
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
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100