Vanishing lash in Developer Help
mob proc CheckAwesome(mob/M) // M is a defined argument that should be a mob if(M.Awesome = 1) // Do the conditionals M << "You are awesome" else M << "You suck"
mob proc ProcDefinition(Arg1,Arg2)
if(something) // same as if(something == 1) / if(something == TRUE) / etc.
Well Robertbanks2 has laid down the law lolz. I always assumed usr is okay as long as there will always be a user. I guess I'll just ask a quick question here.
Is there a general practice rule of "too many args" in a proc definition? I know that a few built in procs can have 6+ args. What does one do to handle such a situation?
add_card_multi() //adds multiple cards, note the lack of arguments? for(var/list/cardlist in args) args += cardlist for(var/card/card in args) // args list takes care of this, each argument is another list entry //mostly so people can call this proc like this: add_card_multi(a, b, c, d) and expect them all to get added cards += card