lowers kilo's bombcap multiplier

[Fikou]

About The Pull Request

uses the map json system to set kilo's bombcap multiplier to 0.7
maptainer approval:

Why It's Good For The Game

i think it's a creative way to nerf bombs a little on kilo

Changelog

🆑
balance: lowers kilo's bombcap multiplier
/:cl:

[Sparkezel]

While its extremally hillarious I don't think that changing the balance of explosives is the right call to justify revelancy for kilo as an actual map. I understand that it was a lot of work to return Kilo back to more modern versions of tg, but it might be the time to let it go.

[IndieanaJones]

I'd rather have Kilo than Tram.

[Pickle-Coding]

I think it would be interesting if the bombcap multiplier was raised instead, because the station looks like it will crumble any second now.

[moocowswag]

Kilo has a lot of (bigger) issues and changing the balance of explosives on a single map will go wildly against consistency.

Also, will this only affect TTVs? Will it affect bomb assemblies bought from uplink? Will it affect large chemical bombs?

[Maurukas]

Based on this being tagged in so many issues, I'm assuming this is TM'd and actively being tested. Give me a ping when there's feedback.

[EOBGames]

Based on this being tagged in so many issues, I'm assuming this is TM'd and actively being tested. Give me a ping when there's feedback.

It is being actively testmerged, I coordinated that with the keyholders prior to my current community break. I also had planned to personally observe rounds but my present situation somewhat precludes that. @Maurukas on second thought however I do wonder if this PR might be something we can't gather reasonable data on from testmerges, given its targeting quite a specific issue and will need a good sample size, and there's no guarantee we're getting Kilo running, or bombs being detonated on station, during the testmerge period. I'm thinking a full merge with a review period in a few months (let's call it 2 months from merge just for the sake of saying something concrete, with potential for extension if we've not got enough data by that point), where we can properly comb logs and quiz admins and the playerbase on whether they think it's had a positive effect might be a better way forward for this change. Your input welcomed, of course.

[github-actions]

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