Bindatcmd and group_id

[HeikoS]

Syntax

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

 

I think the usage of (gm)level is outdated and we now will use group_id instead of level.

How can I restrict the usage of an atcommand (with bindatcmd) to an special group_id?

 

For example there is a group_id 10 which should be allowed to use the atcommand, but a group_id 20 should not be allowed to use the atcommand. When using

bindatcmd "test","acmd_test::OnAtcommand",10; 

this atcommand can be used by chars with group_id 10 and 20. A char with group_id 20 should not be allowed to use the command.

[Stolao]

Hmm that's actually a valid point, why does it still use gm level?

[-SkittleNugget-]

Nice find.

[Capuche]

Interesting~ I move this topic in script discussion

 

I believe we could drop the 'atcommand level' and change it to 'group id' permission

bindatcmd "command","<NPC object name>::<event label>"{,<group id 1>,<group id 2>,...};

[ossi0110]

Interesting~ I move this topic in script discussion

 

I believe we could drop the 'atcommand level' and change it to 'group id' permission

bindatcmd "command","<NPC object name>::<event label>"{,<group id 1>,<group id 2>,...};

that would be perfect

[Capuche]

I forgot the char/at command permission, maybe like that ?

bindatcmd "command","<NPC object name>::<event label>"{,<group id 1>: [ true, false ],<group id 2>: [ true, false ],...};

[ossi0110]

I forgot the char/at command permission, maybe like that ?

bindatcmd "command","<NPC object name>::<event label>"{,<group id 1>: [ true, false ],<group id 2>: [ true, false ],...};

yeah thats perfect

[-SkittleNugget-]

Why not just, min group ID instead of having a boolean... Rather keep it simple...

<Min Group ID>