-
-
Notifications
You must be signed in to change notification settings - Fork 370
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
Breedable & Ageable Stuff #5584
Conversation
This reverts commit a437ca9.
📎 Added EntityEnterLoveModeEvent 🐷 Added EntityBreedEvent ✨ Added EventValues for these events
👪 Added family expression for Father, Mother, Child, and Breeder ✨ Added breeding experience to experience class *update class to current standards
✨ Added condition for checking ageable ✨ Added condition for checking breedable ✨ Added effect for toggle breedable ✨ Added effect for locking age ✨ Added expression for love ticks
🐛 Fixed issue with `livingentities` 🐛 Added class exist checks for Breedable instances ✨ Added RequirePlugins annotation to select classes
📋 Added test for ExprLoveTime & CondIsInLove 📋 Addes test for EffBreedable & CondCanBreed 📋 Added test fpr EffLockAge & CondCanAge
This comment was marked as resolved.
This comment was marked as resolved.
✨ Added Condition for checking is adult ✨ Added Effect to make an entity a baby or adult 📋 Added test for these syntaxes 🔵 1.16 for any mob, below that is animals only
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.
Nice PR ⚡, It's better to split features in multiple PRs next time to avoid such big review and requested changes :)
src/main/java/ch/njol/skript/classes/data/BukkitEventValues.java
Outdated
Show resolved
Hide resolved
src/main/java/ch/njol/skript/classes/data/BukkitEventValues.java
Outdated
Show resolved
Hide resolved
src/main/java/ch/njol/skript/classes/data/BukkitEventValues.java
Outdated
Show resolved
Hide resolved
Thanks for all these formatting changes it's just what I wanted when waking up Co-authored-by: Ayham Al Ali <[email protected]>
✨ Renamed expression to ExprLoveTicks ✨ Added support for ticks via integers 📋 Added a new test for using integers 📋 Removed unneeded test condition
✨ Changed expression for father, mother and offspring a bit ✨ Converted get to a switch statement
🐛 Fixed an issue where set allowed more than one value 🐛 Fixed a typo in examples ✨ Added a spacer to examples
Co-Authored-By: Ayham Al Ali <[email protected]>
Failing on |
Fixed in #5587, not related to this PR. |
Didn't intend to really add so much stuff, love ticks made sense due to breedable, and ageable was just close enough to each other I found it fair. Most requested changes seem to be formatting which is just caused by how little I mess with PRs it'll get better over time. |
All good for now. It's just easier for us to review and easier for you to handle requested changes as the larger the PR is the more time it requires to review/change/merge As for the formatting stuff, it's just a matter of time as you stated. |
Just adds some notes in descriptions to bring more light to animal exclusive syntax Co-Authored-By: Ayham Al Ali <[email protected]>
Co-authored-by: LimeGlass <[email protected]>
Co-authored-by: LimeGlass <[email protected]>
…kript-forky into enhancement/Breedable
bd134d0
to
3f08853
Compare
|
||
static { | ||
if (Skript.classExists("org.bukkit.entity.Breedable")) | ||
Skript.registerEffect(EffLockAge.class, "(lock|:unlock) age of %livingentities%"); |
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.
It would be good to support syntax like allow entities to age
or prevent entities from aging
private static final boolean HAS_MOB_SUPPORT = Skript.isRunningMinecraft(1, 16, 5); | ||
|
||
static { | ||
register(CondIsAdult.class, "[an] adult", "livingentities"); |
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.
maybe worth including a child
option?
@RequiredPlugins("MC 1.16.5+ (Mobs)") | ||
public class CondIsAdult extends PropertyCondition<LivingEntity> { | ||
|
||
// This is required since before 1.16 the 'isAdult' method only supported Animals |
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.
does it throw an error or something when called on a non Animals mob?
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.
My initial worry of this from what I see is unfounded, the same goes for the effect version, the ageable instance check already handles this, I just needed to make mentions in the description annotation
|
||
@Name("Make Breedable") | ||
@Description({ | ||
"Picks whether or not entities will be able to breed.", |
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.
"Picks whether or not entities will be able to breed.", | |
"Sets whether or not entities will be able to breed.", |
.requiredPlugins("MC 1.16+"); | ||
} | ||
|
||
Skript.registerEvent("Player Pickup Arrow", SimpleEvent.class, PlayerPickupArrowEvent.class, "[player] (pick[ing| ]up [an] arrow|arrow pick[ing| ]up)") |
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.
Skript.registerEvent("Player Pickup Arrow", SimpleEvent.class, PlayerPickupArrowEvent.class, "[player] (pick[ing| ]up [an] arrow|arrow pick[ing| ]up)") | |
Skript.registerEvent("Player Pickup Arrow", SimpleEvent.class, PlayerPickupArrowEvent.class, "[player] (pick[ing| ]up [an] arrow|arrow pick[ing| ]up)") |
@@ -733,7 +735,25 @@ public class SimpleEvents { | |||
.requiredPlugins("Paper 1.16+"); | |||
} | |||
|
|||
Skript.registerEvent("Player Pickup Arrow", SimpleEvent.class, PlayerPickupArrowEvent.class, "[player] (pick[ing| ]up [an] arrow|arrow pick[ing| ]up)") | |||
Skript.registerEvent("Entity Breed", SimpleEvent.class, EntityBreedEvent.class, "[entity] breed[ing]") |
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.
I think it could be a good idea for these events to support triggering conditions (e.g. on pig breed
) using a dedicated event class
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.
hmm, not a bad idea, I'll need to relook at this PR again soon, with all the changes recently there's bound to be one or two conflicts in addition to all the changes regarding conventions
Skript.registerExpression(ExprBreedingFamily.class, LivingEntity.class, ExpressionType.SIMPLE, | ||
"breed[ing] mother", | ||
"breed[ing] father", | ||
"[bred] (offspring|child)", | ||
"breeder"); |
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.
Skript.registerExpression(ExprBreedingFamily.class, LivingEntity.class, ExpressionType.SIMPLE, | |
"breed[ing] mother", | |
"breed[ing] father", | |
"[bred] (offspring|child)", | |
"breeder"); | |
Skript.registerExpression(ExprBreedingFamily.class, LivingEntity.class, ExpressionType.SIMPLE, | |
"[the] breed[ing] mother", | |
"[the] breed[ing] father", | |
"[the] [bred] (offspring|child)", | |
"[the] breeder"); |
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.
Thoughts about removing the optional [ing]
in favor of forcing it; for mother and father?
I don't like breed father
or the breed father
return CollectionUtils.array(ExprExperience.class, Integer.class); | ||
case ADD: | ||
case REMOVE: | ||
return CollectionUtils.array(ExprExperience[].class, Integer[].class); |
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.
return CollectionUtils.array(ExprExperience.class, Integer.class); | |
case ADD: | |
case REMOVE: | |
return CollectionUtils.array(ExprExperience[].class, Integer[].class); | |
return CollectionUtils.array(Experience.class, Integer.class); | |
case ADD: | |
case REMOVE: | |
return CollectionUtils.array(Experience[].class, Integer[].class); |
This isn't supposed to be ExprExperience, right?
public Class<?>[] acceptChange(ChangeMode mode) { | ||
switch (mode) { | ||
case SET: | ||
case RESET: |
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.
maybe worth support delete as in clear love time
?
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.
Looking over this PR again, and I want some feedback on a few things before I ship anything
Skript.registerExpression(ExprBreedingFamily.class, LivingEntity.class, ExpressionType.SIMPLE, | ||
"breed[ing] mother", | ||
"breed[ing] father", | ||
"[bred] (offspring|child)", | ||
"breeder"); |
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.
Thoughts about removing the optional [ing]
in favor of forcing it; for mother and father?
I don't like breed father
or the breed father
if (Skript.classExists("org.bukkit.entity.Breedable")) | ||
Skript.registerEffect(EffBreedable.class, "make %livingentities% [negate:(not |non(-| )|un)]breedable"); | ||
} |
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.
I'm personally not a huge fan of not breedable
do we believe it's fine to remove as I don't think of it as valid
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.
go for it
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.
personally i like prevent %entities% from breeding
or the more risque sterilize %entities%
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.
I believe my latest build does add prevent and allow formatting, sterilize is possible but I'll probably put it on the back burner for now.
@Efnilite will be taking this over |
Description
This PR aims to add breeding support along with syntax related to breeding and aging.
Added ✨ EntityBreedEvent MC 1.13+
Added ✨ EntityEnterLoveModeEvent PAPER 1.16+
Added ✨ ExprBreedingFamily MC 1.13+
Added ✨ CondCanAge, CondCanBreed MC 1.16+
Added ✨ EffLockAge, EffBreedable MC 1.16+
Added ✨ ExprLoveTime MC 1.16+ *if anyone has a better name please help
Updated 📋 ExprExperience
Added ✨ CondIsAdult MC 1.13+ (Req: 1.16+ for any non animal)
Added ✨ EffMakeAdult MC 1.13+ (Req: 1.16+ for any non animal)
*the method I used for telling if using 1.16+ if there's any other alternative please let me know
Breaks 🪦 Removes
remove_all
support from ExprExperience, people using it before will breakSome of these 1.16 events could of been added under the Ageable class instead of Breedable which would allow earlier versions, however I find it better to use Breedable in this case then Ageable as it makes more sense. If anyone would prefer Ageable please let me know.
Target Minecraft Versions: 1.13+, 1.16+ & Paper 1.16+
Requirements: Breed event 1.13, Enter love mode paper 1.16, rest 1.16
Related Issues: #5111
Additional: this PR is the updated one for #5116 I accidently did some issues as such just decided to recode it.
Majority if not all of the requested changes there should transfer here, however I've added much more syntax compared to before.