http://whatifsports.com/hd/GameResults/playbyplay.aspx?gid=8274593&half=2
 

00:35	Frank Wilson makes the fadeaway from the left wing on a great pass from James Hopwood	72-69
	Dickinson is playing a spread offense (hold ball) and a fullcourt press (+5)		Hamline is playing a motion offense (slowdown) and a man to man (-2)
00:03		72-69	Carl Barragan is hacked by Michael Williams - foul #3 on Michael Williams, team foul #12
00:03		72-70	Carl Barragan makes the 1st free throw
00:03		72-70	Carl Barragan misses the 2nd free throw
00:03	James Hopwood grabs the board	72-70
	Dickinson is playing a spread offense (hold ball) and a fullcourt press (+5)		Hamline is playing a motion offense (slowdown) and intentionally fouling (-2)
00:00	James Hopwood runs out the clock	72-70

He scores to go up 3 with :35.

My C ends up with the ball in his hands with :03 left and is fouled in a 1-and-1 situation.

Something seems terribly wrong about that logic.  Could just be that something went awry, but I had two guards in the game who were decent 3-pt shooters, or, the alternative would be that I would have attempted a 2 a long time before that.

Ticket worthy or just one of those things?

I'm confused by the play-by-play. What, exactly, is your concern?

His center was fouled with 3 seconds left down 3.  He is mad that his center had the ball when they needed a 3 to tie.

I'm mad that my team waited 32 seconds to take a 2.  With three secons left down 3, the ball shouldn't be inside the 3-pt line, and my C shouldn't have the ball outside the 3-pt line.

One of two things should have happened in those 32 seconds my team had the ball: (1) take a 2 early in the shot clock and play the fouling game, or (2) set up for a three with a guy who will actually be shooting a 3.

Basically it seems like my guys ran around for 32 seconds doing nothing and then gave the ball to a guy who would never be able to hit the game-tying shot.

A ticket in this situation is probably useless but send it anyway. I think it's important that WIS know we're watching the game

Maybe, but if the logic is really bad, then maybe it can be tweaked in the future.

But I don't want to send it if I'm being unreasonable, which I certainly can be from time to time.  I just want to know if others see the same thing I'm seeing, or if it's just an oddity that I should dismiss.

You were running slowdown.  That's why they waited 32 seconds.  I would tweak your late game strategy there.   

CS logic would be that your center wasn't necessarily meant to take the shot, he just had the ball with 3 seconds left when he was fouled.   

Posted by sull21858 on 6/1/2012 11:13:00 AM (view original):
You were running slowdown.  That's why they waited 32 seconds.  I would tweak your late game strategy there.   

CS logic would be that your center wasn't necessarily meant to take the shot, he just had the ball with 3 seconds left when he was fouled.   

+1 and I've been on the wrong end of this sort of thing before and I know how ****** off it makes you.

I guess it can be justified by saying there are many things that could have happened...the ball got knocked away from your guard as he was looking for his shot but your Center picked it up and was looking to kick it out when he got fouled...or they were running some kind of hand off/pick play out high to try and free someone up for a shot, etc since as was noted by sull it doesn't say your guy was in the act of shooting a 2 pointer, just that he got hacked

Fair enough, that's kind of why I was asking.

On the flip side, there's no "uptempo when down 3 with :30 left" option.  I think that should be a given, shoudn't it?

I'd much rather set my late-game seconds out a little further, like down 5 with two minutes or something.  It's common sense and should be written into the code that you don't wait until under 5 seconds to run your play when you're down 3.

Posted by ike1024 on 6/1/2012 11:28:00 AM (view original):
Fair enough, that's kind of why I was asking.

On the flip side, there's no "uptempo when down 3 with :30 left" option.  I think that should be a given, shoudn't it?

I'd much rather set my late-game seconds out a little further, like down 5 with two minutes or something.  It's common sense and should be written into the code that you don't wait until under 5 seconds to run your play when you're down 3.

I agree with this. 

At what point does the quick shot offense kick in?

If I am running slowdow as my gameplan, I change under a minute to Normal.  You don't need to necessarily change it to fast.

  We can all say how we would like it to be, but under the current system you need to adjust your strategy accordingly. 

" We can all say how we would like it to be, but under the current system you need to adjust your strategy accordingly."

I'm fine, or close to fine anyway, with the idea that something could have happened (scramble, deflected pass, etc.) to throw off the play.  But I can't accept that the logic is incapable of determining that I NEED a 3 to tie, and that I should no longer be running slowdown.  Changing my setting to "under one minute" forces me to give up changing other settings if I'm down more earlier, and would like to speed it up then. 

For example, if I am down 5 with under two minutes, I want to move away from slowdown.  But I don't necessarily want to do that if I'm only down 3.  And I don't want to wait until one minute left if I need to go sooner.

The reason I'm asking whether I should send a ticket is because I think it should be built into the logic that you don't wait that long to run a play in that situation.  It's not like that's a gameplan option, that's just an it-should-never-happen kind of thing, in my opinion. 

Like I said, I'll accept that something weird happened, but I have a tough time accepting that's the way it should have gone based on my settings.

I think being down three the engine still (unless you have specific settings in place) tries to run the clock down so you take a shot at or near the buzzer to get that 3 pointer off and go to OT - not sure though...

Posted by dacj501 on 6/1/2012 12:40:00 PM (view original):
I think being down three the engine still (unless you have specific settings in place) tries to run the clock down so you take a shot at or near the buzzer to get that 3 pointer off and go to OT - not sure though...

Totally understand that might be the way it works, but does anyone think that's the way it SHOULD work?

I don't know that I've ever seen a team, down 3 with :35, purposely take a 3 at the buzzer.  Under :10 maybe, or only down 2, but it seems ridiculous that a team would wait in this situation.

Maybe I'm wrong, wouldn't be the first time.  Does anyone disagree that a team shouldn't purposely wait until under :05 in this situation when they have :35 seconds to play with?

I get where you're coming from, they were playing a +5 FCP though and you were in a slow down motion offense