Report this content
We want the Dreams coMmunity to be a safe, diverse and tolerant place for everyone, no matter their age, gender, race, sexual orientation or otherwise. If you believe this content to contradict these principles, you can file a report for our coMmunity teams to investigate.
Note that misuse of the reporting tool will not be tolerated.Item being reported:
Randomiser Zero-Weight:
Before the update, I did wonder how 0 would be handled, as it could be pretty confusing. I thought that most likely the minimum weight would be 1, to avoid all those edge cases and weird situations. But the minimum is 0, so now there are weird confusing edge cases and situations :)
Creators understand the randomiser to work in a particular way, based on how it works without touching the weightings (as in, years of experience), and the names of features in the UI, etc. But the way 0-weight affects the algorithms goes against those understandings, and so will be confusing in certain edge cases.
- Understanding: 1 channel will always be active. New behaviour: with 0 weight, a channel cannot be active. If all weights are 0, no channel will be active.
- Understanding: shuffle is like shuffling a deck of cards; you’ll come up with all of them before staring again. New behaviour: with 0 weight, a channel won’t be included in the sequence at all. Even if the weight is changed, it will never show up.
- Understanding: no-repeat will choose one channel out of the channels that are not currently active to be the next active channel. New behaviour: if only 1 channel has a non-0 weight and that channel is active, the next time “randomise” is triggered no channels will be active.
I don’t know if this is really a load of bugs; it may be working as designed. But it’s definitely working in a way that will confuse people until they gain a deeper understanding of how it’s actually coded.