Skip to content

Add option to control DeathBan with GlobalReviveUnDeathBan schedule#44

Merged
Nergly merged 1 commit intomasterfrom
codex/find-all-placeholders-for-plugin
Apr 24, 2026
Merged

Add option to control DeathBan with GlobalReviveUnDeathBan schedule#44
Nergly merged 1 commit intomasterfrom
codex/find-all-placeholders-for-plugin

Conversation

@Nergly
Copy link
Copy Markdown
Owner

@Nergly Nergly commented Apr 24, 2026

Motivation

  • Allow the server to let a single global revive/un-death-ban schedule enable or disable the death ban system so admins can centrally control whether death bans are active.

Description

  • Add a new boolean field controlUseDeathBanWithGlobalReviveUnDeathBan with a getter and include it in the constructor and deserialization process in ConfigurationDeathBan.
  • Update ConfigurationDeathBan.deserialize to read ControlUseDeathBanWithGlobalReviveUnDeathBan from the config and populate the new field.
  • Change isUseDeathBan to return false if useDeathBan is false, return true if the control flag is false, and otherwise consult getConfigurations().getReviveConfiguration().getGlobalReviveUnDeathBanConfiguration().isEnabled() to determine runtime state.
  • Add ControlUseDeathBanWithGlobalReviveUnDeathBan: false and explanatory comments to config.yml so the behavior is configurable by server operators.

Testing

  • Performed a local project build to verify the code compiles successfully after the changes.
  • No automated unit tests were added or modified in this change and the existing test suite was left unchanged.

Codex Task

@Nergly Nergly merged commit d9292a8 into master Apr 24, 2026
Nergly added a commit that referenced this pull request Apr 24, 2026
…s-for-plugin"

This reverts commit d9292a8, reversing
changes made to 20844a3.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant