Satchel Charges

[LynxSolstice]

About the pull request

Implements the satchel charges and detonators originally coded and abandoned by Totalepicness5.

Explain why it's good for the game

It's C4 that explodes on command, useful for Engineer players to clear a large amount of obstacles at once, they can be countered by taking out the engineer or aciding the charges. They're pretty obvious so they're hard to use for traps, plus the 4 second detonation delay makes it hard to chuck and blow up immediately, not to mention the arming time of 3 seconds from tossing it on top of that. I could maybe see them used to style on crit xenos, but they should end up being used pretty properly for obstacle clearing.

Testing Photographs and Procedure

Screenshots & Videos

Link to the video on Discord!

Changelog

🆑LynxSolstice, Totalepicness5, Thwomper
add: Added satchel charges and the accompanying detonator, added new handling sounds for the satchel charges and detonator (by Thwomper)
imageadd: Added sprites for the satchel charges and detonator (by Thwomper)
/:cl:

[Blundir]

The warning animation is too fast, make it slower, at least the same speed other things with warnings have, otherwise looks fine.

[Blundir]

Whoops

[LynxSolstice]

The warning animation is too fast, make it slower, at least the same speed other things with warnings have, otherwise looks fine.

Fixed!

[Nanu308]

I wish to see this on live, currently from the preview and looking at code I am worried it might be too strong, but we'll see!
adding tm label

[LynxSolstice]

I wish to see this on live, currently from the preview and looking at code I am worried it might be too strong, but we'll see! adding tm label

It was previously TM'd and was seen to be quite, as far as I know, balanced, as not many concerns were brought up, however we'll see how the second test goes!

[cmss13-ci]

This PR has been inactive for long enough to be automatically marked as stale. This means it is at risk of being auto closed in ~ 7 days, please address any outstanding review items and ensure your PR is finished, if these are all true and you are auto-staled anyway, you need to actively ask maintainers if your PR will be merged. Once you have done any of the previous actions then you should request a maintainer remove the stale label on your PR, to reset the stale timer. If you feel no maintainer will respond in that time, you may wish to close this PR youself, while you seek maintainer comment, as you will then be able to reopen the PR yourself

[cm13-github]

This pull request has conflicts, please resolve those before we can evaluate the pull request.

[LynxSolstice]

Fixing conflicts

[kiVts]

fix conflicts

[kiVts]

actually, this is two weeks old, closing due to stale, ask someone to reopen