Jump to content
  • 0

how to disable #commands


antigm2

Question


  • Group:  Members
  • Topic Count:  7
  • Topics Per Day:  0.00
  • Content Count:  18
  • Reputation:   0
  • Joined:  05/01/12
  • Last Seen:  

how do we disable #commands on other gm's to avoid biases?

for example this is the script of eAthena on how they remove or restrict certain gm level to use #charcommands

 

command @,#
 
warp 10,99
storage 10,99

 

 
I saw this on conf/atcommand_athen.conf
 
 atcommand_symbol : "@"
 
charcommand_symbol: "#"

 

removing the whole line of "charcommand_symbol: "#"" will disable the whole #char command? or how do we just restrict it to other gms?

Link to comment
Share on other sites

9 answers to this question

Recommended Posts


  • Group:  Members
  • Topic Count:  130
  • Topics Per Day:  0.03
  • Content Count:  528
  • Reputation:   18
  • Joined:  09/11/12
  • Last Seen:  

if i understand you: You wanna restrict commands for other GM?

 

then go to trunk/conf/groups.conf.

 

This file defines "player groups" and their privileges.

Each group has its id and name, lists of available commands and other 
permissions, and a list of other groups it inherits from.

Link to comment
Share on other sites


  • Group:  Members
  • Topic Count:  7
  • Topics Per Day:  0.00
  • Content Count:  18
  • Reputation:   0
  • Joined:  05/01/12
  • Last Seen:  

i understand the groups. what i mean is that

i am allowing my gm to use @blevel

but not the #blevel command.

 

because he might use it to level his characters or worse other player's characters.

Edited by antigm2
Link to comment
Share on other sites


  • Group:  Members
  • Topic Count:  130
  • Topics Per Day:  0.03
  • Content Count:  528
  • Reputation:   18
  • Joined:  09/11/12
  • Last Seen:  

Or make a script that broadcast if a GM use #blevel so i cant use it woitout the server knows it ;)

Link to comment
Share on other sites


  • Group:  Members
  • Topic Count:  43
  • Topics Per Day:  0.01
  • Content Count:  400
  • Reputation:   5
  • Joined:  12/05/11
  • Last Seen:  

In trunk/conf/group.conf

 

	<commandname> : [ <bool>, <bool> ]
First boolean value is for atcommand, second one for charcommand. If set to 
true, group can use command. If only atcommand value is provided, false is 
assumed for charcommand. If a command name is not included, false is assumed for 
both atcommand and charcommand.
For a full list of available commands, see: doc/atcommands.txt.
Command names must not be aliases.

So,

 

It should be like this :

 

{
	id: 20
	name: "Event"
	inherit: ( "Support" )
	level: 20
	commands: {
		blvl: [true, false]
	}
	log_commands: true
	permissions: {
		
	}
},

Please correct me if I'm wrong.

Link to comment
Share on other sites


  • Group:  Members
  • Topic Count:  7
  • Topics Per Day:  0.00
  • Content Count:  18
  • Reputation:   0
  • Joined:  05/01/12
  • Last Seen:  

@ude i know that we could make it as false but what i mean is that the command is still available to use but for the #charcommand it's disabled.

for example for the eathena commands

blvl 40,99

 

in this configuration gm's that are level 40 can use the @blvl command but not #blvl commands. 

to be able to use the #blvl command the gm's level should be 99.
 

by gm's level meaning its group id.

Edited by antigm2
Link to comment
Share on other sites


  • Group:  Members
  • Topic Count:  82
  • Topics Per Day:  0.02
  • Content Count:  223
  • Reputation:   4
  • Joined:  02/23/12
  • Last Seen:  

as stated above

 

blvl: [true, false]

Link to comment
Share on other sites


  • Group:  Members
  • Topic Count:  9
  • Topics Per Day:  0.00
  • Content Count:  105
  • Reputation:   67
  • Joined:  04/05/13
  • Last Seen:  

[true,false] means that group can use the command on themselves but not as a # command targetted at others

Link to comment
Share on other sites


  • Group:  Members
  • Topic Count:  9
  • Topics Per Day:  0.00
  • Content Count:  69
  • Reputation:   4
  • Joined:  07/02/12
  • Last Seen:  

yep, those settings are the same for normal players by default. that's why they can't make other players use #go or any other command. Just follow the format they posted.

Link to comment
Share on other sites


  • Group:  Members
  • Topic Count:  7
  • Topics Per Day:  0.00
  • Content Count:  18
  • Reputation:   0
  • Joined:  05/01/12
  • Last Seen:  

ohhh shizz i think i get it AHAHHA i thought the true, false are choices :)))) sorry for the argue hehe ill try now :)

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Answer this question...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...