Skip to content

Scene Metadata vs Land Metadata

PassedPoll

Proposal Details

Author0xb7ee…2c48
PublishedNov 02, 2022 18:33
Voting beginsNov 02, 2022 18:33
Voting endsNov 07, 2022 18:33
Snapshot#902338f

Description

As Decentraland gets more attention from creators and brands that want to hop into the metaverse, builders struggle to promote it properly through the Events feature of the platform when it comes to pre-promote scene builds or deploys happening in the world. While I believe there is a valid reason for land to have its own metadata (title, description...) as it helps on the land market, I find it not useful at all to have the Events location to grab the information of the land instead of the scene deployed. This usually leads to confusion among users, creators and brands that see how from the Map Atlas they see their thumbnail, name and creator properly showcased but from the Events page it takes the data from the state they are in. My proposal is to change the Decentraland Events behaviour and grab the data from the scene deployed in the selected coordinates and not from the marketplace land metadata and make the Events location clearer.

5 Comments

daoNov 15, 2022

Scene Metadata vs Land Metadata This proposal has been PASSED by a DAO Committee Member (0xbef99f5f55cf7cdb3a70998c57061b7e1386a9b0)

daoNov 07, 2022

Scene Metadata vs Land Metadata This proposal is now in status: FINISHED. Voting Results: * Make events grab the scene metadata 71% 844,170 VP (51 votes) * Keep it as it is (grab land metadata) 1% 15 VP (5 votes) * Invalid question/options 28% 340,807 VP (10 votes)

CheddarQuesoNov 04, 2022

Looks like this is not a plausible option based on the votes. I wonder if anyone can explain why this wouldn't be possible.

kourtinNov 03, 2022

No, currently the location data is taken from the Land metadata, same shown from the Land market. Scene.js currently doesnt interact with the events page

UnknowerNov 03, 2022

Isn't this how it already works? The name and thumbnail shown for a piece of land is taken from the scene.json file of whatever scene is currently deployed.