Warrior General Games

This has to stop. Please read this play like a chess board; https://glb2.warriorgeneral.com/game/replay/873386/1448336?player_id=364024 The game is over next move if this kick is made. But you know the CPU kicker will miss it, right? How did you know that? Cause it's GLB2.

Its been over 8 years and this has not been addressed. Fixing kicking will not make the game worst.
Please don't take this as a gripe because my team lost. I just watched this too many times. It's uncalled for and needs to be addressed. The rate of missed field goals, especially for CPU kickers is not only unrealistic but it unfairly undermines long hours of game planning and strategizing.


So what is the logic behind Glb2 CPU kickers regularly missing chip shots? How would it hurt the game if kickers made most of their kicks, or at least make them at a realistic rate? Also Kickers should suffer no chemistry effects. Where they do that at? If I cut a CPU kicker who misses a 30-yard kick I gotta take a chem hit on the next guy? What's that logic? Kickers are plug-and-play.

Thanks for reading. Hopefully, this can be addressed. I'm sure this is not the first conversation on this so if I missed the explanation my apologies.

1

This

Kickers are one of the few positions where only about 5 or 6 stats matter. CPU kickers are terrible because they distribute their SPs randomly, and many of those SPs go into making the kicker a better tackler than a kicker.

Maybe there should be an escalating bonus for short distance kicks so kickers don't look so amateurish. But implement it wrong and you risk making kickers even more boring to build than they are now. What's the point of spending all those SPs when the improvement is marginal over a CPU player?

Originally posted by darkwingaa

Maybe there should be an escalating bonus for short distance kicks so kickers don't look so amateurish. But implement it wrong and you risk making kickers even more boring to build than they are now. What's the point of spending all those SPs when the improvement is marginal over a CPU player?

I want to bring up this little bit because I don't think it quite captures the real picture.

If we look at Smash Rock's kicker he's hanging out at right around exactly 50%. Not great, and is a CPU kicker.

If we look at another team in the same league (I would pick Grape Apes for the fairest comparison but we replaced our kicker at the beginning of this season and spent it all getting back morale) that also made the playoffs in The Program's Matt Prater, we can see he has an 80% completion rate.

I think any of us can agree a difference of 30% is sizable and worth the investment.

kicker is just like 50 sps... It is able to be good without boosting. So just make 1.

Originally posted by ellix
I want to bring up this little bit because I don't think it quite captures the real picture.

If we look at Smash Rock's kicker he's hanging out at right around exactly 50%. Not great, and is a CPU kicker.

If we look at another team in the same league (I would pick Grape Apes for the fairest comparison but we replaced our kicker at the beginning of this season and spent it all getting back morale) that also made the playoffs in The Program's Matt Prater, we can see he has an 80% completion rate.

I think any of us can agree a difference of 30% is sizable and worth the investment.

Yes, right now it's worth the investment. My point was that we could buff CPU kickers to be less terrible, but we don't want to buff them so much that CPU kickers are only marginally worse.

Ghanima is also right in that an unboosted kicker can be significantly better than a CPU kicker. It's a cheap fix.

Originally posted by smashrock
Also Kickers should suffer no chemistry effects. Where they do that at? If I cut a CPU kicker who misses a 30-yard kick I gotta take a chem hit on the next guy? What's that logic? Kickers are plug-and-play.
I believe a changelog some time ago mentioned that CPU players have full Chemistry throughout the season despite what their Chem meter says. So, this shouldn't be an issue unless that was changed back at some point.