It appears that name( ) can be giving inconsistent results for mortal-level enactors.
If the objid exists, everything is okay.
If the objid doesn't exist but the dbref part does, name( <gooddbref>:<anything or null> ) returns <null> and the enactor gets "I don't see that here."
If the objid doesn't exist *and( the dbref part doesn't, name( <baddbref>:<anything or null> ) returns `#-1 TOO FAR AWAY TO SEE'. The enactor does not get any server-level response like they do with the previous situation.
Both are error conditions, they're just different error conditions and that seems odd. So I'm bugging this.
(Tested with both the new objeval() and from a mortal-level object to see if they react the same. They do!)
It appears that name( ) can be giving inconsistent results for mortal-level enactors.
If the objid exists, everything is okay.
If the objid doesn't exist but the dbref part does,
name( <gooddbref>:<anything or null> )
returns<null>
and the enactor gets "I don't see that here."If the objid doesn't exist *and( the dbref part doesn't,
name( <baddbref>:<anything or null> )
returns `#-1 TOO FAR AWAY TO SEE'. The enactor does not get any server-level response like they do with the previous situation.Both are error conditions, they're just different error conditions and that seems odd. So I'm bugging this.
(Tested with both the new objeval() and from a mortal-level object to see if they react the same. They do!)