BuzzerBeater Forums

Bugs, bugs, bugs > wrong substitution tactic

wrong substitution tactic

Set priority
Show messages by
This Post:
00
175601.1
Date: 2/23/2011 7:05:37 AM
Overall Posts Rated:
5858
During my game last night, the computer subbed out my point guard at the start of the 4th quarter even though he was assigned to all three spots (starter, backup, 3rd string) on my PG depth chart, and even though I had 'strictly follow depth chart' as my tactic. It seems that the computer incorrectly used the tactic 'follow depth chart until 4th'. Can 12 minutes of PG playing time be added to D. Montanaro? How am I supposed to single position train if the computer decides for itself which substitution tactic to use?

Game link:
http://www.buzzerbeater.com/match/30369617/boxscore.aspx

Thanks,

Mzungu

This Post:
00
175601.2 in reply to 175601.1
Date: 2/23/2011 10:07:08 AM
Overall Posts Rated:
312312
You were up by more than 20 and had more than 9 players suited for the game. In a blow-out like this, if there are players available the coach will always pull the starters. You needed to only have a starter and a backup (you can list the backups again as reserves if you want) for each of the other four positions and then Montanaro at all three spots for PG. By having that extra player available on the bench, the coach will substitute for every starter no matter what tactic you've selected.

This Post:
11
175601.3 in reply to 175601.2
Date: 2/23/2011 10:41:36 AM
Overall Posts Rated:
5858
If that is the case, the game manual should be changed.

"You can use entirely your judgment (Strictly Follow Depth Chart)...or you can use your depth chart strictly until the 4th quarter, then tell the coach to try and win the game however he thinks is best (Depth Chart until 4th)."

Clearly, if I told the coach to only play Montanaro at PG, but he pulled him for the 4th, the substitution strategy was not based ENTIRELY on my own judgment. If I told you that I ate an entire apple pie, but you know that you ate a slice, you would call me a liar. Same thing applies here.

The developers should change the how the tactic is implemented (my preference) or change the guide book, because the status quo is misleading.