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 ExecutableItems (X.24..10.1):
- You can now edit the rarity of your item (1.20.5+)
- You can now define your tools (1.20.5+): -
- default item mining speed
- damage per block destroyed
- add custom rules depending on the block destroyed, each rule has three parameters: materials, mining speed and a true/false parameter to set whether the rule is considered the optimal tool for the blocks listed in that rule and whether it will drop items.
For SCore (all plugins) (X.24.10.1):
Fixes an issue for users of version 1.20.4 and below
Hello, new update !
If you encounter any issue, join the discord server and report it as soon as possible.
https://discord.com/channels/701066025516531753/1047910680608653352/1287125132464095287
For ExecutableItems(X.24.9.17):
Fixes "ItemStack cannot be null/air/amount of 0!" issue for users 1.8-1.12
For SCore (all plugins) (X.24.9.17):
Fixes minor issue
Hello, new update !
If you encounter any issue, join the discord server and report it as soon as possible.
https://discord.com/channels/701066025516531753/1047910680608653352/1282077591787933808
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
For ExecutableItems(X.24.8.25):
Fix an issue with the activator EI_ENTER_IN_THE_INVENTORY
Fix an issue with /ei console-modification that didnt modify correctly the item when the item amount was superior to 1
draw of the hitscan : (spoil i'm not an artist)
FAST FIX OF THE ISSUE getPlaceholders()" is nullHello, new update !
If you encounter any issue, join the discord server and report it as soon as possible.
For Executable Items PREMIUM (6.24.5.25).
- Fixed in-game edition of the detailedslots feature
For SCore (all plugins) (4.24.5.25).
- MiniMessage dependency version update