Skip to content

BukkitClasses - make "effect" in PotionEffectType pattern non-optional#7440

Merged
sovdeeth merged 3 commits into
SkriptLang:dev/featurefrom
ShaneBeee:shane/more-potion-stuff-you-cant-stop-me
Mar 19, 2025
Merged

BukkitClasses - make "effect" in PotionEffectType pattern non-optional#7440
sovdeeth merged 3 commits into
SkriptLang:dev/featurefrom
ShaneBeee:shane/more-potion-stuff-you-cant-stop-me

Conversation

@ShaneBeee

Copy link
Copy Markdown
Contributor

Description

This PR aims to make "effect" non-optional in the "potion [effect] type" pattern.

A few reasons:

  1. it should be required, its the name
  2. Theres a class in Bukkit called PotionType, currently not used by Skript, but could in the future and cause conflict.
  3. Im adding PotionType to SkBee (on request) and the pattern conflicts.

As discussed with pickle this could technically cause a breaking change, but really....
send all potion types -> send all potion effect types
Thats probably it. (or looping... but who does that)


Target Minecraft Versions: any
Requirements: none
Related Issues: none

@Efnilite Efnilite added bug An issue that needs to be fixed. Alternatively, a PR fixing an issue. breaking changes Pull or feature requests that contain breaking changes (API, syntax, etc.) labels Jan 15, 2025
@Efnilite Efnilite added the feature-ready A PR/issue that has been approved, tested and can be merged/closed in the next feature version. label Feb 25, 2025
@sovdeeth sovdeeth merged commit 974be12 into SkriptLang:dev/feature Mar 19, 2025
@ShaneBeee ShaneBeee deleted the shane/more-potion-stuff-you-cant-stop-me branch March 19, 2025 23:53
erenkarakal pushed a commit to erenkarakal/Skript that referenced this pull request Nov 26, 2025
SkriptLang#7440)

* BukkitClasses - make "effect" in PotionEffectType pattern non-optional

* BukkitClasses - remove extra "?"
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

breaking changes Pull or feature requests that contain breaking changes (API, syntax, etc.) bug An issue that needs to be fixed. Alternatively, a PR fixing an issue. 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.

5 participants