mojira.dev
MCPE-25044

Random selector not random enough

Phone : Asus Zenfone 2 ZE551ML (not root)
Hello,

I used the random selector (@r) to a random generation system and it seems that it works always with the same paternal (it choice every time the same entity OR like three different entities but always the sames on the same order)

Idea to fix it : add more paterns to the random selector or change the random system to be more random.

Details : I activate a command block that do
— /execute @r[type=armor_stand,name=Randomer5x5] ~ ~ ~ /execute @r[type=armor_stand,name=Randomizer5x5] ~ ~ ~ /setblock ~ ~-2 ~ redstone_block 0
and this redstone block activate a command block with
— /execute @r[type=armor_stand,name=Generator5x5] ~ ~ ~ /clone [coordinates] [coordinates] ~-2 ~-1 ~-2 replace
Maybe using two times the random selector is the reason but I tried to just select one entity and it's always the three same while I don't move.

Linked issues

Comments 4

In my case, it seems to always target the oldest entity that can be selected. For instance, if I spawn five armor stands, then a command that uses @r[type=armor_stand] will always run on the oldest armor stand that is currently present.

In my case, it seems to always target the oldest entity that can be selected. For instance, if I spawn five armor stands, then a command that uses @r[type=armor_stand] will always run on the oldest armor stand that is currently present.

In my case, it seems to always target the oldest entity that can be selected. For instance, if I spawn five armor stands, then a command that uses @r[type=armor_stand] will always run on the oldest armor stand that is currently present.

In my case, it seems to always target the oldest entity that can be selected. For instance, if I spawn five armor stands, then a command that uses @r[type=armor_stand] will always run on the oldest armor stand that is currently present.

ZeReaper

(Unassigned)

80865

Confirmed

Android

Android 6.0

1.2.0.18

1.2.8.0

Retrieved