Sort:  
  • Trending
    • [-]
     5 years ago (edited)

    No. You could have one NFT and use data properties to specify what type of item it is. So you could call your token QUEST or some other name, then in the properties when you issue have a property called name which specifies what the name of the item is. To save money on additional properties, you could have a custom ID and keep track of items in your own DB.

    { 
  "contractName": "nft",
  "contractAction": "issue",
  "contractPayload": {
      "symbol": "QUEST",
      "to": "playeraccount",
      "feeSymbol": "SSC",
      "properties": {
          "name": "item",
          "itemId": 2
      }
  }
}

    You would then reference itemId in your own table when dealing with the NFT to determine what it corresponds to. If managing your own database for items is not ideal, just pay to have additional fields for your token at 100 ENG a piece. So, you could easily have an NFT with 10 additional fields for info at a one-off cost of 1000 ENG.

    $0.00
      Reply
      [-]
       5 years ago 

      No the Databse is Ideal for me. Working on that right now.
      So if I issue say a Quest Token with name Gobln Sword and ID#201
      The player issued the token see’s just the name in the wallet ??
      I would like them to see the image.

      Thanks for the response it made things so much clearer for me

      $0.00
        Reply