Difference between revisions of "OnItemRemoved - ObjectReference"

OnItemRemoved - ObjectReference (edit)

Revision as of 21:10, 28 February 2015

83 bytes removed , 21:10, 28 February 2015

m

→‎Notes

Anonymous user

imported>DavidJCobb

@@ Line 33: / Line 33: @@
 *If you only care about certain kinds of objects, you should also use [[AddInventoryEventFilter - ObjectReference|AddInventoryEventFilter]] to filter out any events for things you aren't interested in.
 **Refer to the notes for [[OnItemAdded - ObjectReference#Notes|OnItemAdded]] to get an idea of how important this is.
-**If something calls [[RemoveAllItems - ObjectReference|RemoveAllItems]] and you don't use an inventory event filter, then for every type of item removed from the object's inventory, one call to your OnItemRemoved event handler will be queued. If the player is holding a very wide variety of items (like alchemy ingredients and books in addition to the player's usual gear), then Skyrim will queue up more calls than it can even hold, and end up dumping stacks instantly. One in-game example of this? The Thalmor embassy quest in the main questline, in which a character takes possession of all items in the player's inventory when the actual mission starts.
+**If something calls [[RemoveAllItems - ObjectReference|RemoveAllItems]] and you don't use an inventory event filter, then for every type of item removed from the object's inventory, one call to your OnItemRemoved event handler will be queued. If the player is holding a very wide variety of items (like alchemy ingredients and books in addition to the player's usual gear), then Skyrim may queue up more calls than it can even keep track of, causing an instant stack dump.
+***The "Diplomatic Immunity" quest is a good testcase for this; getting thrown in jail may also work.
 *If the item is consumed by any means (crafting, charging, poisoning, eat/drink) the dest parameter is None and most likely, but not always, the reference is None too.
 * If player uses a poison to apply it to a weapon the event is fired twice: before and after the confirmation dialogue. If canceled in the confirmation dialogue then is not fired twice.