Skip to content

Stabilise damage source experiment#8414

Open
tibisabau wants to merge 4 commits intoSkriptLang:dev/featurefrom
tibisabau:feature/stabilise-damage-source-experiment
Open

Stabilise damage source experiment#8414
tibisabau wants to merge 4 commits intoSkriptLang:dev/featurefrom
tibisabau:feature/stabilise-damage-source-experiment

Conversation

@tibisabau
Copy link

Problem

Damage sources were marked as experimental because they relied on unstable Bukkit APIs. The relevant Bukkit APIs have been stable since Minecraft 1.21.7 with no reported breaking changes, making the experimental status unnecessary.

Solution

Stabilized the damage source feature by removing experimental restrictions:

  • Changed DAMAGE_SOURCE lifecycle from LifeCycle.EXPERIMENTAL to LifeCycle.STABLE in Feature.java
  • Removed implements DamageSourceExperimentSyntax from all 9 damage source syntax element classes
  • Deleted the DamageSourceExperimentSyntax.java interface file as it's no longer needed

Testing Completed

  • ./gradlew clean build - Successful with 0 errors
  • ./gradlew clean quickTest - All tests passed, including:
    • "custom damage source" test case
    • "damage source error" test case
    • "damage source outside section error" test case

Supporting Information

This is not a breaking change. Existing scripts using using damage source will continue to work. Users can now use damage source syntax without the experimental declaration.


Completes: #8333
Related: none
AI assistance: GitHub Copilot with Claude Sonnet 4.5 model

The code in this pull request was generated by GitHub Copilot with the Claude Sonnet 4.5 model.

@tibisabau tibisabau requested a review from a team as a code owner January 28, 2026 22:57
@tibisabau tibisabau requested review from APickledWalrus and Pesekjak and removed request for a team January 28, 2026 22:57
@skriptlang-automation skriptlang-automation bot added the needs reviews A PR that needs additional reviews label Jan 28, 2026
@sovdeeth
Copy link
Member

This shopuld be pushing it to MAINSTREAM, not STABLE
See the for loops experiment

@sovdeeth
Copy link
Member

Should remove the experiment from the damage source tests too.

@sovdeeth sovdeeth added the enhancement Feature request, an issue about something that could be improved, or a PR improving something. label Jan 29, 2026
Copy link
Contributor

@Pesekjak Pesekjak left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

remove the UnstableApiUsage supression if everything in the affected classes is now stabilized api

@tibisabau tibisabau requested a review from Pesekjak January 30, 2026 10:25
@skriptlang-automation skriptlang-automation bot added feature-ready A PR/issue that has been approved, tested and can be merged/closed in the next feature version. and removed needs reviews A PR that needs additional reviews labels Jan 30, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement Feature request, an issue about something that could be improved, or a PR improving something. feature-ready A PR/issue that has been approved, tested and can be merged/closed in the next feature version.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants