Weird misnaming effect in connection with decaying items.

Weird misnaming effect in connection with decaying items. - Printable Version

+- SphereCommunity (https://forum.spherecommunity.net)
+-- Forum: Sphere 0.56d (/Forum-Sphere-0-56d)
+--- Forum: Script Help (/Forum-Script-Help)
+--- Thread: Weird misnaming effect in connection with decaying items. (/Thread-Weird-misnaming-effect-in-connection-with-decaying-items)

Weird misnaming effect in connection with decaying items. - Gadianton - 09-06-2012 10:09 PM

I really don't know where to put it, but since I can't rule out some glitch in my scripts I put it here. I am currently developing a new set of scripts for our project. Since I am alone on the server and there are only a handful of items I have witnessed a really awkward behaviour.

If I have an Item laying around called "Bogus" and this item decays as soon as I create some new item (does not matter which) - say a piece of marble - the tooltip of this new item reads "Bogus". Most interestingly if you use a function like .xshow name on the item it will give you the correct name: "Marble"

I have reproduced this phenomenon very securely now, it even went so far that when I logged out yesterday there was still one of my testitems lying around. It decayed overnight and when I logged in today my Char suddenly was named like the item. Using .set name= fixed that but I still find it to be odd.

At first I blamed one of my standard typedef scripts, that manipulates the Tooltips via the @CLIENTTOOLTIP trigger. But even commenting it out or using items that do not use this type has not fixed the issue.

Anyone has seen this before? My server build is a nightly from April 30th 2012.

advice appreciated

Gadianton

Okay it seems to be some sort of client issue 7.0.7.1 client I use. When I relogg after such an event the item has the correct name again...

But if anybody else has seen this would be great to get some feedback.

RE: Weird misnaming effect in connection with decaying items. - Skul - 09-12-2012 04:04 PM

This is a client tooltip issue. It only happens because tooltips are updated after a certain amount of seconds at a certain amount of times. You can alter these values in sphere.ini but the real way of updating a tooltip is to use

Code:

[obj.]resendtooltip

You can use this in a script such as

Code:

on=@itemdropon_ground //first placed in world or dropped whenever after creation

act.resendtooltip

You should use this feature in other triggers such as @itemdropon_pack, @itemdropon_item to update the amount of objects inside a container, example

Code:

on=@itemdropon_pack

argo.resendtooltip //argo is the pack, act is the item

act.resendtooltip //act is the item, argo is the pack

Pretty simple I guess, wherever you notice this error just add in a trigger and add resendtooltip to the object in question Smile