Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CMB Spam Update - CL can now print Blackmarket Scanners from their Briefcase #7458

Closed
wants to merge 1 commit into from

Conversation

efzapa
Copy link
Contributor

@efzapa efzapa commented Oct 31, 2024

About the pull request

CL can now print Blackmarket Scanners from their Briefcase for 50 points each

Explain why it's good for the game

Adds more CL fluff, since the role is in desperate need of mechanical things to do. This should give the CL the option to spice up the round for both them and req should they both choose.

Testing Photographs and Procedure

Screenshots & Videos

Put screenshots and videos here with an empty line between the screenshots and the <details> tags.

Changelog

🆑
add: CL can now print Blackmarket Scanners from their Briefcase for 50 points each.
/:cl:

@cmss13-ci cmss13-ci bot added the Feature Feature coder badge label Oct 31, 2024
@BeagleGaming1
Copy link
Contributor

The blackmarket scanner used to always be available, then it was made rare so it wouldn't happen every round. This would just cause it to happen every round again.

@efzapa
Copy link
Contributor Author

efzapa commented Nov 1, 2024

The blackmarket scanner used to always be available, then it was made rare so it wouldn't happen every round. This would just cause it to happen every round again.

"rare" as in praying for RNG to be on your side
if there was a definitive way to get a scannner, even if it was difficult it would be fine
but banking a fun feature on pure RNG is a bad way to do it

in any case we can TM it, if it is abused then I can scrap this PR and make another rebalancing BM

@efzapa
Copy link
Contributor Author

efzapa commented Nov 1, 2024

actually gonna work on another PR that should fix the abundance problem then just PR that instead of this

@efzapa efzapa closed this Nov 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Feature Feature coder badge
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants