I read the thread on injury cluster bugs and agree, from an intuitive perspective, it seems odd. However, and I'm not trying to be a jerk here at all, but there is a common belief that random events should not occur in groups, otherwise it is not random. Unfortunately this is simply not true.
There are certain, proven, mathematical principles that show that the occurrence of random events is not actually random at all (this is called chaos theory) and events occur based on what is called a poisson distribution and process (ie. weird things happen in bunches). It's actually true! Here is a link to an article that explains that seemingly random events do indeed occur in clusters that make no sense, and a link to wiki's chaos theory:
https://stats.stackexchange.com/questions/109390/how-odd-is-a-cluster-of-plane-accidents
https://en.wikipedia.org/wiki/Chaos_theory
In short, I don't think there is much that can be done to prevent freak injury streaks. I think the only coding MFN could put into the system is one that says if a team has had 2 injuries to a player group within, say 15 plays, it nulls the 2nd, or 3rd injury to the same player group. However, such coding would undermine what David refers to in terms of having to watch fatigue and conditioning levels which I suspect are deliberately coded to make sure team managers are factoring that into roster management decisions, particularly on offensive lines.
Just my two worthless bits on the subject.
P.S. and, yes, I will complain too if I get hit with such an injury bug cluster of course! lol.
Last edited at 12/02/2019 5:20 pm