is enchanted condition docs update for level

[Blacksoul16]

Skript/Server Version

Server Version: git-Paper-409 (MC: 1.16.4)
Skript Version: 2.6
Installed Skript Addons:
- Skacket v1.0.5
- skript-gui v1.3-alpha1 (https://github.com/APickledWalrus/skript-gui)
- Skellett v1.9.11 (https://forums.skunity.com/resources/skellett.24/)
- skDragon v0.16
- skript-reflect v2.2.3 (https://github.com/TPGamesNL/skript-reflect)
- skUtilities v0.9.2 (https://tim740.github.io/)
- skRayFall v1.9.25 (https://sk.rayfall.net/)
- SkQuery v4.1.4
- SkBee v1.11.2 (https://github.com/ShaneBeee/SkBee)
- SkJade v1.3.2 (https://www.github.com/Ankoki-Dev/SkJade)
- skript-holo v1.0.2 (https://github.com/Blueyescat/skript-holo)

Bug Description

When you use "!send "Yes" if me's tool is enchanted with sharpness 2" with an item that has sharpness 2 in hand, obviously the condition is met, the problem starts when you put "sharpness 1" (in the effect command) or a number lower than the item's enchantment, also the condition is met when it shouldn't be. The condition is not met with a number higher than the item's enchantment level.

Expected Behavior

The condition should be met only at the specified level, not at levels lower than the enchantment.

Steps to Reproduce

1. Enchant an item with any enchantment level.
2. Run the effect command mentioned above while holding the item.

Errors or Screenshots

This is the item I tested with:

And here is the ouput of everything I said before (The only change is that I put "to console" to make the example look cleaner).

Other

No response

Agreement

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

[TPGamesNL]

This is intended behaviour: if tool is enchanted with sharpness X should return true if the tool has at least sharpness X. If you want to check the exact level, use the enchantment level expression.
However, the docs of the is enchanted condition should be updated to specify this behaviour.

[AyhamAl-Ali]

@TPGamesNL assign it to me please

[AyhamAl-Ali]

I will not include this in the docs PR rather I will update it in this PR #4366 since it changes the condition's behavior