💠Leak💠 ⭐ Executable Blocks ⭐ Add Activators on your blocks ! 5.24.10.20 [1.14-1.21]

For ExecutableBlocks(X.24.10.20):

• Feature enhancement

For SCore (all plugins) (X.24.10.20):

• Fixed an issue with a custom DAMAGE command that only affects the old 1.21 Paper build.

For SCore (all plugins) (X.24.10.1):
Fixes an issue for users of version 1.20.4 and below

For SCore (all plugins) (X.24.9.17):
Fixes minor issue

For SCore (All plugins) (X.24.8.25):

New, two custom commands :
HITSCAN_PLAYERS range:5 radius:0 pitch:0 yaw:0 leftRightShift:0 yShift:0 throughBlocks:true throughEntities:true COMMANDS HERE
HITSCAN_ENTITIES range:5 radius:0 pitch:0 yaw:0 leftRightShift:0 yShift:0 throughBlocks:true throughEntities:true COMMANDS HERE

Range: how far an entity can be to be targetted by the HITSCAN command
RadiusOfHitscan: How WIDE the cylinder is. It's basically the difference of shooting a bullet vs shooting a cannonball.
Pitch: What direction to shoot it in, relative to player pitch
Yaw: Samething
leftRightShift: -5 = the hitscan STARTS from 5 blocks to the left. 0 = Hitscan is centered where the player is. 5 = hitscan STARTS from 5 blocks to the right of the player.
yShift: Same as left,right, except with a different axis.
throughEntities: Boolean: Whether or not the HITSCAN can go through entities.
throughBlocks: Boolean: Whether or not the HITSCAN can go through blocks.
and for command sits the same than AROUND, cou can typ command1 <+> command2 ... and use the placeholder %around_target%

YEAH THE FORMAT OF THIS NEW COMMAND IS DIFFERENT IT REQUIRES TO PUT THE SETTING NAME + ':' AND THEN THE SPECIFICATION. Progressively it will be the norm, like that there is no order and you can place them where you want. And In the future I can add more without difficulties.

Fix an issue with the custom command FORMAT_ENCHANTMENTS

Click to expand...

draw of the hitscan : (spoil i'm not an artist)

View attachment 1631

For ExecutableBlocks (X.24.8.13):​

• Fixed dupe issue in 1.16.5
• Fixing an issue with the cancelGravity feature
• Same as for EI, only the teams are different.
• - /eb run-custom-trigger trigger:{activatorId} // Will execute the trigger(s) for all placed EBs that have an activator with the specified ID.
• - /eb run-custom-trigger trigger:{activatorId} block:{world,x,y,z} // Will only execute the trigger(s) for the EB placed in the specified location and if it has an activator with the specified ID.

For SCore (all plugins) (X.24.8.13):​

• New to the custom AROUND command, you can add where you want throughBlocks:false, and it won't affect players who are behind the blocks

For SCore (all plugins) (5.24.8.9):​

• We fixed an issue where for some reason, default items could not be loaded when plugins were first installed.

For SCore (All Plugins) (5.24.7.1):​

• New ability to set variable conditions for EB in blockAround

For Executable Blocks PREMIUM (4.24.5.25).

• PufferFish compatibility fixes

For SCore (all plugins) (4.24.5.25).

• MiniMessage dependency version update

For EB (all plugins) (4.24.4.30).

• Fixed /eb remove error message
• Fixes problem with ovens and paper
• Fixed /eb give in EB
• /eb give Ssomar NivaI{Usage:5,Variables:{a: "B"}

For SCore (all plugins) (4.24.4.30).

• I've improved the code of several important methods
• Fixed the detailedBlocks & blockTypeMustBe edit, now it doesn't always convert your inputs to uppercase.

For SCore (all plugins) (4.24.4.21).
Translating 0 to Latin now returns O instead of crashing the server

New "drop" setting for the TRANSFER_ITEM custom command {launcher slot} {receiver slot} [boolean drop].
drop false: will simply swap items in place
drop true: itemA will go into slotB and itemB will be dropped

Fixes placeholder parsing issue in custom IF command