Warrior General Games

How are people setting this up? The only time when you'd really use is after a completed pass with no timeouts left, but there's no way to set "after a completed pass" as a condition for an input. If you just set it 1st & 10 with no timeouts, you could end up spiking on the first play of a possession or immediately after calling your last timeout.

0:35 2nd & 8.5 OPP 47 Siena IL PALIO calls timeout Replay
0:35 1st & 10 OPP 28.5 LoneStar Staubach spikes ball Replay

Good question.
We call a timeout, then we spike the ball.
This shouldn't happen, it should be a no brainer to not spike the ball after a timeout.

You need to set your timeouts to 0 in AI.

And you should use spiking in the last seconds, and in 1-3 downs. If there is time for one more play, it doesn't really matter if it's 1st or 3rd down.

Edit: hmm... Even if the timeouts are set to 0, AI might make that thing... So therefore forget about spiking the ball.

I came looking for a thread like this because I had the same question as harsh. At first I had the same answer as Kyy, and then his edit realization.

Without Bort changing the Inputs to include a clock-running switch, I don't know how to get this to work in any situation other than 15-20 seconds left on the clock and spike until you get to 4th and kick the FG.

Also..does the spike logic force a hurry up offense approach?

If you run a spike ball play with 37 seconds on the clock as you're tackled in bounds, is it going to run 40-45 seconds, or is it going to snap it in 10-12.

I think you should just forget the spiking, as the AI WILL spike the ball when you take your last timeout.

And no one know if hurry up offense is used. Cos if not, you spike the ball while you could have run your playbook play at the same time.

without an output for clock running/clock stopped, it's worthless.

Thanks for replies, glad I'm not the only one who couldn't figure out any viable way to make this work. Maybe I'll take this over to the Bugs forum and hope that Bort pops in.