ScriptBlock
Welcome on the ScriptBlock v0.8.0 project page !
ScriptBlock is a CraftBukkit plugin inspired by the great Fluff's plugin Annotate and CommandSign !
It allow you to bind text, commands, or MANY commands to any block (levers, buttons, doors, Signs, etc...), triggered by clicking or walking on it !
Here is a Tutorial video made by Kunoichi Kitteh ! Thanks to here !
LiekMudkipzz also made a cool video of ScriptBlock ! It's a bit outdated, some commands have changed ! but Thanks to him too !
Here is the link !
Regarding Donators
Those who help me maintain motivation for Keeping this project updated !
I really Thanks them !
S4h4rk
StefanPelskamp
Slipswhitley
About 0.8.0...
Lot of change in the codes, in the commands, to make possible and easily, for other devs, the add of Options, and the use of ScriptBlock Options for other Minecraft Event than walk , and interact trigger ! ( ask for sources, and for help if you want to do one ! )
Also a New BIG and FULLY customizable permission system. See changes log for more informations !
Features
- Adding any text, command, or set of commands to a block (levers, buttons, doors, signs, etc...) with Various Options !
- Read any Text and execute any commands or command Script. that has been bound to a block with right or left-click !
- ScriptBlock use the Vault API ! You need to download it even if you don't want to use the Economy and Permissions features !
Download Vault - Support all permissions plugins supported by Vault or if you don't like permissions, it can be Op based only !
- Most of Economy plugins support (if Vault support it, ScriptBlock support it too ! ).
- MultiWorld Support.
- Player can use a bound command, even if he usually doesn't have the permission to use it, with the help of the @bypass prefix.
- You can edit scripts with a simple Text editor like notepad
++
. - Look at Changes Logs for more Infos !
Commands
Trigger:
- /sbinteract
is used for "on block interaction triggered" scripts ! - /sbwalk
is used for "on block walk triggered" scripts !
After you've choosen the kind of trigger you want , you need to choose the type of commands you want to send to ScriptBlock !
Types:
- create
Use this command to create a script and follow displayed informations ! - add
Use this command to add a command, or a script to an already created one, or to an already bound one. - remove
Use this command to remove a script from a block. - view
Use this command to view the script you've bound to a block ! - reload
This command let you reload the save file, to refresh the scripts bound on blocks !
Usefull when editing script in the BlocksData.yml save file while server is still running !
exemples:"/sbinteract create" , "/sbwalk create", "/sbinteract remove", "/sbwalk remove", etc...
Options
There is a lot of cool options you can use for your scripts ! You MUST at least use one option with your script to make it work !
Options List
Permissions
ScriptBlock Permissions system have a lot of possible customisation. You can use simple permissions nodes if you are admin and want full power, without taking the time to set up all the permissions for your players. Or you can take the time, and fully customize the way you want your players to use ScriptBlock.
Upcoming Features
- Per Player Cooldown.
Economy plugins support- Copy/paste Scripts. (low priority)
Add a Config file to edit Script that has been bound.More Permission NodesA command that let you know what commands you've bound to a block.- WorldGuard / Residence support. (low priority)
- Custom messages
- Chat color
@kbassil
Good luck for your server ! I hope you won't have more issue with my plugin !
Confirmed. It is WORKING perfectly now. I did not have allowOps : true set. it was on false. Great plugin.
You will be seeing it highly used in "AggieCraft", a new RPG Class server coming up soon. I'm sure you'll hear some feedback on it here and there. This plugin will make the whole thing automated
@kbassil
I didn't set a scriptblock.* permission node yet ! so... if you use it, it won't work ! please open a ticket, and show me your permissions.yml situated in pex folder ! I will try to solve it !
Edit: Have you tried to set "allowOps : true" in the PermissionsEx/config.yml ?
@user_158075
Thanks for feedback ! I will put this version on official download !
@NotYetRated
Nice ! i'm happy to see it's working for you !
To further update the below issue - this is fixed in the dev build you linked in other comments.
@Shereis
It is working for me!
@bypass and all. Thank you!
Minor issue: When using Essentials, a user must /nick off before the <player> variable will work in commands, even if the user has no nick set.
When commandsigns started losing all signs on reboot, I had to give up a lot of my server functionality....until I found this.
Thank you so very much for developing it - this is a wonderful, flexible, and powerful plugin that accomplishes everything I need from it.
@kbassil
Now I think it's a problem with "@bypass". I gave someone the permission scriptblock.* and they "dont have enough permissions" either
@Shereis
It works!... sorta...
<snip - wrong assumption> Here's what's wrong. Only an ADMIN with all priv's enabled can use the sign, even when it has "@bypass" written on it. Mods, etc with slightly lesser priv's then me (an Admin) are not able to promote or demote themselves.
help plz
If I had to guess- there is another permission besides the two listed above. Otherwise, why can only an Admin use the @bypass sign successfully, and anyone else is told "you do not have enough permissions"?
@NotYetRated
PermissionEx issues fixed ! ! Please Send a Feedback about the latest version !
@Shereis
Let me know if I can help. I can provide u with whatever u need.
@NotYetRated
hmmm ...I will investigate this more ...
@Shereis
I am having the same issues. Using PEX 1.15, CB 1321, your latest version.
Trying to issue ANY /sbcreate command, I get a "bukkit sad" permissions error. I am the op of my server, and it is set so in the ops.txt..... Allow ops is enabled in PEX.
@kbassil
Go in your PEX config.yml and set : allowOps : true
then, add your name if it isn't already done to Ops.txt Be carefull ! Don't set any untrusted user to Ops in Ops.txt with that !
Actually, i'm coding a Plugin that will have features to set and buy (for money or for free) PEX ranks with interesting features ! and a lot more "security" than adding PEX command to a ScriptBlock ! feel free to come again, I should release it soon.
@Shereis
I'm using PEX, and here's an example:
/sbcreate @bypass /pex user <player> group set Engineer5
where Engineer5 is a group with unique permissions.
@kbassil
What permission plugin are you using ? What are the commands you're trying to execute ? Write me an example of the Script you made !
@kbassil
I used your new plugin, but whenever I try to use the commands, I get "Bukkit is sad. Bukkit will leak tears, etc..."
I am running the latest Bukkit.
@Shereis
I truly appreciate the quick feedback. Your plugin is ESSENTIAL to my server plans, so fingers crossed it works. I'll let u know.
@kbassil
Here is a Dev version that should fix your first problem, and maybe the second one...
http:dl.dropbox.com/u/41205606/ScriptBlock_Dev.jar
Don't forget to remove your previous ScriptBlock.jar ... or it will corrupt your ScriptBlock Save !
if it doesn't fix your issue, I need you to send me your plugin folder in a zip, or just the ones who are related to Chat ! If it fix it, please post a comment, so I will update the official version...
I REALLY REALLY need your help on 1 issues:
1) I use a server with prefixes on names, and whenever I use the <player> command it will not work. Console shows the entire prefix plus and color codes as the player's name. So, if the player's name was orange, the <player> would output "&8PlayerName" totally ruining the script.
2) When i remove all titles/prefixes, and still try to use the <player> command in a sign, the effing output shows an "f" on the end of every name, so it doesn't work. So for example, "kbassil" becomes "kbassilf" and the script doesn't work. Help, man.