Shori-Uta
Comments
Could be. But every chest added to the count increases the chance of this not being 'tough luck', but actually being a bug.
The fact that the code works as expected most of the time does not eliminate the possibility of a bug or glitch happening, that is why it's called a bug.
What you did does not recreate all the circumstances which led to this scenario happening. And again, every chest I open increases the chance of this being a bug and not tough luck.
+13 chests to the count, btw.
Chest count: 90+
No, all of them after 1.20... and add +8 chests to the count
There's more gold in those lines than in gold boots.
Since you will just dismiss this I decided to gather actual evidence of what I mean.
The command block purely as you used it does not account for the factors and in computer science we need to recreate all the scenario to investigate the possible existence of a bug. As a software dev, I say many bugs often happen in very specific circumstances. For example, in certain games one can fly or clip through walls if very specific circumstances are met. The fact that in most cases the game works as intended does not mean that in rare cases the code will malfunction or present unexpected behaviour.
And the command block used in a random world does not factor in the world seed and progressive updates in the code/game, for example. These are features that can influence its occurrence.
And there is actual data to show that there is some sort of anormality.
In red 'fog' is the area explored before 1.20.
In green 'fog' is the area explored after the trim update in search for it.
You will notice that there is this sort of red circle area in which the trim was unable to spawn. this doesn't seem at all like mere "bad luck" (as you like to put it).
And in blue 'fog' are end cities explored outside the 'no-spawn-circle'.
blue 'circles' are end cities in which the trim spawned (FINALLY)
The fact that this occurred just past the circle in multiple instances and that there seem to be an actual 'no-spawn-zone' make it seem that this isn't a matter of mere luck, but an actual sort of bug.
It is known that minecraft and any game (in fact any software for that matter) have bugs and I don't know if anyone would be able to recreate it. However using a dry command code in a random world that did not undergo all the "history" of its counterpart isn't the way to claim "nothing to see here, move along" from a dev's pov.
This issue is resolved to me now, but I'll leave the evidence here to future people that may experience something similar, in case it ever happens again.
I won't be checking this thread again.
[media]