This is the power of cc0. That person doesnโt need to be active and the character/IP is public domain.
Weโve already encountered She Who Smiles, Piyu, & Detriti in the game. None of these required the owners being active.
On the flip side we tried involving Richardโs Luta the Beacon & it didnโt really evolve into anything, whereas Merlinโs own char creation, Elise and Ruined Shrine ties to the seal and Yuria had a more profound impactโฆ
Merlin wasnโt forced to behave the way he did and the owner of Yuria wasnโt involved.
You have passion and your heart is in the right place but trying to force people to do things and punishing those who donโt isnโt the answer.
Besides we already have hardcore mode and friction.
We have events people canโt participate in without risking their NFTs and they have to be paying attention when call to action happens or they miss the opportunity to participate. These things are already punishing enough to those who arenโt committed 24/7 and donโt have excess capital to afford throwing an nft away.
Even the best games offer hardcore and casual modes. Ranked and unranked. We have one side of it already covered and are doing it well. We also need to think about the other side.
Itโs cc0. You can create a storyline with that char without that personโs permission.
Cant edit the char sheet, canโt vote with that token. But you could rock that pfp, make story with it and hey maybe even get that persons attention and then negotiate buying it off them or get them to update the sheet.
Not saying you can force them to sell or change it, thatโs their choice. But no one is stopping anyone from creating story with any chars they want.
It may not fit the canon or mainline, it may find its way in, depends how itโs done and whether the community accepts it. But what youโre saying is a problem is actually not an issue and if anythingโฆ itโs part of a solution.
If we have good holders who arenโt active, those are chars that arenโt being utilized and Iโm sure theyโd be honored and happy to see people creating story with their chars
While lack of participation might be frustrating to some I do not personally feel itโs up to us to take unilateral actions based on how we think people should be interacting with the project.
One of the core principles of WAGIDE is consent.
Every burn has been something you the community has opted into. The only metadata changes so far have been to WAGIDE owned by the team or to reveal a concord. I canโt see any future path where we change this dynamic.
This is an interesting idea and something that is very doable. POAPs could also have a much lower voting power than WAGDIE tokens to ensure the community has a greater say. It does open up some issues with the funding proposals but there is always the option to split off story based voting from conclave voting.
Participation POAPS (voting power only for story line) This would primarily be in the Keeperโs hands, so doesnโt need a champion yet.
If the goal is to onboard new people, having a simple barrier would suffice. Multiple choice question about a specific detail in the narrative space. We can monitor for abuse down the line, but we donโt need to have a perfect solution now.
The art for the POAP can be a scene from the specific story itself by the Keepers, maybe the community can contribute down the line.
Yes haha I made them for fun really nothing serious. I like to listen to them while some events unfold in the game. But yeah I totally think itโs a great idea to adapt intro/outro songs to enhance the UX.
Any reference, suggestion or criticism is welcome. Iโm interested to know what does @josiah.peace (I wonโt get tired of saying how good the ads of The Grand Tournament were), and @tenacity.eth thinks about the intro/outro songs idea.
In the meantime, I can edit loops/clips of songs/beats that can go along with the podcast. We can also take the path of producing original music for the weekly space, in my opinion both are effective. The key is in the sentiment of familiarity generated by the music, thus creating a greater impact on the listenerโs memory.
