Explanation of the Meta Asset Data taken from our Back End
Last updated
Last updated
In the gaming universe, metadata plays a fundamental role. It ensures that digital assets, like in-game items, characters, and collectibles, are accurately represented and described. Think of metadata as the rich information that brings these digital entities to life, much like the description on the back of a trading card or the stats on a piece of equipment in a role-playing game.
But what's even more crucial is the existence of standardized metadata structures. These structures are the agreed-upon formats and frameworks that define how this vital information is organized and presented. They are the common language that gaming platforms, marketplaces, and applications like Metapro use to make sense of the data associated with in-game assets.
For example, a digital sword in a game might have metadata fields that include its name, description, image, rarity, and damage stats. With standardized metadata structures, these attributes are consistently organized, making it easy for platforms like Metapro to fetch and display this information in a coherent and user-friendly manner.
Properties are an essential component of these metadata structures. They provide a way to highlight additional attributes and characteristics of in-game assets. In the context of weapons, properties might include details like elemental damage, special abilities, or any other unique traits that set one sword apart from another. When presented through properties, players and collectors can quickly assess the distinct features and values of digital assets, making informed decisions about their use or trade.
In summary, metadata structures are the backbone of the gaming world, enabling consistent, accurate, and detailed descriptions of digital assets. Standardized metadata is the common language that applications like Metapro rely on to make sense of in-game data, and properties are the showcase for the unique attributes that make each digital asset special. This combination creates a richer and more informative gaming experience for players and collectors alike.
Our metadata is inspired by the Enji metadata standard. To learn more about the Enji standard, click on the
In the 'Token' section, you'll discover essential details about the token. Here, you can access crucial information, such as the token's unique identifier (Token ID), the contract or protocol address associated with the token, and the quantity of this specific token that has been created (a characteristic often seen in tokens based on the ERC1155 standard). Below, you'll find a breakdown of the specific information contained within this section. FilesSpec and Properties have been addressed separately in the documentation for your convenience.
Properties in NFT metadata are used to provide additional information and parameters about a digital asset. They offer more detailed data about items, which can be especially useful in blockchain-based games and NFT collectibles.
Example of the Visual Properties Implementation in the Metapro Market
The Collection field is an additional parameter in metadata and is not required, but it can significantly enhance the value of the game. Collections are used when there is a need to differentiate between various types of items, characters, or other resources in the game. For example, if you're creating a fantasy game, collections can help label different types of weapons, such as swords, bows, or shields. This allows players to easily identify, collect, and utilize various types of items.
Similar to collections, properties (Properties) are not mandatory, but they are incredibly useful. Properties enable the description of attributes or characteristics of specific characters, items, or other game elements. This can be particularly useful in games where different characters possess unique abilities. For instance, if you're designing a character in an RPG game, properties can describe their skills, like the ability to ride a horse, which sets them apart from other characters.
Why Do We Have Levels?
The "Levels" parameter is optional but plays a crucial role in games, especially when determining access levels to specific weapons or items. Levels allow game developers to control when and at what point players can gain access to certain game elements. For example, regarding weapons, levels can specify when a player gains access to more advanced types of weaponry, influencing the dynamics and difficulty of the gameplay. This allows developers to provide players with challenges and encourage them to continue playing.
The "Boosts" parameter is an optional attribute for weapons or items that affects their effectiveness in specific situations. In the context of weapons, boosts allow for the customization of a weapon's behavior for different types of opponents or in various game scenarios. For example, a weapon like the "Fire Sword" can deal additional fire damage to monsters, making it effective against them, but it may be less effective against other types of enemies, such as dragons or demons. Boosts add an element of tactics and strategy, enabling players to adapt their choices during gameplay.
In summary, collections, properties, levels, and boosts are tools that allow for more intricate and engaging gaming experiences. While not mandatory, they can significantly enrich gameplay and contribute to more diverse and engaging player experiences.
In the context of gaming, FileSpec structures play a significant role in digital assets, such as weapons, characters, or other in-game elements. They are used to identify, describe, and manage various types of files or multimedia resources associated with a specific game asset. This can include images, sounds, animations, or even 3D files that add visual and auditory elements to the game.
With FileSpec, games can precisely manage files and multimedia linked to specific elements, allowing for more advanced visual and auditory effects in the game. For example, for a given weapon in the game, FileSpec can indicate which textures, 3D models, and sounds are used in connection with that weapon. As a result, players can enjoy more advanced and diversified experiences while using that weapon.
Overall, in gaming, FileSpec helps developers manage and utilize a variety of multimedia resources, translating into more elaborate and thrilling player experiences.
When creating an NFT Meta asset resource on our marketplace, you will find this in the third step of the resource creation process.
This metadata segment is of paramount importance because:
It helps unequivocally identify and describe NFTs, making asset management in the game more streamlined.
It defines licensing terms that must be adhered to, which is crucial for legal compliance and copyright.
It specifies restrictions and tags, aiding in adapting assets to various contexts and needs.
It categorizes assets, simplifying asset organization within the game and facilitating navigation.
As a result, proper management of this metadata segment is essential for the design and management of Web3 technology-based games.
This JSON fragment, identified by the "2d_spec" key, contains essential information. It specifies the dimensions and characteristics of 2D assets within the game.
"asset_height" and "asset_width" provide the height and width dimensions of the 2D assets, both set at 1024 pixels as integer values. These dimensions are crucial for accurately rendering and displaying the assets in the game.
The "3d_spec" JSON fragment provides essential information about working with 3D assets in the game. It offers detailed insights into the characteristics and complexity of these assets:
The "sound_spec" JSON fragment provides technical details about sound assets. It covers aspects such as BPM, sample rate, bit depth, channels, duration, and an ISRC code, offering valuable information for audio integration and management within the game.
This data structure contains essential information about a specific NFT asset. It includes the asset's identifier, owner's wallet address, contract address, the NFT standard used (in this case, "erc1155"), the protocol (here, "metaprotocol"), the blockchain network (e.g., "bnb-chain"), block number, version, listing status (whether it is available for sale), the creation date of this information, and the "__v" field used for document versioning in the database. This structure is crucial for identifying and managing NFT assets on the platform.
| Key | Value |
|---|
Click to see it live:
| Key Value | Purpose | Application in Gaming |
|---|
| Key Value | Purpose | Application in Gaming |
|---|
| Key Value | Purpose | Application in Gaming |
|---|
| Key Value | Purpose | Application in Gaming |
|---|
Asset Card Page of the Presented NFT Metadata Structure
_id | A unique identifier for the asset. |
_tokenId | The asset's identifier of the protocol can be used for unambiguous identification. |
address | The address associated with the asset (Protocol Address). |
_quantity | Specifies the quantity of available assets of the same type. |
burn | A Boolean value (true/false) indicates whether the asset has been burned. |
createdAt | The date and time the asset was created. |
createdBy | The address of the person or entity who created this asset. |
creationBlock | The blockchain block number in which this asset was created. |
description | A description of the asset. |
extraFiles | A reference to additional files or resources related to this asset, such as sound files, etc. |
favorites | A number indicating how many users have added this asset to their favorites. |
image | A reference to an image associated with the asset. |
initialOwner | The wallet address of the individual who initially owned the asset. |
minifiedImage | A reference to a downsized image linked to the asset. |
owner | The current owner of the asset. |
tokenName | The name of the asset. |
transactionHash | The transaction hash associated with this asset. |
updatedAt | The date and time of the last update to the asset. |
wishes | The number of wishes or desires from users, may reflect interest in the asset within the gaming community. |
asset_type | Determine asset type for proper categorization | Used to classify assets as 2D images, 3D models, audio |
asset_licence | Specify asset's license terms | Informs asset Licence (e.g., Royalty Free, Rights Managed, Creative Commons) |
asset_restriction | Describe any asset usage restrictions | Communicates specific usage limitations (e.g., Public meta asset or Resticted meta asset) |
asset_tags | Add tags for asset categorization and searchability | Helps in find assets with specific attributes (e.g., "NewEra") |
asset_tag_ids | Assign integer identifiers to tags | Ensures consistent and efficient asset categorization |
asset_category | Choose predefined primary asset category | Categorizes assets broadly (e.g., "Weapons") |
asset_subcategories | Choose predefined additional subcategories | Offers detailed classification within primary categories |
asset_category_ids | Assign integer identifiers to categories | Precisely determines the primary category of assets |
asset_height | Determining the height (size) of 2D assets | Helps in precisely adjusting the size of objects in 2D games. |
asset_width | Determining the width of 2D assets | Enables precise specification of the width of objects in 2D games. |
asset_layers | Indicating whether 2D assets consist of multiple layers | Informs whether objects can be composed of multiple layers. |
asset_geometry | Description of 3D asset geometry and structure | Provides information about the 3D asset's geometry, helping developers understand its structure. |
asset_polygons | Number of polygons in the 3D asset | Indicates the level of detail in 3D models, affecting rendering and performance in 3D games. |
asset_vertices | Number of vertices in the 3D asset | Specifies the number of vertices in 3D models, impacting the overall complexity and rendering quality in games. |
asset_materials | Presence of materials in the 3D asset | Indicates whether the 3D asset has associated materials, crucial for defining its appearance and behavior in gaming environments. |
asset_textures | Presence of textures in the 3D asset | Informs whether textures are applied to the 3D model, enhancing its visual realism and rendering quality in games. |
asset_uv_mapped | Indicating whether UV mapping is applied | Specifies whether UV mapping is used, allowing proper texturing and shading in 3D gaming objects. |
asset_animated | Indicating if the 3D asset is animated | Identifies whether the 3D asset has animations, which are vital for creating dynamic and interactive elements in games. |
asset_bpm | Beats per Minute (BPM) | Specifies the speed of the sound, important in music, rhythm-based games, or sound-related gameplay. |
asset_sample_rate | Sound Sampling Rate | Determines the sound's sampling rate, affecting sound quality and ensuring compatibility with the audio system. |
asset_bit_depth | Sound Bit Depth | Indicates the sound's bit depth, influencing sound quality and the precision of sound reproduction. |
asset_channels | Number of Sound Channels | Informs about the number of sound channels, which is important with multi-track sound or spatial sound. |
asset_duration | Sound Duration | Specifies the sound's duration, essential where controlled sound duration is critical. |
asset_isrc_code | International Standard Recording Code (ISRC) | Introduces the ISRC code, which is a unique identifier for sound recordings and can be useful in managing music or sound in game. |
_id | A unique identifier for the NFT asset. |
address | The address of the smart contract associated with the NFT. |
createdBy | The wallet address that created this asset. |
contractAddress | The address of the smart contract associated with the NFT. |
standard | Indicates the NFT standard, which is "erc1155" in this case. |
protocol | Specifies the protocol being used; here, it's "metaprotocol." |
network | Indicates the blockchain network where this NFT resides, "bnb-chain" in this example. |
chainId | The chain ID, which is 56 in this case. |
creationBlock | The block number on the blockchain where this NFT was created. |
version | The version of this NFT, with a value of 0 in this example. |
isListed | A boolean flag indicating whether this NFT is listed for sale (false in this case). |
isAsset | A boolean flag indicating that this item is indeed an asset (true). |
createdAt | The date and time when this information was created. |
__v | A version field, is typically used for tracking document versions in databases. |
token | The "token" section provides detailed information about the token, including its metadata and meta-assets. The components of this section have been previously discussed, covering essential details related to the token's characteristics and associated resources. |
