Skip to content

feat: Added SpawnReasons and RoleSpawnFlags to CustomRole and some item/ammo fixes #554

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

Closed
wants to merge 7 commits into from

Conversation

Bonjemus
Copy link

Description

Describe the changes
Read title.

What is the current behavior? (You can also link to an open issue here)
Currently CustomRole always uses ForceClass as a SpawnReason and doesn't allow devs to specify RoleSpawnFlags.
Additionally, CustomRole behaviours when it comes to ammo and items was inconsistent so I also fixed it.

What is the new behavior? (if this is a feature change)
Read title.

Does this PR introduce a breaking change? (What changes might users need to make in their application due to this PR?)
Nope, some methods became obsolete though :

  • AddRole
  • RoleAdded
  • RemoveRole

Other information:


Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)
  • Documentations

Submission checklist

  • I have checked the project can be compiled
  • I have tested my changes and it worked as expected

Patches (if there are any changes related to Harmony patches)

  • I have checked no IL patching errors in the console

Other

  • Still requires more testing

BoltonDev and others added 4 commits June 13, 2025 12:15
## Description
**Describe the changes** 


**What is the current behavior?** (You can also link to an open issue
here)


**What is the new behavior?** (if this is a feature change)


**Does this PR introduce a breaking change?** (What changes might users
need to make in their application due to this PR?)


**Other information**:

<br />

## Types of changes
<!--- What types of changes does your code introduce? Put an `x` in all
the boxes that apply: -->
- [ ] Bug fix (non-breaking change which fixes an issue)
- [ ] New feature (non-breaking change which adds functionality)
- [ ] Breaking change (fix or feature that would cause existing
functionality to change)
- [ ] Documentations
<br />

## Submission checklist
<!--- Put an `x` in all the boxes that apply: -->
- [ ] I have checked the project can be compiled
- [ ] I have tested my changes and it worked as expected

### Patches (if there are any changes related to Harmony patches)
- [ ] I have checked no IL patching errors in the console

### Other
- [ ] Still requires more testing
@Bonjemus Bonjemus changed the base branch from master to dev June 16, 2025 12:47
@Bonjemus Bonjemus closed this Jun 16, 2025
@Bonjemus Bonjemus deleted the master branch June 16, 2025 12:59
@Bonjemus Bonjemus restored the master branch June 16, 2025 13:00
@Bonjemus Bonjemus deleted the master branch June 16, 2025 13:02
@Bonjemus Bonjemus restored the master branch June 16, 2025 13:02
@Bonjemus Bonjemus reopened this Jun 16, 2025
@github-actions github-actions bot added the API label Jun 16, 2025
@Bonjemus Bonjemus closed this Jun 16, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants