Closed ghost closed 1 year ago
It seems I'm experiencing the same thing. Any updates on this @nftchef ? Thanks!
Hi @spike-hue
given your example:
const forcedCombinations = {
"Service Shirt": "Service Visor",
}
forcedCombinations
expects the right side value of the object to be an Array
of items to match it with.
Solution:
const forcedCombinations = {
"Service Shirt":[ "Service Visor"],
}
Notes: It looks like the output here is trying to split the "Service Visor" into a string and then trying to force combinations for files that are single-letter file names
Setting up the following forced combinations for Service Shirt: S e r v i c e V i s o r
your Output 2 where it selected the Service Visor was still not working correctly but happened to roll the trait randomly.
Hope that helps! @JohnCarp if you have similar issues, hope it fixes it, otherwise please reach out to me or open a discussion 🙇
Hello how are you?
Awesome library! So it seems forced combinations is not working as expected. Essentially it works sometimes but not always. What I mean is it does not match like its suppose to and sometimes matches other things together.
In this case I want the Service Shirt to Always match Servicer Visor and nothing else.
Here is an example:
Layer configuration
Forced Combinations
Output 1 Does't Work
Output 2 Works
I also tried adding incompatible layers as a test and it still does not work always as expected (only sometimes)
Thanks for the help!