Click Macro Disable System

ID:195128
 
Nov 21 2006, 7:41 am
 
//Title: Click Macro Disable System
//Credit to: Crispy
//Contributed by: Jtgibson

/*
Click() can normally be macroed, but you can prevent that by making another
verb named .click. --Crispy
*/

mob/verb/ClickSubstitute()
    set hidden = 1
    set name = ".click"
    src << ".click has been disabled."


/*
A really neat trick.  It still allows normal click events to go through, but
prevents people from using the well-known trick of defining a macro for the
".click" command.

Perfect if your game is strictly graphical and uses clicks for anything that
is game critical.  I'd personally get rid of the message, however, to simply
trim out the additional bandwidth use.  They'd catch on soon enough.
--Jtgibson
*/
Feb 28 2017, 3:51 am
Someone posted on this today, this example will fail in any instance where .click or .dblclick is used with more than one argument, as the default parser will kick back in instead of an invalid command error being tossed.

I supplied the following to MLAAS' source back when Skysaw still ran things and it has worked perfectly since.
mob
    verb
        DisClick(argu = null as anything, sec = "" as text, number1 = 0 as num  , number2 = 0 as num)
            set name = ".click"
            set category = null
            return

        DisDblClick(argu = null as anything, sec = "" as text, number1 = 0 as num  , number2 = 0 as num)
            set name = ".dblclick"
            set category = null
            return