Jump to content
McKay Development

Dr. McKay

Administrator
  • Posts

    3408
  • Joined

  • Last visited

Posts posted by Dr. McKay

  1. Yes, a TradeOffer object has a confirmationMethod property as you describe.

     

    The value of that property is different for each party in the trade. If you're the sender, then it's populated on send. A nonzero value in state CreatedNeedsConfirmation means that it's waiting on you to confirm it. A nonzero value in any other state means that you were required to initially confirm it using that method, but no further action is required on your part.

     

    On the recipient's side, a zero value in state Active means you haven't tried to accept it yet. A nonzero value in state Active means you need to confirm it using that method before the offer can be accepted. A nonzero value in any other state means you previously had to confirm it using that method.

    1. Player 1 creates a trade offer and sends it to Player 2. Player 1 needs to confirm it: offer state is CreatedNeedsConfirmation and it's invisible to Player 2.
    2. Player 1 confirms the trade. It goes into state Active and both players can view it.
    3. Player 2 accepts the trade. It requires confirmation, but stays in state Active. Once accepted, the API for Player 2 says that confirmation_method is either 1 or 2 (previously 0) depending on email or mobile confirmations.
    4. Player 2 confirms the trade. It changes into state Accepted.
  2. Extracting the token from a trade url isn't a big issue, however I would stick to tokens since it's straight forward. if the token isn't validated means the token doesn't belong to the SteamID provided or is invalid. extracting a token can be as simple as it sounds, but i believe the act of sending an offer via a trade url is more of a hassle than sending an offer via tokens (as it needs more functions).

     

    I'm not sure we're on the same page. Allowing the usage of a trade URL wouldn't remove the ability to use a SteamID and token separately.

  3. The best way to make sure that you don't miss (many) confirmations is to use the same device ID for every confirmation request (on the account).

     

    If you use my libraries for confirmations, then you'll always use the same device ID. If you use a node app alongside a real phone, then there can be problems.

×
×
  • Create New...