You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a pool of custom player models that are large enough (40+ player models) and I want to have them uniquely assigned.
My idea: have a pool of available player model and another pool of assigned model (exhausted pool), and for each player, pick a random model on the available player model pool, assign it to the player, and pop the model from available player model, then put it into the exhausted pool.
Because all skins are unique, there shouldn't be any problem regarding random distribution.
If the available player model pool is exhausted (say like we have only 32 player models available but we have 64 players), then we simply swap the exhausted pool back to available player model pool. This way, we will have duplicates, but I think it is necessary imo in this case. Another choice is to get another pool of "fallback" player models and do random assignment based on uniform distribution. For example, I would like to use random Blue Archive mob chans as player models if unique character models are not available anymore.
The text was updated successfully, but these errors were encountered:
I have a pool of custom player models that are large enough (40+ player models) and I want to have them uniquely assigned.
My idea: have a pool of available player model and another pool of assigned model (exhausted pool), and for each player, pick a random model on the available player model pool, assign it to the player, and pop the model from available player model, then put it into the exhausted pool.
Because all skins are unique, there shouldn't be any problem regarding random distribution.
If the available player model pool is exhausted (say like we have only 32 player models available but we have 64 players), then we simply swap the exhausted pool back to available player model pool. This way, we will have duplicates, but I think it is necessary imo in this case. Another choice is to get another pool of "fallback" player models and do random assignment based on uniform distribution. For example, I would like to use random Blue Archive mob chans as player models if unique character models are not available anymore.
The text was updated successfully, but these errors were encountered: