-
-
Notifications
You must be signed in to change notification settings - Fork 355
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
EffSecDrop #6745
Comments
I don't see the point of this. You can just spawn a dropped item with the spawn section and set the NBT of that just as easily via |
Concurrency — some might have some beefs with |
Skript does not run any code in parallel, so concurrency is not a concern. Also, you don't have to use last dropped item if you use the spawn section. |
I dont know if maybe I am just doing it wrong. But |
You need to use an item type, eg |
Hmm I'll have to look into that tonight, it should be valid. |
Looks like dropped items aren't spawnable through the normal methods, however, I think we should override the spawning method for DroppedItemData to allow it to be spawned normally via World#dropItem(). |
I think this is an issue from my EntityData#canSpawn thing. I'm starting to regret that. |
No, no, it's working properly! Bukkit doesn't allow you to spawn Item entities with World#spawn. I'm adding an override to the spawn method of its entityData so it can use dropItem right now :) |
Spawning item entities is valid after 2.8.6, so I'm closing this for now. If there's some feature that you think a drop section would have over the spawn section, please reopen or make a new PR! |
Suggestion
To add or change the drop effect to match the spawn effect.
With the Spawn effect, you have both
Effect
(spawn|summon) %entitytypes% [%directions% %locations%]
Effect Section
Im proposing for the drop effect to also have a section
Why?
This would allow users to add/set NBT+values of the dropped entity with a higher sense of accuracy.
Following suit of the spawn effect, minimalizing the usage of the
last spawned %entitytype%
Other
No response
Agreement
The text was updated successfully, but these errors were encountered: