|
Quote: |
|
|
|
|
Originally Posted by Ian_Cummings_EA |
|
|
|
|
|
|
|
|
To jump in and correct a few incorrect assumptions - the NFL rule states that clipping is both an illegal block below the waist OR a block in the back.
http://en.wikipedia.org/wiki/America...by_either_team
To MJenness -
- We can't have unnecessary roughness / late hits because as soon as we enable it people would exploit it and post videos all over the place - something the NFL just won't approve
- Illegal forward pass I've been looking into implementing
- Ineligible receiver downfield I've also been looking into implementing
- Illegal touching is a tricky one (i.e. a WR running out of bounds then back in)...I'm trying really hard on this one but there are a bunch of issues with CPU logic that need to be addressed before we turn this one on. I was thinking maybe if we had it in as a slider (and shipped the default slider at zero), then you guys could tweak it up and find a value where it doesn't get called TOO often and neuter the offense.
Even still, all of the above aren't very easy to implement at all - but I am definitely looking into them for you guys. They are things that I've always wanted but honestly I never thought the general public even cared about (until I started communicating back and forth with you guys).
|
|
|
|
|
|
Explain what you mean by a slider for illegal touching? It's a pretty binary situation, the guy either went out of bounds or he didn't... I'm not quite sure what the slider would do or what the difficulty in implementation is for this one. Quite frankly, I would be very upset if it was ever
not called after a receiver stepped out of bounds and then caught the ball. Or dropped it. In fact it already does upset me in goalline situations where the CPU calls plays with streaks in them, the guys run out the back of the endzone, and the CPU pegs them the ball as they run back in.
If the problem is that receivers run out of bounds on their own- well that's a different issue altogether and one that should absolutely be addressed on its own grounds. Receivers should be smarter about the sideline in general, but I don't see why there's a whole lot of "issues with CPU logic". I
am a programmer, and I can't imagine what kind of code you'd have to have that would make it difficult to at the very least make receivers cut off their routes before they go out of bounds.