Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

parsed as breaks with capitalization #7621

Open
1 task done
TheLimeGlass opened this issue Feb 15, 2025 · 0 comments
Open
1 task done

parsed as breaks with capitalization #7621

TheLimeGlass opened this issue Feb 15, 2025 · 0 comments
Labels
bug An issue that needs to be fixed. Alternatively, a PR fixing an issue.

Comments

@TheLimeGlass
Copy link
Contributor

TheLimeGlass commented Feb 15, 2025

Skript/Server Version

[23:49:15 INFO]: [Skript] Server Version: 1.21.4-144-edacfdf (MC: 1.21.4)
[23:49:15 INFO]: [Skript] Skript Version: 2.10.1-lime (selfbuilt-unknown)
[23:49:15 INFO]: [Skript] Installed Skript Addons:
[23:49:15 INFO]: [Skript]  - skript-reflect v2.6 (https://github.com/SkriptLang/skript-reflect)
[23:49:15 INFO]: [Skript] Installed dependencies:
[23:49:15 INFO]: [Skript]  - WorldGuard v7.0.13-beta-2+5c4848b

Bug Description

Doing "LimeGlass's II" parsed as "%player%'s II" breaks, but if you make the letters lowercase after the spacing like "LimeGlass's ii" parsed as "%player%'s ii" it'll work. This happens with any letter. \broadcast "LimeGlass's Z" parsed as "%player%'s Z" does nothing, but lowercase z will work.

Expected Behavior

To be able to parse out as LimeGlass (Player object) regardless if the next letter after a space is uppercase or lowercase.

Notes

Remember that parsed as returns as a list, this is because you can have multiple types in the matching string.
I suspect that the classinfo is being considered a multiple look up, and it's looking for multiple players to parse, when I only provided %player% and not %players% or it's some weird gender noun issue, because it's relating to capitalization.

Only players present on the server is myself LimeGlass

Agreement

  • I have read the guidelines above and affirm I am following them with this report.
@erenkarakal erenkarakal added the bug An issue that needs to be fixed. Alternatively, a PR fixing an issue. label Feb 18, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug An issue that needs to be fixed. Alternatively, a PR fixing an issue.
Projects
None yet
Development

No branches or pull requests

2 participants