-
Notifications
You must be signed in to change notification settings - Fork 117
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
A way to turn off Empty trait for some traits #41
Comments
@shaanyeat can you just make sure that the rarity of available options adds up to 100% and there are no conflicts that set the value to empty? or is there something i'm missing? |
I have set each each trait to be 100%, then from 7 Traits lets say I set Trait 2 as an conflict with Trait 3, Then when I went to create a composite there would be some where both Trait 2 and Trait 3 are set as none? Even when I set Trait 2 to 50% and Trait 3 to 50% hoping that that would balance it out, But that did not help either. I still would see some of the traits I set in the conflicts both coming out as None. Hope I made myself clear |
@shaanyeat seeing the same thing myself. did it ever resolve for you? |
@shaanyeat & @brantchoate also seeing the same issue. I've seen this happen to a few people in the discord but dont think its been solved yet |
Could someone add minimal steps to reproduce from setting a project to configuring traits please? trait sets may help out here if used instead of conflicts. |
A way to ensure some traits can NOT be empty (None) while making composite.
The text was updated successfully, but these errors were encountered: