-
-
Notifications
You must be signed in to change notification settings - Fork 414
EntityData Parse Tags #7972
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
Merged
sovdeeth
merged 6 commits into
SkriptLang:dev/feature
from
Absolutionism:dev/EntityDataParseTags
Jun 30, 2025
Merged
EntityData Parse Tags #7972
sovdeeth
merged 6 commits into
SkriptLang:dev/feature
from
Absolutionism:dev/EntityDataParseTags
Jun 30, 2025
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
APickledWalrus
approved these changes
Jun 26, 2025
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
looks good, couple ideas i had while looking through (perhaps not in scope)
Efnilite
approved these changes
Jun 26, 2025
sovdeeth
approved these changes
Jun 30, 2025
…taParseTags # Conflicts: # src/main/resources/lang/default.lang
…taParseTags # Conflicts: # src/main/java/ch/njol/skript/entity/EntityData.java # src/main/resources/lang/default.lang
Burbulinis
pushed a commit
to Burbulinis/Skript
that referenced
this pull request
Jul 9, 2025
* Initial Commit * Additional Cleanup * Update default.lang
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
completed
The issue has been fully resolved and the change will be in the next Skript update.
enhancement
Feature request, an issue about something that could be improved, or a PR improving something.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Problem
EntityData utilized the parse marks to determine the plurality and baby state of a pattern. This could be confusing when looking at the patterns and seeing
1,2,4and8rather than specific terminology.Solution
entitiessection in thedefault.langin favor of parse tags. Including theage pattern1has been replaced withplural2has been replaced withunknown_plural4has been replaced withbaby8has been replaced withadultage patterndefault with no specified age state now usesunknown_ageentitiessection for describing the usages of these tagsEntityData#initto remove the usage/check for parse marks in favor of parse tagsTesting Completed
quickTestSupporting Information
N/A
Completes: none
Related: none