NodeBB

It's not paranoia if they ARE out to get you. 8)

Maybe for the most part. Perhaps have it generally accessible, for things like quest clues and other info, but leave the predominant activities remort-only.

Or base it upon the condition of the object. A worn/loose sextant isn't likely to work as well as a prestine sextant. Through age (if degradation is added) and repeated use, it will eventually become damaged.

Just testing something.

After looking at it through the debugger, this stems from the fact that the titan guardian hammer has "hidden" flag on it for some reason. This is a utility flag which gets set on objects which are hidden with the "hide" command and are thus completely hidden from view until they are found with "search" which flips the flag bit. It shouldn't EVER be on inventory items for any reason. I hardcoded it so that "hidden" can't be set on objects for any reason - once again this is a utility flag, not really something that should be set. I also added a bit of code to flip the flag on any inventory items which might have it on, on player log-in. Idea for self: in the future, implement a utility bitfield for objects to put flags which imms aren't supposed to set.

This might be a consequence of Whisp's replacing my painstaikingly-fixed get and put functions with his older, crappier functions to make his carts work. Luckily, my functions are commented out; leaving this post as a reminder to myself to re-enable them and see if it fixes this error. Edit: Actually, my function doesn't account for this either, despite the things it fixes. I'll look into resolving this prob ASAP since I don't like blank lines any more than you do :twisted:

Hmm, i wasn't aware the printf functions could be used with this syntax. You live, you learn 8) I was trying to do a ghetto workaround with a second buffer string, and kept running into overflows. I'll give this a go when I get back home.