Difference between revisions of "RemoveItem - ObjectReference"

320 bytes removed ,  09:57, 14 August 2016
m
The issue lies with the OnItemAdded Event and not RemoveItem.
imported>Goggle
m (→‎Notes: Some clarification.)
imported>Goggle
m (The issue lies with the OnItemAdded Event and not RemoveItem.)
Line 45: Line 45:
*Keywords and components in FormLists are supported as well, including mixed base objects, keywords, and components.
*Keywords and components in FormLists are supported as well, including mixed base objects, keywords, and components.
*Removing items by component does not scrap the items like extracting components via the workshop does, it simply removes the item itself (and which item is removed if multiple items have the specified component is non-deterministic). If you want to scrap, use [[RemoveComponents - ObjectReference|RemoveComponents]]
*Removing items by component does not scrap the items like extracting components via the workshop does, it simply removes the item itself (and which item is removed if multiple items have the specified component is non-deterministic). If you want to scrap, use [[RemoveComponents - ObjectReference|RemoveComponents]]
* Using this with OnItemAdded Event, will remove the item of the same type that is equipped, instead of the item that has been caught by the event, if you need to remove that for any reason. In other words, it appears this function cannot differentiate between an equipped item from an unequipped item of the same type.


== See Also ==
== See Also ==
Anonymous user