#(gageg23) End Crystal Explosion trigger
1 messages · Page 1 of 1 (latest)
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.
Help us help you by pasting your script to https://paste.denizenscript.com/New/Script and linking it back here.
!e entity explodes
Entity
<entity> explodes
when an entity explodes (primed_tnt, creeper, etc).
<context.blocks> returns a ListTag of blocks that the entity blew up.
<context.entity> returns the EntityTag that exploded.
<context.location> returns the LocationTag the entity blew up at.
<context.strength> returns an ElementTag(Decimal) of the strength of the explosion.
ListTag(LocationTag) to set a new lists of blocks that are to be affected by the explosion.
ElementTag(Decimal) to change the strength of the explosion.
True - this adds switches in:<area> + location_flagged:<flag name>.
True - this adds <context.cancelled> and determines cancelled + cancelled:false.
on ender_crystal explodes
in one specific world
can usein:world_nameswitch
!lang Advanced Object Matchables
Script events have a variety of matchable object inputs, and the range of inputs they accept may not always be obvious.
For example, an event might be "player clicks <block>"... what can "<block>" be filled with?
"<block>" usually indicates that a LocationTag and/or MaterialTag will be matched against.
This means you can specify any valid block material name, like "stone" or "air", like "on player clicks stone:" (will only run the event if the player is clicking stone)
You can also use a catch-all such as "block", like "on player clicks block:" (will always run the event when the player clicks anything/anywhere)
You can also use some more complicated matchables such as "vanilla_tagged:", like "on player clicks vanilla_tagged:mineable/axe:" (will run if the block is mineable with axes)
(Fo...
Object System
on ender_crystal explodes in:world_name
just break instead
You can just- drop end_crystal <context.location>
!tias
Try it and see!
If somebody pulled this up for you, you're probably asking a question of the public channel that's easier and faster to figure out by just attempting your idea in-game and looking at the result of that attempt.
Sorry, I meant I tried it and it doesen't work.
!info haste debug
Help us help you by pasting your script to https://paste.denizenscript.com/New/Script and linking it back here.
If you need help with a script issue, one of the most powerful tools Denizen has to offer is full debug output. This is displaying in your console whenever scripts are running until you turn debug off. To share a debug log quickly and easily with helpers, simply run the command /denizen debug -r in-game to begin recording, then run through the part of the script you need help with, then run the command /denizen submit. This will give you a link to a paste of the debug log, which you can then copy/paste back to us!
Content of Server Log Paste #119428: Denizen Debug Logs From A development server... pasted 2024/01/13 12:28:09 UTC-08:00, Paste length: 893 characters across 16 lines, Content: Java Version: 18.0.2.1Up-time: 26m
Content of Server Log Paste #119428: Denizen Debug Logs From A development server... pasted 2024/01/13 12:28:09 UTC-08:00, Paste length: 893 characters across 16 lines, Content: Java Version: 18.0.2.1Up-time: 26m
Paper version git-Paper-318 (MC: 1.20.2)-- (:warning: Outdated build, behind by 67... Current build is 385)
Citizens: 2.0.33-SNAPSHOT (build 3282) -- (:warning:Outdated build, behind by 19)
Denizen: 1.2.9-SNAPSHOT (build 1800-REL) -- (Outdated build, behind by 2)
@limpid drift
4 (:white_check_mark: Online)
18.0.2.1 :warning: - Only Java versions 17, 16, and 8 are fully supported
WorldGuard: 7.0.9+5934e49
TAB: 4.1.2 - This plugin adds Below_Name scoreboards to NPCs.
ViaVersion: 4.9.2 - Mixed client vs server versions can sometimes cause packet-related issues.
Multiverse-Core: 4.3.12 - Multi-world configuration plugins may affect NPCs in unexpected ways.
FastAsyncWorldEdit: 2.8.5-SNAPSHOT-639;a4a1126 - This plugin has been known to break the plugin load order on many servers, due to usage of the 'loadbefore' directive in its 'plugin.yml'.