NFT chance function question for future production purposes #1630
Unanswered
AlexK020908
asked this question in
Q&A
Replies: 1 comment
-
I have not gone through any productions, so I could be wrong here. I am assuming from my understanding that -- let's assume a Dog NFT -- the breeds will be just a handful and possible-to-get for anyone (and not 800+), but what they will have is a limited but excess amount of features which, once randomly used on a NFT is removed from the array (which stores the possible combinations/features left). Thereby, preserving the unique status. TL;DR Common features -- excess but limited, unique traits which segregates the common features from the rare ones while keeping the common ones distinct. Hope this helps. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
I am reviewing the randomlpfs module, and I see that utilizing a chance array may be very useful to represent rarities, however, in the example we only used three URIS. Many of the productions I have seen sometimes have 888 or more NFTS.
If we used the
getBreedFromModdedRNG(moddedRng)
function like we did in the module , wouldn't the code get very large?for example
for a 90 percent chance , you can get common NFTS, and we have 700 commons...
how do we select one common from the 700 and send it over to the onwer? would we have to make an enum that is 700 units long?
code reference:
Beta Was this translation helpful? Give feedback.
All reactions