Skip to content

feature: MaxTeamNadesPerType configuration#202

Open
erikpeik wants to merge 3 commits intoyonilerner:mainfrom
JonneKahvila:feature/MaxTeamNades
Open

feature: MaxTeamNadesPerType configuration#202
erikpeik wants to merge 3 commits intoyonilerner:mainfrom
JonneKahvila:feature/MaxTeamNades

Conversation

@erikpeik
Copy link

This pull request adds a new feature for configuring per-team, per-nade-type limits, allowing server admins to restrict specific grenade types (e.g., smokes) for each team and round type.

New configuration feature: Per-team, per-nade-type limits

  • Added the MaxTeamNadesPerType config option, allowing admins to set limits for each nade type per team and round type (e.g., max 2 smokes for Terrorists on pistol rounds). This is implemented in Configs.cs, NadeHelpers.cs, and described in the README.md.

  • The nade allocation logic in NadeHelpers.cs now enforces both per-player and per-team per-type limits when distributing grenades.

Documentation and configuration updates

  • Updated the README.md to document the new MaxTeamNadesPerType option, provide configuration examples, and improve formatting of external links.

Dependency and version updates

  • Upgraded CounterStrikeSharp.API dependency to version 1.0.341 in both RetakesAllocator.csproj and RetakesAllocatorCore.csproj.

- Introduced MaxTeamNadesPerType setting to limit specific nade types per team.
- Updated NadeHelpers to enforce per-type limits during allocation.
- Added tests to verify max nade restrictions for different round types.
- Bumped version to 2.5.0.
@erikpeik erikpeik changed the title Feature: MaxTeamNadesPerType configuration feature: MaxTeamNadesPerType configuration Jan 22, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant