Almost every .openpack command or variants thereof I have seen uses SendOpenSpecialContainer to display the contents of a character's backpack. The issue with using this function call to show a
player's backpack is that when you do this the backpack on the player's paper doll goes invisible and will not reappear in the paper doll until the player logs out and back in again. Closing and reopening the paper doll has no effect. As any one with any GM experience knows there are occasions when it is necessary to perform a clandestine inspection of a player's pack. If your .openpack or .info command uses SendOpenSpecialContainer I suggest switching it to SendViewContainer. This has the disadvantage of requiring you to be close to the character if you need to manipulate items in their pack but it will not cause their backpack to disappear from their paper doll.
Back to SendOpenSpecialContainer. The docs say:
Code: Select all
Normally only used to show "inaccessable" containers like bankboxes.
If used on normal containers, it allows the character to both view and
change the contents. See SendViewContainer().
This does not explain why the container disappears though. This issue has existed for some time and I cannot remember ever seeing a post about it. So is this a bug with the Core or perhaps a client issue?