removing # on players

[geoffreypogi]

Hi guys,

 

I'm not sure if im on the right page. If not, kindly move this post to the right one.

 

Here's my question:

My players can use # commands. such as #storage #go. I want to remove this and only enable it on my GM's. 
Here's my player's group.conf

{
	id: 0 /* group 0 is the default group for every new account */
	name: "Player"
	level: 0
	inherit: ( /*empty list*/ )
	commands: {
		commands: true
		charcommands: true
		help: true
		rates: true
		uptime: true
		showdelay: true
		exp: true
		mobinfo: true
		iteminfo: true
		whodrops: true
		time: true
		whereis: true
		request: true
		hominfo: true
		go: true
		breakguild: true
		autoloot: true
		alootid: true
		autoloottype: true
		duel: true
		accept: true
		reject: true
		storage: true
		gstorage: true
		changegm: true
		guildstorage: true
		leave: true
		autotrade: true
		feelreset: true
		load: true
		guild: true
		noks: true
	}
	permissions: {
		/* without this basic permissions regular players could not 
		trade or party */
		can_trade: true
		can_party: true
		command_enable: true
	}
},

 

[Jey]

> I see. How can I remove "storage" on @charcommands? it seems like it is a script bound command.

> btw, I tried using [ true,false ] and it does not work before... 

Can you be a bit more precise?

If you want to disable the use of scriptbound charcommands just set the charcommand level to something higher than zero:

*bindatcmd "<command>","<NPC object name>::<event label>"{,<atcommand level>,<charcommand level>};

 

Edited April 16, 2017 by Jey

[Jey]

Just remove this line:

		charcommands: true

 

[geoffreypogi]

53 minutes ago, Jey said:

Just remove this line:

		charcommands: true

 

still the same...

[Jey]

Are there any other changes that may affect your atcommand settings?

Normally you need to explicitly allow charcommands like:

item: [true, true]

The second true allows the char command. Unless the group has the permission "all_commands".

Edit:

My first post is just wrong, sorry for that. See:

@charcommands

Displays a list of # commands available to the player.

Edit2:

Recheck which commands are concerned. Maybe you are mixing these commands with script bound commands?

Edited April 11, 2017 by Jey

[geoffreypogi]

10 hours ago, Jey said:

Are there any other changes that may affect your atcommand settings?

Normally you need to explicitly allow charcommands like:

item: [true, true]

The second true allows the char command. Unless the group has the permission "all_commands".

Edit:

My first post is just wrong, sorry for that. See:

@charcommands

Displays a list of # commands available to the player.

Edit2:

Recheck which commands are concerned. Maybe you are mixing these commands with script bound commands?

I see. How can I remove "storage" on @charcommands? it seems like it is a script bound command.

 

[geoffreypogi]

btw, I tried using [ true,false ] and it does not work before... 

[geoffreypogi]

where can I find this?

 

*bindatcmd "<command>","<NPC object name>::<event label>"{,<atcommand level>,<charcommand level>};

im using Rathena...

[Cyro]

bindatcmd is used to create custom commands using npc scripts, if you are unable to turn off a command in groups, 
may be you using a npc script,
which is with bindatcmd function so find the script and remove that from ur npc scripts list. 

then your problem might be solved 

Edited April 16, 2017 by Cyro

[geoffreypogi]

On 4/16/2017 at 2:25 PM, Cyro said:

bindatcmd is used to create custom commands using npc scripts, if you are unable to turn off a command in groups, 
may be you using a npc script,
which is with bindatcmd function so find the script and remove that from ur npc scripts list. 

then your problem might be solved 

Hi! Thanks for the reply. Can you send me a script like this? I just want to remove the #storage from players. It seems that some of them are using this to stall other players during pvp and woe.