@Ne0nx3r0

Oh okay. I see what you mean now. I wasn't thinking of it as in the perspective that it could have an error and fail to remove the said permission.

I understand now, I won't bother you with this anymore. But if you ever do add it - I would be 100% thrilled

Any reason you ignored my question Ne0nx3r0?

Would have been courteous to have acknowledged it.

I got a MASSIVE amount of errors when I tried to use an aliased command. As far as I can tell everything is set up properly, as I have other aliased commands that are working fine.

Anything you can suggest as to why this is happening?

Here is how it appears in the config file:

gamemode:
0: "reply Usage: /gamemode <player> <#> or /gamemode <#>"
1: /gamemode !1
2: /gamemode !1p !2

And here is the error:

http://justpaste.it/byp7

@Ne0nx3r0

Couldn't you just add it and have it say something like?

requirePermission: true/false

Like you did the the caseSensitive

Looks like a great plugin :D

Can you tell me if it can do the following please? I have two plotme worlds, one of which is a shop world. If a player wishes to tp to a specific shop, they must type this as an example:

/plot tp -1;2 shopworld

Would it be possible to make this:

/shop -1;2

I can see this being a problem because "shopworld" must be specified at the end of the original command, and of course the co-ords will change depending on which shop someone wishes to tp to.

Any help is very much appreciated, thanks! :D

@Ne0nx3r0

It's okay, I think I'll just go with the alternative way for type 2 by assigning the needed permission and then having it be removed after said command has been executed.

I don't see how this could be abused if you just let people know what the two types are and how they are used.

All aliases by default (your examples page) could be the way they are now. So it wouldn't be possible to add a way so the user doesn't need the actual command permission, but only the Betteralias permission?

@Ne0nx3r0

This would only work on commands that could only be issued from the Console correct?

@xDeeKay

@IITheLegendII

I dont think essentials mixes too well with the "*" because when I tried to do this:

m danny: "*": /m DanielBlakey !*

it wouldn't work but with this:

m danny: 1: /m DanielBlakey !1 2: /m DanielBlakey !1 !2 3: /m DanielBlakey !1 !2 !3 4: /m DanielBlakey !1 !2 !3 !4 (up to 25) it seems to work fine with the exception of adding Error: Player not found which is why I like the idea of disabling original commands

My Idea

Type 1 Alias

Player needs the actual permissions(from whatever plugin the command requires) as well as the BetterAlias permission(if there is one set) to run the commands that the Alias is attempting to execute.

Type 2 Alias

Player only needs the BetterAlias permission(if there is one set) to run the commands that the Alias is attempting to execute.

What this would allow

This would allow you to create Aliases that would execute normal commands through the Alias that you designated while making it so the regular command would not work.

Example of Type 1

This example would allow anyone who had the betteralias.ban AND essentials.tempban permission to use this Alias. If the person didn't have the essentials.tempban permission, they would receive the error below.

Example of Type 2

This example would allow anyone who had the betteralias.ban permission to use this alias without having the essentials.tempban. By having it this way, the normal tempban command wouldn't work because the user doesn't have access to essentials.tempban So the only way they could ban someone would be by using this Alias which bypasses the need for the permission.

Alternative way to do Type 2 with your current settings

So this would allow me to accomplish Type 2 with nothing on your part. It adds the permission required to execute the commands in the Alias and then after executing them, it removes the permission. I just worry that this would be too impactful and this isn't the only command I wish to do this with.

Alright, so...

Is this possible? It it already possible and I'm just an idiot who can't figure it out like before with the multiple arguments idea that you helped me with. If this isn't something you can do, just let me know so I can get right to work doing the alternate method for all of them.

Thanks for reading.

First - Sorry For My Bad English I'm Turkish

I like this plugin but i have an idea for this Do you can disable origin command but we should control that Example:

"DisableOrigin: true" in the config.yml whatever

and someone use the old command then

send a customizable message ? we should change that message in the config ?

if you do that i'm sure plugin be the best

Don't worry, found a fix.

Permission: > permission:

Didn't know it was case sensitive.