WY Security Surv on LV-624 spawns with M20A gun but empty belt

Open Beginner friendly
#13,195 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
70/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Domain
game-dev

Research direction

Start by checking the survivor security loadout for LV-624 and the M20A weapon setup. Compare the spawned rifle with its main belt contents; done means security survivors who spawn with an M20A also receive a full belt of matching ammunition.

Written by the indexing model from the issue text.

Description

Bug

Testmerges

#12947: 'Revert "Working multiz tacmap, round two, extra buttons"' by Rain7x at commit ea384007a4
#12627: 'Tyrargo Rift (2) - Various Alterations' by Steelpoint at commit 3f05646f8d
#12967: 'Balance: Allows pill bottles to be forced open by bayonets' by antlersss at commit 98470554f7
#13037: 'Survivors now grant half a larva on permadeath but no extra on burst' by Drulikar at commit 73d6ec8fea
#11128: '[code beet] dissolver (used to be venator)' by cuberound at commit e233d6c0ff
#13155: 'White Antre LZ Redesign + Rebalance Of Hull Walls' by Steelpoint at commit 17b6fb6e41
#12739: 'Sun mk3' by cuberound at commit b6d94c25bb
#12503: 'LACNification of New Varadaro' by Drazamuffin at commit e4b809c770

Round ID

36539

Description of the bug

Spawned with M20A Rifle, but had no ammo for it in main belt slot

What's the difference with what should have happened?

sec survs should spawn with a gun and belt full of ammo for that respective weapon

How do we reproduce this bug?

check loadouts for sec surv that spawns with m20a

Attached logs

N/A

Additional details

  • Author: Tacoloaf
  • Admin: the thepolynomer
  • Note: None
Dominant language
DM
Stars
170
Forks
944
Avg merge
5d 22h
Merged PRs (30d)
52

Contributor guide

Open the contributing guide

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 cmss13-devs/cmss13

All issues in cmss13-devs/cmss13

Similar issues

More Game Dev issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.