A
          / \      _             Play Now                         Nemesis on 
          | |     | |  _______   _        _   _______    _______   _    _______
          | |\    | | |   ____| |  \    /  | |   ____|  /   ____| | |  /   ____|
 /-------/-------------------------------------------------------------------,
O= Home <=XX|  About  News  Pics  Adventurers  Wizards  Download  Connect     >
 \-------\-------------------------------------------------------------------'
          | |   \   | |  |____  | |      | | |  |____   ___ \  \  | |  ___ \  \
          | |     \_| |_______| |_|      |_| |_______| |_______/  |_| |_______/
          \ /
           V  

Documentation Area

Document Path: /doc/efun/transfer

int transfer(item, dest)
object item;
object dest;

Move the object "item" to the object "dest". Some kinds of tests are done,
and a number is returned specifying the result:

0: Success.
1: To heavy for destination.
2: Can't be dropped.
3: Can't take it out of it's container.
4: The object can't be inserted into bags etc.
5: The destination doesn't allow insertions of objects.
6: The object can't be picked up.

Parameter "dest" can be omitted, this_object() is then assumed as
default destination.

'transfer' does not test the notify_*_* and forbid_*_*-functions (see below)!

If an object is transfered to a newly created object, make sure that the
new object first is transfered to it's destination.

And monsters should arrive with 'move_player()' and not be moved in with
'transfer()' or 'move_object()'.

See also:
efun/move_object
living/move_player
object/drop
object/get
object/prevent_insert
object/can_put_and_get
object/add_weight
object/notify_item_enter
object/notify_item_leave
object/forbid_item_enter
object/forbid_item_leave
object/notify_enter_container
object/notify_leave_container
object/forbid_enter_container
object/forbid_leave_container