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

Makes flare gun not use ChamberMagazineAmmoProvider #33291

Open
wants to merge 7 commits into
base: master
Choose a base branch
from

Conversation

SpaceRox1244
Copy link
Contributor

About the PR

Adds optional bolt mechanics to the BallisticAmmoProvider component so that the reworked flare gun can make use of them while still enabling things like accepting ammo from shell dispensers. Generally enables break action ballistic weapons that can actually break open.

Why / Balance

Making the flare gun use ChamberMagazineAmmoProvider for the bolting mechanics felt inappropriate, but I think what it aimed to accomplish was cool enough that I wanted to help out and give the desired bolting mechanics to the ammo provider it previously used.

Technical details

For transparency, alot of the code for bolting on ballistic weapons was taken from bolting on magazine weapons, but repurposed and tested to the best of my ability. Considering that not-weapons like the ammo boxes also use the BallisticAmmoProvider component, I made sure to test everything thoroughly and I show proof that the boxes still work in the provided video.

Media

2024-11-13.01-05-06.mp4

Requirements

Breaking changes

I dont think that it is a breaking change, but I want to note that one of the differences between the current reworked flare gun and the one in this PR is that this flare gun auto ejects its shells when firing. The ChamberMagazineAmmoProvider has the benefit of an AutoCycle data field. I tried to implement this for ballistic guns, but I ran into issues that caused exceptions involving the "unspawned ammo" that is present in a shotgun when it is first spawned in.

Changelog

I dont think CL is necessary

@github-actions github-actions bot added the S: Needs Review Status: Requires additional reviews before being fully accepted label Nov 13, 2024
@SlamBamActionman SlamBamActionman added the S: Untriaged Status: Indicates an item has not been triaged and doesn't have appropriate labels. label Nov 14, 2024
@SaphireLattice SaphireLattice added P2: Raised Priority: Item has a raised priority, indicating it might get increased maintainer attention. T: New Feature Type: New feature or content, or extending existing content D2: Medium Difficulty: A good amount of codebase knowledge required. A: Combat Area: Combat features and changes, balancing, feel A: Core Tech Area: Underlying core tech for the game and the Github repository. and removed S: Untriaged Status: Indicates an item has not been triaged and doesn't have appropriate labels. labels Nov 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A: Combat Area: Combat features and changes, balancing, feel A: Core Tech Area: Underlying core tech for the game and the Github repository. D2: Medium Difficulty: A good amount of codebase knowledge required. P2: Raised Priority: Item has a raised priority, indicating it might get increased maintainer attention. S: Needs Review Status: Requires additional reviews before being fully accepted T: New Feature Type: New feature or content, or extending existing content
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants