The only procs where usr is needed are Click() and DblClick(). Everywhere else, there's a better alternative.
Entered() is one of the WORST procs to be using usr in.
[edit]Also: usr is useful in Stat() in certain cases.
You're taking it to some un-unnecessary extremes there. There's a few other places too. LummoxJR's article clears it up pretty well and should leave people with a basic understanding of when to use it and when not to.
You're definitely right about usr in Entered() though, that's even one of the "What not to do" examples in the article. Reading the reference entry for Entered() also makes that pretty obvious, but I think some of the people who have been posting here don't quite understand the concept of arguments yet. | |
Granado Espada wrote:
Lummox JR wrote: And to help un-confuse them, here's the correct answer. Entered() is a totally bogus place for usr, as are all movement procs. Click() on the other hand really is better described as a pseudo-verb; it's basically always used as a verb unless you do something to muck with the client verb that calls it, or you call it directly. Likewise Stat() is really only ever called by client/Stat(). But pseudo-verbs are quite obvious, whereas cases like Entered(), Login(), etc. clearly are not the same thing. Or at least, it's clear except to the aforementioned rookie BYONDers. Lummox JR | |
You're right. I'd forgotten that usr also has a place in Stat(), in rare circumstances.
As for client procs: usr is equivalent to mob (being, you know, defined as the client's mob), and so there's no reason to use it instead of mob. Sure, usr is valid, but my rule of thumb is: because newbies are apparently inclined to slather usr all over everything, it's best to use it as little as possible in the hope that they get the hint. I even support not using usr in verbs so long as src is an alternative. The perfect example of how abusing usr can mess something up is if you have a means of controlling another player. Errors just plain start flying, then. | |
~Grand