Jarodd21s Madden 13 All-Madden sliders

[A_New_Classic]

Finished up Bears @ Titans had a good result :-)

Final score was 24-17 Bears win. Difference in the game was another kick return for TD by Devin Hester in the 1st quarter before dislocating his shoulder later in the game :-(

Team Stats (USER/CPU)

Total Offense: (296/222)
Rushing yards: (130/66)
Passing Yards (166/156)
First Downs: (15/7)
PR Yards: (59/7)
KR Yards: (184/19)
Total yards: (539/248)
Turnovers: (2/0)
3rd Down: (5-10/2-10)
4th Down: (0-0/0-1)
Red Zone TD: (2-2/0-0)
Red Zone FG: (0-0/0-0)
Penalties: (1-5/0-0)
Possession: (22:13/16:47)

Player Stats

Passing
Matt Hasslebeck (CPU) - 101.4 Rating 11/20 177 Yards 55% 1 TD 0 INT 8.8 AVG
Jay Cutler (USER) - 81.9 Rating 15/23 181 Yards 2 TD 2 INT 7.8 AVG

Rushing
Matt Forte (USER) - 25 ATT 129 Yards 5.1 AVG
Chris Johnson (CPU) - 16 ATT 53 Yards 3.3 AVG

Receiving

CPU
Kenny Britt - 3 REC 33 Yards 11 AVG 2 Drops
Chris Johnson - 2 REC 19 Yards 9.5 AVG
Nate Washington - 2 REC 101 Yards 50.5 AVG 1 TD
Jared Cook Jr. - 2 REC 12 Yards 6 AVG
Damien Williams - 1 REC 7 Yards 7 AVG 1 Drop
Kendall Wright - 1 REC 5 Yards 5 AVG

USER
Alshon Jeffery - 5 REC 80 Yards 16.0 AVG 1 Drop
Matt Forte - 3 REC 21 Yards 7 AVG
Kellen Davis 2 REC 19 Yards 9.5 AVG 1 Drop
Earl Bennett - 2 REC 16 Yards 6 AVG 1 TD
Devin Hester - 2 REC 36 Yards 18 AVG 1 TD
Evan Rodriguez - 1 REC 9 Yards 9 AVG
Johnny Knox - 1 Drop

This game played really well I was happy to finally get my run game going and the CPU didn't let up nearly as many sacks as in previous games (only 3 here). Also the CPU threw no picks which was good, but there were probably about 3 really easy picks dropped by my team so their QB still isn't making the greatest decisions all the time. Chris Johnson didn't have a super impressive total, but it was just under average and it wasn't boosted by 1 big run or anything so there is hope for the CPU run game. There were a couple runs where I was legit scared CJ was gonna bust it wide open.

Also I think I'll leave User Catching at 45 instead of dropping to 40 like you suggested, I had 3 drops here in this game and it's been consistent around that number which I think is realistic.

[sls25]

I don't have the retail game or even the season ticket so I'm merely speculating, but in regards to CCM games being way easier do you think it has anything to do with the dynamic performance that was in last year (PPD I think it was referred to as?) being overly sensitive i.e. if someone fumbles they fumble every third carry or interceptions coming in bunches? Also, I read somewhere that production ratings of players start at 0 in week 1 of CCM so maybe it takes a few weeks for players to truly settle into their ratings? Again, just throwing ideas out there as I do not have the retail version.

[Jarodd21]

Quote: Originally Posted by jaredlib

I had to restart my game against Bills. Even with zero rush pass reaction and 70 run block for CPU it just was more of the same.... I am not a slider maker, to be honest I am not sure what I am doing here. Its crazy to me how much worse, at least on slow speed, the CPU run game is in CCM games than play now games. Part of it seems like the CPU RB isnt very aggressive, typically he just runs into his linemen or right into a tackle. Tackling seems to be a bit spot on too. I am going to try this game again, with your tweaks to user catching and INT (I dont feel like raising user pass react time up is necessary on slow speed). I will try cpu run block up to 75 and user tackling down to 40

Trust me when you lower the INT slider the USER pass reaction definitely needs to get raised also because the INT slider affects your defender reacting to the ball in the air.. Hopefully there runblocking at 75 helps open up the run for them.. I know I would be real frustrated right now if I had the retail version with the CPU playing weak like that..

Yeah from everything I'm reading it sounds like the CPU is much more weaker in CC then it is in Play now.. As of now I'm going to leave the sliders exactly where they are and check things out when I get the game.. I have a feeling that I'll be having the CPU sliders extremely high like I have in past years from what I'm seeing.

I can't see how some slider makers are talking about making the USER and CPU sliders equal like the CPU don't need all the help they can get.. Good luck with that.. Haha!

[Jarodd21]

Quote: Originally Posted by A_New_Classic

Finished up Bears @ Titans had a good result :-) Final score was 24-17 Bears win. Difference in the game was another kick return for TD by Devin Hester in the 1st quarter before dislocating his shoulder later in the game :-( Team Stats (USER/CPU) Total Offense: (296/222) Rushing yards: (130/66) Passing Yards (166/156) First Downs: (15/7) PR Yards: (59/7) KR Yards: (184/19) Total yards: (539/248) Turnovers: (2/0) 3rd Down: (5-10/2-10) 4th Down: (0-0/0-1) Red Zone TD: (2-2/0-0) Red Zone FG: (0-0/0-0) Penalties: (1-5/0-0) Possession: (22:13/16:47) Player Stats Passing Matt Hasslebeck (CPU) - 101.4 Rating 11/20 177 Yards 55% 1 TD 0 INT 8.8 AVG Jay Cutler (USER) - 81.9 Rating 15/23 181 Yards 2 TD 2 INT 7.8 AVG Rushing Matt Forte (USER) - 25 ATT 129 Yards 5.1 AVG Chris Johnson (CPU) - 16 ATT 53 Yards 3.3 AVG Receiving CPU Kenny Britt - 3 REC 33 Yards 11 AVG 2 Drops Chris Johnson - 2 REC 19 Yards 9.5 AVG Nate Washington - 2 REC 101 Yards 50.5 AVG 1 TD Jared Cook Jr. - 2 REC 12 Yards 6 AVG Damien Williams - 1 REC 7 Yards 7 AVG 1 Drop Kendall Wright - 1 REC 5 Yards 5 AVG USER Alshon Jeffery - 5 REC 80 Yards 16.0 AVG 1 Drop Matt Forte - 3 REC 21 Yards 7 AVG Kellen Davis 2 REC 19 Yards 9.5 AVG 1 Drop Earl Bennett - 2 REC 16 Yards 6 AVG 1 TD Devin Hester - 2 REC 36 Yards 18 AVG 1 TD Evan Rodriguez - 1 REC 9 Yards 9 AVG Johnny Knox - 1 Drop This game played really well I was happy to finally get my run game going and the CPU didn't let up nearly as many sacks as in previous games (only 3 here). Also the CPU threw no picks which was good, but there were probably about 3 really easy picks dropped by my team so their QB still isn't making the greatest decisions all the time. Chris Johnson didn't have a super impressive total, but it was just under average and it wasn't boosted by 1 big run or anything so there is hope for the CPU run game. Their were a couple runs where I was legit scared CJ was gonna bust it wide open. Also I think I'll leave User Catching at 45 instead of dropping to 40 like you suggested, I had 3 drops here in this game and it's been consistent around that number which I think is realistic.

Good game man.. Stats look better for sure. There run game is still weak from what I see even though you said CJ almost broke a few.. Yeah you can leave the catching at 45.. I just want to see what kind of results that others will get with the catching at 40.. Did you lower the USER INTs to 40 though?

[RogueHominid]

Denver Broncos at Oakland Raiders
Jan 1,	1ST	2ND	3RD	4TH	OT	SCORE
Denver Broncos ()	0	6	0	7	0	13
Oakland Raiders ()	0	2	0	11	3	16

Team Stats Comparison
	DEN	OAK
Total Offense	282	327
Rushing Yards	136	113
Passing Yards	146	214
First Downs	15	19
Punt Return Yards	20	13
Kick Return Yards	25	113
Total Yards	327	453
Turnovers	2	4
3rd Down Converstion	6/15	11/18
4th Down Conversion	0	0
2-Point Conversion	0	1
Red Zone Touchdowns/Field Goals	1/1	1/1
Penalties	0-0	1-5
Posession Time	25:55	37:24

at
Jan 1,	1ST	2ND	3RD	4TH	SCORE
()
()

PASSING C/A YDS TD INT Carson Palmer 22/39 228 1 3 RUSHING ATT YDS AVG TD Darren McFadden 31 97 3.1 0 RECEIVING REC YDS AVG TD Denarius Moore 7 75 10.7 0 Darren McFadden 5 33 6.6 0 Darrius Heyward-Bey 4 51 12.7 1 Jacoby Ford 2 30 15.0 0 DEFENSE TACK SACK INT TD Lamarr Houston 5 3 0 0 Matt Shaughnessy 6 2 0 0 Ron Bartell 0 0 1 0 Shawntae Spencer 6 0 1 0 KICKING FG XP PTS LONG Sebastian Janikowski 2 2 42

PASSING C/A YDS TD INT Peyton Manning 15/36 184 0 2 RUSHING ATT YDS AVG TD Willis McGahee 22 123 5.5 0 Lance Ball 4 13 3.2 1 RECEIVING REC YDS AVG TD Demaryius Thomas 4 33 8.2 0 Eric Decker 3 67 22.3 0 DEFENSE TACK SACK INT TD Von Miller 5 2 0 0 DJ WIlliams 11 0 1 0 Mike Adams 5 0 1 0

I messed up in setting the tables up, but there are the stats from an OT game between me (OAK) and the CPU (DEN). This game took 5.5 quarters of play to end.

I played with the green set, straight up. It felt like the running games were about even, and I felt that my INTs were all deserved. The INTs I got vs. the CPU were fine animations wise, but I continue to out-intercept the CPU each game.

Here's what stood out most to me, though: DEN had 7 drops and OAK had 5. That's an awful lot. I'd imagine that Manning's stat line would have been much, much better had his WR not dropped all those passes. I know that some drops will occur, but I'm wondering if the catch value needs to come up a tad.

Perhaps others are not seeing this.

That aside, the game was, once again, very fun and competitive. I felt like I had to work for every yard. Hats off to you, Jarrod, for getting such a competitive set out so quickly.

I'm going to push the catching up a tad for my own testing purposes to see what happens.

More stats to come.

[Jarodd21]

Quote: Originally Posted by sls25

I don't have the retail game or even the season ticket so I'm merely speculating, but in regards to CCM games being way easier do you think it has anything to do with the dynamic performance that was in last year (PPD I think it was referred to as?) being overly sensitive i.e. if someone fumbles they fumble every third carry or interceptions coming in bunches? Also, I read somewhere that production ratings of players start at 0 in week 1 of CCM so maybe it takes a few weeks for players to truly settle into their ratings? Again, just throwing ideas out there as I do not have the retail version.

That could be part of it.. I'll definitely be looking into it when I get the game..

[A_New_Classic]

I started the game before you posted those minor tweaks so those stats were going from the blue set before those.

[buddy321813]

CPU still too accurate and doesn't drop the ball. I personally think the CPU and Human catch should both be at 40. The CPU could use an advantage in some categories, but WR Catching should not be one of those things. CPU run blocking is killing me.