HeikoS Posted May 30, 2013 Group: Members Topic Count: 3 Topics Per Day: 0.00 Content Count: 22 Reputation: 2 Joined: 01/08/12 Last Seen: October 22, 2013 Share Posted May 30, 2013 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. Quote Link to comment Share on other sites More sharing options...
Stolao Posted May 30, 2013 Group: Developer Topic Count: 48 Topics Per Day: 0.01 Content Count: 1443 Reputation: 337 Joined: 10/17/12 Last Seen: April 17 Share Posted May 30, 2013 Hmm that's actually a valid point, why does it still use gm level? Quote Link to comment Share on other sites More sharing options...
-SkittleNugget- Posted May 31, 2013 Group: Members Topic Count: 11 Topics Per Day: 0.00 Content Count: 318 Reputation: 54 Joined: 12/23/12 Last Seen: July 1, 2017 Share Posted May 31, 2013 Nice find. Quote Link to comment Share on other sites More sharing options...
Capuche Posted May 31, 2013 Group: Developer Topic Count: 10 Topics Per Day: 0.00 Content Count: 2407 Reputation: 613 Joined: 07/05/12 Last Seen: April 15 Share Posted May 31, 2013 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>,...}; Quote Link to comment Share on other sites More sharing options...
ossi0110 Posted June 1, 2013 Group: Members Topic Count: 12 Topics Per Day: 0.00 Content Count: 318 Reputation: 37 Joined: 12/30/11 Last Seen: October 3, 2017 Share Posted June 1, 2013 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 Quote Link to comment Share on other sites More sharing options...
Capuche Posted June 1, 2013 Group: Developer Topic Count: 10 Topics Per Day: 0.00 Content Count: 2407 Reputation: 613 Joined: 07/05/12 Last Seen: April 15 Share Posted June 1, 2013 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 ],...}; 1 Quote Link to comment Share on other sites More sharing options...
ossi0110 Posted June 1, 2013 Group: Members Topic Count: 12 Topics Per Day: 0.00 Content Count: 318 Reputation: 37 Joined: 12/30/11 Last Seen: October 3, 2017 Share Posted June 1, 2013 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 Quote Link to comment Share on other sites More sharing options...
-SkittleNugget- Posted June 1, 2013 Group: Members Topic Count: 11 Topics Per Day: 0.00 Content Count: 318 Reputation: 54 Joined: 12/23/12 Last Seen: July 1, 2017 Share Posted June 1, 2013 Why not just, min group ID instead of having a boolean... Rather keep it simple... <Min Group ID> Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.