Talk:Message Spam

Guidobot 00:31, 2 July 2007 (EDT) My part of this article is old now and needs some TLC. I've been using the over-buffering trick for some time but I find it is best to do:

 Message "  " 1
 Message " " 1
 Message " " 1

which helps the messaging system return asap. I've also found using just two messages unreliable. The remainder of my article shows how to avoid using msg buffereing altogether my moving some things indirectly in and out of inventories, etc.

To avoid unequip msg spam you can bump an item out using a token, in combo with the msg over-buffering above. E.g. a helmet that is marked unplayable that you force equip on the player will unequip another helmet.

Reorganization

Removed per request
--Haama 18:38, 10 September 2007 (EDT)

Yep, my original article is old and verbose. (I was trying to give additional tips via scripting examples, etc.) Since there are so many revisions I didn't want to change the front page directly but am happy if you wish to combine all the useful bits. I believe my example of Message buffer overloading is best at the top of this talk page for general Message spam hiding. PlaceAtMe/Activate is the best action for silently adding items and the RemoteTrashCan solution is the best for silently deleting (non-scripted) items from the player's inventory. For scripted objects, using a Shadow (disabled persistant actor) via RemoveMe ShadowRef is best for silent object transfer (followed by ShadowRef.MoveTo player and RemoveMe player for object replacement or DropMe for forced dropping). You should then remove this talk page as other info. is a little off topic.

--Guidobot 19:46, 9 September 2007 (EDT)