cmss13-devs / cmss13-devs/cmss13

random DS selection for hijack can cause event dropships to be sent down to the planet and hijacked

Open
#6,940 0 comments 0 reactions 1 assignee Claimed by @realforest2001 View on GitHub
Bug
Dominant language
DM
Stars
170
Forks
940
Avg merge
5d 16h
Merged PRs (30d)
61

Description

## Testmerges
#6334: 'Xenomorph Endgame' by Git-Nivrak at commit 8d2cc8fb83
#6071: '[V] Sorokyne Strata: Expanded Small corridors, removed 3000 unused tiles, Xenos can now weed everything except LZ's and surrounding of LZ's, allow LAZ for CAS inside structures with light blue Tacmap Areas (glass ceiling hallways)' by Venuska1117 at commit 817ed55a47
#6248: 'New Map: LV-759 Hybrisa Prospera' by Zenith00000 at commit a897d80bba
#6682: 'Hugged changes' by zzzmike at commit 901f664a71
#6860: 'Mentor New Player Markers' by realforest2001 at commit e8eef22705
#6855: 'Non folding plasteel barricade' by Blundir at commit d277c0e46f
#6939: 'Dropship 3 'Resolute'' by realforest2001 at commit 3154f91786
#6824: 'Human bursting sounds + sprite, new hugging sounds' by Blundir at commit 05f4f31df8
#4818: 'Synthetic Wrist Computer' by realforest2001 at commit d47f9a0723

## Round ID
23482

## Description of the bug
title

## What's the difference with what should have happened?
admin-event related dropship that marines are RPing around shouldnt be able to be pulled down for hijack, it should just select between alamo and normandy. RP-wise they wouldnt have known about the random CLF dropship that crashed anyways

## How do we reproduce this bug?
1. have admin event dropship on the ship
2. xenos call down a dropship
3. the dropship selected is neither the normandy nor the alamo but the event dropship

## Attached logs
```
N/A
```

## Additional details
- Author: Doomvoyager
- Admin: Marrone
- Note: None

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.