Skip to content

Stabilise the damage source experiment #8333

@bluelhf

Description

@bluelhf

Suggestion

Damage sources by @Absolutionism were initially marked as experimental because they used unstable Bukkit API. I propose we stabilise the experiment.

Why?

The relevant Bukkit APIs have been marked as stable since 1.21.7. SkBee has had damage source syntax for a while now, and Shane reported no breaking changes to the API. This means we should be good to just stabilise the syntaxes even before we stop supporting the last version in which the API was unstable (1.21.6).

Other

Minecraft 1.21.6 released on the 17th of June, 2025. This means that our 18-month support window for the unstable API closes on the 17th of December, 2026. Since there appear to be no breaking API changes, we should be able to stabilise the experiment even before this window closes.

Agreement

  • I have read the guidelines above and affirm I am following them with this suggestion.

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementFeature request, an issue about something that could be improved, or a PR improving something.good first issueAn issue that would be good for a first-time contributor to make a PR for

    Type

    No type

    Projects

    Status

    Planned Issues

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions