Re: @create problem

• Date: Sun, 31 Mar 1996 16:46:48 -0500
• From:
  phantom@baymoo.sfsu.edu (Richard Connamacher)
• Content-Type: text/plain; charset="us-ascii"

>Welp, the best solution is to find out what went wrong... I do not use
>the new core so i do not know what object #90 is, or what the moveto
>acceptable says... I can _guess_ what the problem is though -- when
>objects are created they are in #-1, the @create verb tries to move them
>to the creator, and #90:moveto tries either to check a property or
>execute a verb on the objects former location -- which is an invalid
>object (#-1).

Actually, no.  #90 is Frand's Player Class, and the problem has to do with
the new callers().  I'm not sure what the change should be, however, but it
has to do with one part of callers() returning a non-object, when the old
callers() returned an object ref there, so when it tries to check something
on that object, it gets E_INVIND.

Phantom

-----BEGIN PGP PUBLIC KEY BLOCK-----
Version: 2.6.2

mQCPAzEtexUAAAEEALPfu202DEwxLQ96BwKL5liDPzdCVox/iSbc201h5oTzLGmT
v1PU+TmeS/lEtTvVe5WVZ3iDjjKDcoWwc1MRmbCMMVosywXEiXoLqWBTj+hlcKXA
//TpyK4RRBZodr6eFesy2wSphpXTtJnIduKMDP0XuVgcrOILMUa1Zcdw+pa1ABEB
AAG0LVJpY2hhcmQgQ29ubmFtYWNoZXIgPHBoYW50b21AYmF5bW9vLnNmc3UuZWR1
Pg==
=iME4
-----END PGP PUBLIC KEY BLOCK-----

• Prev: Re: @create problem
• Next: Re: @create problem
• Index: MOO-cows
• Thread: MOO-cows