The games that
SEEM to keep getting stuck ... are the insane, 300, 400, hell 600 - 0 CPU thrashings. AA2 getting stuck the other day, seemed like it was on this game, as the other 5 simmed ... and this one stayed stuck for like 2+ hours, and started impacting other leagues, that played after AA2. ->
https://glb.warriorgeneral.com/game/replay.pl?game_id=90002&pbp_id=788803Seriously, seems like it would be something not TOO monumental to fix? Though I don't know Bort's code base, so maybe not. But as someone who's programmed for 40+ years, I would hope it's not THAT much spaghetti. Save the hamsters!!!

1) *slightly* bump the average 'template' that CPUs are based on? Outside CPU dots glitching, and going from 79 -> rookie, without getting stats re-adjusted, and going full on GOD mode - the CPUs, are just
WAY too pathetic.
2) Maybe rework whatever algorithm
(if there is one), that keeps putting linebackers, DEs, etc. at KR/PR? Maybe restrict the roster sort for those CPU / D-League teams, to only look at positions that have at least MINOR carrying, (too include KR CB, etc.) and ban the 0 ALG carrying ones from even getting looked at? Hawks had some 500+ to zero games up the ladder, due to that nonsense. (8 carrying KR/PR *seem* - like they're just putting undue stress on the servers, by having to sim so many KOs? Guessing that the path finding part for the sim, is a lot more 'expensive' than normal plays?? I know the AI path finding in FPS, has to be hyper-optimized to not cause serious PAIN, and lag.)