I would not use InvokeRepeating() here use the Update() Method instead for your timing.
I would suggest a simple state machine. Using a timer to switch to Fireing-state and executing of the whole stuff (counting shots, start and time animations and sounds) in Update().
Update then switches to waiting or reloading or whatever state you implement after the 10 shots.
You gotta see the Gunner as an agent with a state machine and very simple KI (It should not shoot when not in range, should it?).
You could invoke just something like...
Invoke("fireShot", 1);
Invoke("fireShot", 2);
.
.
.
Invoke("fireShot", 10);
but then you have no control. What if the player hides behind a wall? What if the player gets out of range. What if the gunner dies?
Sure there is CancelInvoke(), but for the most situations that will bring a lot pain, handling the state with invokes and cancel.
About
>"Basic everyday video game programming> is just long lists of "Invoke"> commands."
I heavily doubt that. And I may quote Game Engine Architecture, p. 9 for the classification of Videogames as
>"soft real-time interactive agent-based computer simulation"
Games are much, in some simple cases like a sequence even a list of invokes, but NOT JUST a list of invokes.
KISS does not only mean "Keep it simple, Stupid!" too. It also means "Keep it simple and straightforward" and some other interpretations depending on your situation. An that would (IMAO) mean make a small simple agent with a state machine, because a gunner with it's own little brain and states is straightforward and a good abstraction for a "living" game object.
↧
