#(Darwin) entity targets entity: multiple causes
21 messages · Page 1 of 1 (latest)
(Darwin) entity targets entity: multiple causes
Hi I'm AutoThreadBot! Don't mind me, I'll just be adding the helper team to this thread so they can see it. A human will get to you soon.
You can block this bot if you don't want to see these messages, I won't mind.
<@&525394568410038282>
Thread is now a Feature thread. This indicates a request for a new feature to the plugin, that both (A) does not already exist and (B) reasonably can be added. If you are unsure whether this applies, use </helpthread:1028674284870180883> to change back to a normal help thread.
!e entity targets
Entity
<entity> targets (<entity>) (because <cause>)
when an entity targets a new entity - usually a hostile mob preparing to attack something.
when the entity being targetted is a player. - this adds switches flagged:<flag name> + permission:<node>, in addition to the <player> link.
<context.entity> returns the targeting entity.
<context.reason> returns the reason the entity changed targets. Refer to <@link url https://hub.sp...
<context.target> returns the targeted entity.
EntityTag to make the entity target a different entity instead.
True - this adds switches in:<area> + location_flagged:<flag name>.
True - this adds <context.cancelled> and determines cancelled + cancelled:false.
!mcve
Please create a Minimal, Complete, and Verifiable Example of the problem you're reporting.
Minimal: contains nothing other than the part that's broken (and bare minimum structure).
Complete: contains everything needed to demonstrate the issue.
Verifiable: Anybody should be able to throw it on their own server and see the problem happen for themselves, without any needed tinkering.
Didn't I?
Please can somebody add support for multiple causes in entity targets entity event
Currently only 1 cause per event is supported
added ref #commit-log
Has your issue been resolved, or your question been answered?
If so, please use the </resolved:1028673926114594866> command to close your thread.
Or </invalid:1028673926898909185> if it's not possible to resolve.
If not yet resolved, please reply below to tell us what you still need.
(Note that if there is no reply for a few days, this thread will eventually close itself.)
@spice mauve
Great. Thank you