#TransferInventoryItems Issue

5 messages · Page 1 of 1 (latest)

nimble agate
#

heyo, I'm struggling with what seems to be a bug

executing TransferInventoryItems:
{ "DeleteEmptyStacks": true, "GivingEntity": { "Type": "title_player_account", "Id": "B6D532E3C6D694EB" }, "ReceivingEntity": { "Type": "title_player_account", "Id": "2F9D90ED38BD58CA" }, "GivingItem": { "Id": "58a274fc-2766-43fc-9610-c8cfa59a901e" }, "ReceivingItem": { "Id": "9a9fb8f8-0cf9-4540-bead-463658f8756b" }, "Amount": 1 }

Yields this response

{ "code": 200, "status": "OK", "data": { "GivingETag": "1/MTYy", "ReceivingETag": "1/NDk=", "OperationStatus": "Completed", "IdempotencyId": "3b9a9e72-c46a-4bc2-8382-66fade2db897", "GivingTransactionIds": [ "161", "162" ], "ReceivingTransactionIds": [ "50" ] } }

I'm seeing 161 as the subtract, and 162 as stack delete, but transaction 50 is using the GivingItem instead of the ReceivingItem. As far as I can tell, the Receiving item appears to be ignored

When I was first testing out the rest operation, I could have sworn I'd gotten the ReceivingItem to correctly show up in the ReceivingEntity. Is there some gotcha I should be aware of?

I've confirmed this behaviour in both postman rest calls, as well as a title entity call from unity.

nimble agate
#

@frigid patrol @rain trail

strong dust
#

Hi @nimble agate ,

The documentation might need some additional clarification.

The giving item is what will be sent to the receiving entity.

Example: transfer item A of stack 123.

The receiving item is if you want to map the receiving item to a different stack.

Example: item A of stack ABC.

The scenario you are describing is closer to gifting or exchanging.

nimble agate
#

so, for clarity, you cannot use transferinventoryitems to remove item A from player 1 and add item B to player 2?

#

that makes sense, I was assuming the existence of receiving item in the Player to Player example implied a transformation