Bukkit

What steps will reproduce the problem?
1. Create a script with /sbcreate @bypass /warp cloud
2. Add it to a block
3. Clicking that block

What is the expected output? What do you see instead?
It should tp the user to the place I set the warp to, but instead it says they don't have permission.

What version of the product are you using?
ScriptBlock: 0.7.2
PEX: 1.19.1
VAULT: 1.2.15

Do you have an error log of what happened?
No.

Please provide any additional information below.
The plugin does give OP's permission to warp automatically.

My PEX version is the same and I don't have any problem. So There is probably something that you're doing wrong !

Does others commands works with the @bypass ?
Does it occurs only with the /warp command ?
Does it works with the '@bypassPERM:warp.permission' ( replace warp.permission by the good permission node ) ?
Does it works with the '@bypassGROUP:warpgroupname' ?

Silly questions I have to ask : Does the player that should use the Scripted block have the "scriptblock.use" permission ?

You should post the part concerning the script that have an issue in the blocksdata.yml . also with the '@bypassPERM:' test and the others option that do not work.

I also need the part concerning scriptblock int your permission.yml

@Shereis: Go

Hmm. After re-testing the @bypassPERM it worked, so I probably had a typo in the permission or something. @bypassGROUP works fine too. @bypass still doesn't work, although that's not really a problem because I can just use @bypassPERM.

@bypass doesn't work with whatever command I try.

    -405,86,-21:
    - '@bypass /warp cloud'

All my groups (including default have the 'use' permission. I know that because scripts for like /kill, without bypass do work.

BTW: Thanks for this amazing plugin, it really helps making my server more user friendly by not having to type commands :D

@jorisk322: Go

Well, I don't really know why the @bypass do not work with you as the script have no error in the syntax... Maybe all commands you've attempted are from the same plugin, and maybe this plugin does not support OP ! check the config of this plugin, to see if you can activate it...

Otherwise you are stuck with the @bypassPERM and @bypassGROUP options ! ( they are more heavier in resources but they are also more cautious ! )

@Shereis: Go

The commands where from different plugins, so I don't know what the problem could be either. If I ever find out what was wrong, I will probably post it here. Might help some people.