evilpuncker 503 Posted May 15, 2015 The idea is simple, add a "delay" parameter to bindatcmd in milliseconds, so we can set them to prevent abuse of some commands, and maybe a flag that will define if logout will reset the delay or not. (maybe even add it to atcommands itself ) PS: yeah I know it is possible to achieve this with scripting, but so is the gmlvl check and what else. Quote Share this post Link to post Share on other sites
- Mariel 2 Posted May 16, 2015 I think this will be useful on warping commands. Quote Share this post Link to post Share on other sites
Dastgir 1246 Posted May 16, 2015 I think this will be useful on warping commands. Not only warping, but with many other things too. Quote Share this post Link to post Share on other sites
Emistry 145 Posted May 16, 2015 if you dont mind , add the "log" option as well .. I think this isnt included right ? Quote Share this post Link to post Share on other sites
evilpuncker 503 Posted May 16, 2015 if you dont mind , add the "log" option as well .. I think this isnt included right ? it is *bindatcmd "command","<NPC object name>::<event label>"{,<group level>,<group level char>,<log>}; Quote Share this post Link to post Share on other sites
Emistry 145 Posted May 16, 2015 if you dont mind , add the "log" option as well .. I think this isnt included right ? it is *bindatcmd "command","<NPC object name>::<event label>"{,<group level>,<group level char>,<log>}; LOL... seem like I am still using a super old version of script_command.txt haha my bad. Quote Share this post Link to post Share on other sites
evilpuncker 503 Posted March 1, 2016 I think this will be useful on warping commands. Not only warping, but with many other things too. indeed bump! Quote Share this post Link to post Share on other sites
sbk_ 30 Posted March 4, 2016 sim... yes xD 1 evilpuncker reacted to this Quote Share this post Link to post Share on other sites