Overlordz
10-18-2012, 04:24 AM
I'm sure I'm not the first but... I've noticed that item names are often shortened when they're in your hands, i.e.
>;exec echo rhand.inspect
--- Lich: exec2 active.
[exec2: #<GameObj:0x13e9f810 @after_name=nil, @before_name=nil, @noun="katar", @id="61476713", @name="steel katar">]
--- Lich: exec2 has exited.
>put kat in longc
You put a damascened steel katar in your serge longcoat.
>;exec echo inv("longcoat").contents[0].inspect
--- Lich: exec2 active.
[exec2: #<GameObj:0xf1c59d8 @after_name=nil, @before_name="a", @noun="katar", @name="damascened steel katar", @id="61476713">]
--- Lich: exec2 has exited.
Notice how @name changes from "steel katar" to "damascened steel katar".
As far as I know, items anywhere else (ground, containers, lockers, etc) get the "full" name -- please correct me if I'm wrong on this.
This is correct in a way since what GS sends through its stream is shortened. The shortened name is useful for displaying the item in the wizard/SF controls with limited space. But, IMO, it's not very useful and somewhat counter-intuitive to use the shortened name for scripting purposes.
The full name is useful for tracking items... I've noticed a couple scripts on the repo (itemnotes, enchantnotes) do this "wrong" and simply use the GameObj.name when the item is in your hand to track it. What they SHOULD be doing is sending a GLANCE, getting the name and using that. For example I might have some "polished full leathers" that I'm enchanting and some "full leathers" that I'm not... scripts like enchantnotes and itemnotes won't be able to tell the difference between those two items.
I'm wondering if it would even make sense for Lich itself to lazily do that "glancing" routine when needed? Lich could probably completely hide this issue from gripers like me if it wanted. With how chatty GS is as it is... it probably wouldn't be too burdensome on the game.
This is more food for thought than anything... I can fix the scripts on my end when I run into problems. Just figured that other people will run into the same problem and might wonder why things are acting that way.
>;exec echo rhand.inspect
--- Lich: exec2 active.
[exec2: #<GameObj:0x13e9f810 @after_name=nil, @before_name=nil, @noun="katar", @id="61476713", @name="steel katar">]
--- Lich: exec2 has exited.
>put kat in longc
You put a damascened steel katar in your serge longcoat.
>;exec echo inv("longcoat").contents[0].inspect
--- Lich: exec2 active.
[exec2: #<GameObj:0xf1c59d8 @after_name=nil, @before_name="a", @noun="katar", @name="damascened steel katar", @id="61476713">]
--- Lich: exec2 has exited.
Notice how @name changes from "steel katar" to "damascened steel katar".
As far as I know, items anywhere else (ground, containers, lockers, etc) get the "full" name -- please correct me if I'm wrong on this.
This is correct in a way since what GS sends through its stream is shortened. The shortened name is useful for displaying the item in the wizard/SF controls with limited space. But, IMO, it's not very useful and somewhat counter-intuitive to use the shortened name for scripting purposes.
The full name is useful for tracking items... I've noticed a couple scripts on the repo (itemnotes, enchantnotes) do this "wrong" and simply use the GameObj.name when the item is in your hand to track it. What they SHOULD be doing is sending a GLANCE, getting the name and using that. For example I might have some "polished full leathers" that I'm enchanting and some "full leathers" that I'm not... scripts like enchantnotes and itemnotes won't be able to tell the difference between those two items.
I'm wondering if it would even make sense for Lich itself to lazily do that "glancing" routine when needed? Lich could probably completely hide this issue from gripers like me if it wanted. With how chatty GS is as it is... it probably wouldn't be too burdensome on the game.
This is more food for thought than anything... I can fix the scripts on my end when I run into problems. Just figured that other people will run into the same problem and might wonder why things are acting that way.