Skip to content

EntityPotionCause and DamageCause conflict with the attack enum #7589

@Fusezion

Description

@Fusezion

Skript/Server Version

[10:05:19 INFO]: [Skript] Skript's aliases can be found here: https://github.com/SkriptLang/skript-aliases
[10:05:19 INFO]: [Skript] Skript's documentation can be found here: https://docs.skriptlang.org/
[10:05:19 INFO]: [Skript] Skript's tutorials can be found here: https://docs.skriptlang.org/tutorials
[10:05:19 INFO]: [Skript] Server Version: 1.21.4-138-5395ae3 (MC: 1.21.4)
[10:05:19 INFO]: [Skript] Skript Version: 2.10.1 (skriptlang-github)
[10:05:19 INFO]: [Skript] Installed Skript Addons: None
[10:05:19 INFO]: [Skript] Installed dependencies: None

Bug Description

Both the EntityPotionCause classinfo and DamageCause classinfos have a conflicting type of attack in which EntityPotionCause appears to take priority when used within variables

Expected Behavior

Skript to not have a conflict between the EntityPotionCause and DamageCause types

Steps to Reproduce

command /testing:
  trigger:
    set {_a} to attack
    #send "SkriptType: %skript type of {_a}%" # (easier if you have skbee too)
    send "attack is (DamageCause) attack: %whether {_a} is ("attack" parsed as damage cause)%"
    send "attack is (EntityPotionCause) attack: %whether {_a} is ("attack" parsed as entity potion effect cause)%"

Errors or Screenshots

Image

Other

No response

Agreement

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugAn issue that needs to be fixed. Alternatively, a PR fixing an issue.completedThe issue has been fully resolved and the change will be in the next Skript update.

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions