Subject: @args not working properly.

From: [email-masked] (Paul Jimenez)
Date: Mon, 20 Sep 1993 11:48:40 -0700

It's come to my attention that @args is not working properly on the MOO I
help run..

a common situation:
someone creates a new verb and forgets to specify tnt...
they then find that when they try and call it from another verb, they get 
'no verb found'-type error messages. No problem we'll just use @args to fix
this, right?
So @args object:verb tnt
@show object:verb show that the params are indeed this none this
but we STILL get the 'verb not found'-type error messages.

so to me it sounds like something somewhere isnt getting updated where it should
and it also sounds like that something is somewhere in the server. anyone else
have these problems or know how to fix them? anyone? anyone? Beuler?...

--Zachary
  Zachary@lambdamoo, @metaverse, @jayshousemoo, @...

---

From: Roger Crew <[email-masked]>
Date: Mon, 20 Sep 1993 12:03:11 -0700

@chmod object:verb +x  ?

---

From: [email-masked] (Erik Ostrom)
Date: Mon, 20 Sep 1993 07:05:34 -0700

> 'no verb found'-type error messages. No problem we'll just use @args to fix

The argspec for a verb has nothing to do with whether or not a verb
can be called.

> but we STILL get the 'verb not found'-type error messages.

Because the verb is !x.  The @verb command (_not_ set_verb_info())
assumes that if a verb is tnt, it should be +x (unless otherwise
specified), and if not, it should be !x.  The two are not directly
related, though, so if you use the @args command, it assumes you just
want to change the args, and if you use the @chmod command, it assumes
you just want to change the permissions flags.

@chmod <object>:<verb> +x

--Erik/JF