xWarp

37k Downloads

<NAME> and other variables for warp signs.

Kosyne opened this issue ยท 4 comments

commented

Title says it all. I have a banking system, and I want multiple people to access their accounts with a single sign.

For example, the warpsign says <NAME>_Bank

If I click it, it warps me to Kosyne_Bank and if someone else clicks it, it takes them to Someone_Bank.

commented

Okay, in 2.12.0 I added this. At the moment not everything you suggested, because the missing are more complicated. As there is a bug with PermissionsEx the 2.12.0 has to wait. But 2.12.0 will come today either with or without PermissionsEx support.

Fabian

commented

Nice idea, I will look into this, maybe someone has also suggestions for other variables. As this is relative easy to implement this will come in a future version.

Fabian

commented

Thank you SO much. I've been trying a workaround with CommandSigns, but for that I have to temporarily give users permission to use /warp when I only want to give them permission to use WarpSigns.

As for other variable ideas, just brainstorming here, but:
{
for currently held item. That way only a user holding, a certain block could get access.
Example:
Sign's text is _SekritLair
And the warp is 87_SekritLair (not Netherrack_SekritLair because Netherrack is commonly called Bloodstone, netherstone, and netherrock, item names could cause confusion, but I may be wrong.)

Checks if the sign's block is recieving power. For example:
'_Test' could point to either 'On_Test' or 'Off_Test'
you could also look at the CommandSigns thread.

Replaces with the name of the permissions group the player is in.
Obviously requires permissions, but this one could be really useful.
_Area could point to
Users_Area, Admins_Area, and Guest_Area

Similar to perm is and , it gets a users prefix and suffix from permissions. May or may not be useful.

Could be a slightly less useful alternative to Perm.

When thinking up more variables,it is probably most useful to come up with ones that select certain users based on certain criteria, such as and
}

That's all I can think of right now. Again, this is just brainstorming... they may not be nearly as useful or feasible as I think they are. Ultimately, you decide what goes into the next build :D

I have one more idea that I've needed for a while now, but it may be a bit out of this projects scope, but I'll post it up anyway, and let you give your verdict on it.

commented

Woops, didnt mean to hit that button >_>
Ignore that...
whistles