steelerfan's AA sliders

[steelerfan]

These are the sliders I've been using in my Dynasty. I made some tweaks as recently as 3 or 4 games ago, so I'm sure as I improve I'll make more. I am using Baylor so take that into consideration. The main thing that was ruining the game for me was the number of INTs thrown by the computer which, if nothing else, these sliders appear to get under control. I am playing on AA (obviously) using 9 minute quarters. FWIW, I'm on ps3. I don't have the exact number of INTs from season 1, but in season 2 the CPU has thrown me 9 INTs in 7 games, so I'm pretty happy with that. The CPU does usually complete about 65% but I can't seem to control that without bringing the INTs back. Anyway here it goes:

RULES: 45, 65, 85, 100, 100, 85, 85, 45, 50, 100, 100

UO: 55, 80, 35, 50, 75
UD: 5, 0, 0, 70, 65
US: 25, 25, 45, 75, 40

CO: 60, 40, 30, 60, 65
CD: 10, 0, 0, 55, 65
CS: 25, 80, 35, 100, 60

Good Luck!!

[gnperdue]

65% against Baylor is realistic. Maybe even low, lol. What is your record in conference play with these sliders?

Also, have you played using powerhouse with these sliders?

[steelerfan]

65% against Baylor is realistic. Maybe even low, lol. What is your record in conference play with these sliders?

Also, have you played using powerhouse with these sliders?

Year 1 I was 3-9 (2-6). Year 2 I'm now 6-2 (3-2). Not real thrilled with a 6-2 mark this year, so like I said, I'm sure I'll continue to make adjustments as I get better. I have not tried using a powerhouse with these. I think, if nothing else, my penalty and special teams sliders are very good. The main problem of CPU INTs is good too. The CPU has now thrown 10 INTs in 8 games in year 2. I just wish the CPU would throw deep sometimes.

EDIT: I should tell you that I did use my early sliders using all sorts of teams and had good results.

[gnperdue]

Comparing these to mine, the big differences are you have a lower user awareness (probably, this is what pulls down the INTs), a higher QB accuracy for both, and lower catch rating for both.

You also have the CPU running ability and blocking pretty low. How is the CPU run game? Also, does the CPU actually respond to the lower FG length or does it still try 57 yarders?

I installed one of your features (lower user awareness) and saw a better CPU passing game out of it, but the decision making by the CPU QB was still beyond abysmal.

[steelerfan]

The CPU runs against me fairly well. Javorskie Lane had 187 yds against me last night, lol. But, again, I'm using Baylor. The catch sliders were lowered to promote a couple more incompletions per game since I raised accuracy to fight the INT problem.

The CPU definitely responds to the FG power. As I recall, the CPU has only hit 1 or 2 50 yarders against me in 21 Dynasty games. And they were like 52 at most. The CPU isn't lining up for 57 yarders either which is good. As you may realize, I would recommend raising only sliders that will have no bearing on INTs (ie not AWR, KND, INT). Be careful abour pass blocking also. More pressure = more INTs. I currently have recorded 17 sacks in 9 games this season and my team leader has 5. I'm good with those numbers.

[DonohoFlnkr]

Steelerfan,

I will be trying these out tonight. I attempted playing a dynasty using PMaker's sliders, but all it got me was a broken controller. The OL doesn't block for me at 50, much less 20. My Def won't tackle on 50 either, let alone 35. I could go on and on, but what I see in these sliders is that as a B+ Off and a B defense, I might actually get some realistic games rather than wondering WTF all game long.

[gnperdue]

These are pretty good. I'll give them the gnp stamp of approval, for whatever that is worth, lol. They're similar to my last set, I just didn't have the huevos to take user awareness all the way down to 10. I think that makes a big difference in the INT issue. I'll have to test lower catch ratings too because with my current sliders (and steelerfan's super low human awareness), every game is going to be a 38-35 shootout. I have the CPU awareness at 40 I think (his is zero), so it is tougher for me to move the ball and there is a lot of pressure to score with user awareness at 10. Still, that said, even though I would like to see scores more like 24-17, and even the occasional 13-7, I'll take a 41-38 thriller over a 49-13 beat down where I pick off five passes (and take three to the house) any day.

I feel for you on the O-line issue. I played a season with Clemson and got tired of watching my 96 OVR all american left tackle simply side-step and block nobody at all while allowing the DE to rush inside untouched over and over. Meanwhile I couldn't even get a sniff of the QB, even against sub-par teams like ULM. I've gone even further there and have user pass block at 100 and CPU pass block at 15. And the CPU protection is still way better than anything I can get even out of a superior line.

[steelerfan]

Thanks for the gnp!;) I do have lots of low scoring games. In fact, I had a 16-6 game yesterday. My starting HB is averaging 3.3 Yd/carry, so it's not a prooblem. If he got too much higher I'd feel like I was screwing the CPU as my O-Line and HB are all in the low 80s OVR. I control a DT or DE at the start of every play. The best advice I got on this board was soce's advice to mix up playcalling/looks on D. I was stuck in a cover 2 man/press rut and felt like I gave up big plays when I deviated from C2M. I have found, as soce said, that really mixing it up throws the CPU out of sync and gives you a chance to get pressure on their QB. I doubted that alot, but my desire to change coupled with my trust of soce prompted me to give it a shot. Anyway, thanks for checking in and let me know how it goes.

[joshuahuskers]

I gave these a shot. I don't think they are for me. I'm Nebraska playing at Mizzou. It's at halftime right now. I'm up 17-0. Missouri has a grand total of 47 yards of offense.

My starting HB (Cody Glenn) has 20 carries for 30 yards. For those of you not mathematically inclined, that's 1.5 YPC. The only plays I can even sniff positive yardage with are the inside handoff plays. I've tried all types of run plays, but combined the outside handoff, counter, draw, and toss plays have probably had one play go for positive yards, and I've netted negative yards on those plays.

Despite the lack of a running game outisde of "inside handoff", I had scoring drives of 21 and 13 plays. I just don't think these are for me. I'm going back to my modified version of play makers.

[steelerfan]

Like I said, I'm using Baylor. Joshua, if you wanted to continue with these you could try lowering the HUM AWR to 0 and tweaking the CPU offensive sliders too. I played for a long time with HUM AWR at 0, but with Baylor, I just wasn't having any fun (don't mind losing). Like I said before, I think the close-to-perfect areas of these sliders are turnovers, special teams and penalties. You may have to adjust the other areas depending on your team and your skill level. I am running with moderate success and that's good enough for me with Baylor.

[joshuahuskers]

I definitely agree with the turnover part. I was VERY pleased. I committed none in that first half, and Mizzou had one errant throw that my safety picked up. I actually didn't mess with the peanalty settings, maybe I'll implement those and see how it goes. Playmakers sliders just give me a better game.

With these, I feel like I'm going to win the game. With his set, I feel like I'm always in a game, and I don't know the outcome until late in the game. When I'm playing a good team, I always feel like they could come back (I blew a 17 point lead vs. USC in the 4th quarter).

I may play around with these in play now some more and make some tweaks. I'm going to be rolling with Playmakers for my dynasty for now, though.

[steelerfan]

That's cool, Joshua, I understand. We all have to use what suits us. Just thought I'd give you some ideas before you gave up. Good luck.

[gnperdue]

I took these for a spin last night in a play now game with Maryland (me) vs. West Virginia. I made a few changes and had CPU Running Ability at 75 and CPU Run Blocking at 70. I moved CPU Def. Awareness to 40 and set catching for both was at 45, but that was too high, as the numbers show:

MD 31 - WVU 28
MD Rushing: 40 for 155, 1 TD, 2 Fumbles Lost
WVU Rushing: 30 for 149, 3 TD, 1 Fumble Lost
MD Passing: 16/19 for 288 yds, 3 TD, 0 INT, Sacked 3 times
WVU Passing: 25/34 for 254 yds, 1 TD, 0 INT, Not Sacked

The kicking/return game was solid but unspectacular this time. No INT's which is the really good news. I almost had a couple, but my players dropped them. So there could have easily been one or two, but that's fine.

The 1st quarter was slow, with the teams exchanging fumbles. WVU had me pinned on my side of the field most of the 1st quarter and took advantage of a fumble inside my 20 to take a 7-3 lead just as the 1st quarter expired.

After that it was a basketball game and both teams were almost unstoppable. There were some punts and some stops, but it was very much an offensive game. We were both running the ball a lot though and that kept scoring down (could have easily been another ten or twenty total points). WVU probably would have won except for Pat White's horrible running. He ran six time for -22 yards and lost a fumble. I don't really blame this on the sliders though - the CPU just doesn't know how to run a QB Choice play. They were also killed by having a 49 yard TD run called back on holding (I keep all penalty sliders maxed out except clipping, whihc I leave at 50). My QB threw for a high %, but they were all dink and dunk. I had one 22 yards-in-the-air TD that was really nice, but the yardage was inflated by a swing pass that ended up going almost 80 yds and by a bubble screen that went for more than 60 (both TDs).

My 22 yarder was memorable because it had a great spectacular catch animation. The ball was thrown to the pylon and the reciever reached way out of bounds to snag it, stabbed a foot down, and then tried to get the other down, but his momentum pulled him out of bounds. I watched the replay about twenty times. I bet that animation is in Madden for an "almost" awesome catch.

I think I had the Catch ratings too high at 45, but CPU awareness is fine at 40 and the run game was fine at 75/70. Pat White couldn't run, but again, I don't pin that on the sliders. Maybe I should try 70/75 or 75/75, but I don't want to overpower the CPU run game to the point that scrubs are monsters. Steve Slaton can be a terror and that's fine, but I hate giving up big runs to garbage teams, so I'm nervous about going over 75/75 for CPU RBA/RBLK.

Pass protection was fine I guess (actually, another change there, I had 100 for User and 15 for CPU). I never hit White but I did hurry him a few times. One sack was my fault (held the ball too long), the other two were ridiculous Jumped Snaps, one on Play Action (WVU did not respect Play Action at all through the entire game), and another on some random play.

One last comment is that I played with my standad "house rules" in effect - the same offensive play cannot be run twice in a half and the same defensive play cannot be run twice in a quarter. I think these are perfect for this low awareness setting because otherwise you might worry about abusing a money play.

Overall I'd say you can get away with bumping up the CPU run game some (maybe you just don't want to put up with 200+ yard efforts out of everyone while playing with Baylor) and I think you can bring up the CPU awareness. You definitley had the Catch ratings right though, and the QBA bump + lower User Awareness really does put a dent in the INT problem. So, in short, nice job. I tweaked them some, but your core ideas are good for a fun, if high scoring, game. Like I said above, I like me some defense, but this would have been exactly the kind of game you would want to watch on a Saturday night in October (well, the kind Maryland fans would want to watch, lol).

[steelerfan]

Interesting findings, thanks for the compliments and for putting in the time to test and report.

I really am OK with the pressure I get on the CPU QB. I just finished year 2 and had, I think 24 sacks.

I also think that, while I have the occasional 38-35 game, I never get a basketball feel of back-and-forth. In year 2, I averaged 21-point-something points per game. Maybe later I'll post all of my year 2 scores.

[killerBsaturn]

My favorite set of sliders I have used so far. I only had to up user catch to 40. Too many passes bouncing off my TE's and WR's chests.

[steelerfan]

Glad you like them, killerB.

Note to all: I just made some minor tweaks for season 3. I edited the first post to reflect the tweaks.

In my first game in season 3, I won 21-20 at WF. The CPU missed a PAT with 8:35 left (9 minute quarters). There were 0 turnovers in the game. It was an ominous beginning to the season when the CPU returned the opening kick 95 yds for a score. The CPU only completed 52% (very rare in my Dynasty) on 9-17 passing.

[gnperdue]

They're a really solid set. If you don't go out of your way to cheese the CPU, I think they're about the most fun set out there.

The only thing I really think you have "wrong" is CPU running. It has to be at least 70/70, IMHO. Although, playing Baylor doubtlessly influences your choices. I don't think it possible to get realistic sliders for A and C teams simultaneously.

[grisch44]

Steelerfan, if these results hold up, you've created the best sliders I've played so far and I've played with A LOT of them. I only picked the CPU twice and they were legit, one by my impact MLB.

There were only 2 issues that I saw:

The CPU running game didn't get going against me. (Of course I was playing with my Buckeyes against NWU so they shouldn't). I'll need to test with a better running team.

I didn't generate any pass rush without blitzing. I'll get a couple more games under my belt with these and determine if I need to lower CPU pass blocking.

Finally, I "fat finger" the controller. I threw a stupid INT for 6 by completely hitting the wrong button and threw into double coverage for another pick. Otherwise, this game would have gone off the way it should have with a 34 to 13 win. Instead it ended up a 27 to 20 win.

Regardless, the game play felt great.

Thanks for the sliders!

[steelerfan]

Thanks alot guys. It is important for everyone to understand that I am using Baylor. The CPU can run against me, but if I had some talent in my front 7, that may not be the case. Adjusting CPU RB or RBA shouldn't ruin these sliders. You can also try playing with User D AWR at 0. The main thing is to not mess with the turnover inducing sliders. The others can be adjusted to meet your team's ability and your skill level. I'm really glad some of you guys are enjoying these. I hesitated for some time to post them because I didn't want to hear the "these suck" rants when I'm happy and just trying to help others make the game playable.

[DonohoFlnkr]

Thanks alot guys. It is important for everyone to understand that I am using Baylor. The CPU can run against me, but if I had some talent in my front 7, that may not be the case. Adjusting CPU RB or RBA shouldn't ruin these sliders. You can also try playing with User D AWR at 0. The main thing is to not mess with the turnover inducing sliders. The others can be adjusted to meet your team's ability and your skill level. I'm really glad some of you guys are enjoying these. I hesitated for some time to post them because I didn't want to hear the "these suck" rants when I'm happy and just trying to help others make the game playable.

I will be going to these sliders when I run my Sun Belt, lower tier BCS, or other small school/ground up dynasty later on in the year. I think they are VERY good for that. I'm just holding off from these for my AU dynasty.

[steelerfan]

I will be going to these sliders when I run my Sun Belt, lower tier BCS, or other small school/ground up dynasty later on in the year. I think they are VERY good for that. I'm just holding off from these for my AU dynasty.

These would likely need some CPU favored adjusting for a Sun Belt team because the level of competition would be low also. Playing Texas, Oklahoma and ATM every year is a bit different. Just keep that in mind in the weaker conferences even if your team is weak.