This happened in Cust-10 but I posted one yesterday for MFN-1 on that leagues bug report also.

Seems like the TO's are back to being called in the 3rd Q again by teams that are losing


1-10-MAN 37 (0:54) 36-Abel Nguyen ran to MAN 39 for 2 yards. Tackle by 36-Cody Ramos.
Offensive Play: Shotgun Normal HB Dive
Defensive Play: Nickel 3-3-5 Cover 2 Man Under
Timeout SAN
2-8-MAN 39 (0:50) 36-Abel Nguyen ran to MAN 44 for 5 yards. Tackle by 32-Jon Ricks. MAN 36-Abel Nguyen was injured on the play.
Offensive Play: Singleback Big Off Tackle Strong
Defensive Play: 4-3 Under Inside LB Blitz
Timeout SAN
3-3-MAN 44 (0:45) 17-Michael Blecha ran to SAN 48 for 8 yards. Tackle by 94-Ronnie Wymer.
Offensive Play: Singleback Empty 4 TE Deep Out
Defensive Play: Dime Normal Double WR2
Timeout SAN
1-10-SAN 48 (0:36) 17-Michael Blecha pass incomplete, intended for 86-Daniel Watson.
Offensive Play: Singleback Slot Strong All Go
Defensive Play: Nickel 3-3-5 Cover 2 Man Under

I think this is specific to recent updates in MFN-1 - it should be resolved in that version. If anyone else notices the defense burning all their timeouts suddenly in the 3rd quarter, especially in non-MFN-1 leagues, please let me know.

This one happened in Cust-10

This is still happening.

MFN 8. KC vs DEN.

KC called all their timeouts at the end of the 3rd.

http://mfn8.myfootballnow.com/log/1251

Still happenning.

MFN 7.

http://mfn7.myfootballnow.com/watch/1459#314633

Fix is in 0.3.1 which is now in Release Candidate stage.

Happened today in Cust-10 in Divisional round game. No TO's used in first half and opposing team kicked a FG on a promising drive as time burned away and then at end of 3rd Q they burned all their TO's

Absolutely nothing will get done, this is happening too frequently and over too long a period of time, sadly

This is one of those things that, once a fix is found, shoud be deployed immediately to all leagues instead of waiting for the "next version".

While I understand this sentiment, the last time I did this the unintended consequences made it even worse for about a week, and technically this is one of the unintended consequences that is still here. These unintended consequences are also why the next release was delayed - that would have had this fix in it - because instead of getting it solidified in the upcoming engine I was spending my time patching the existing one. There are some bug fixes that are easy to slip into the existing version because the logic is very simple. Timeout decision logic is extremely complex and making what seems like a small change has a butterfly effect that has the potential to blow everything up. MFN-1 is the league designated for testing this, and the fixes are baked into this engine with the additions of other tweaks that would be unfair to release on leagues who have game plans in place with the expectations of how the engine currently works.