NDL Forum

Georgia has quite a few frosh that made it which only helps in dynasty mode. Only thing I didn't like was they had Tray Matthew at backup SS when he should be starting FS.

ChampDizzle wrote:Georgia has quite a few frosh that made it which only helps in dynasty mode. Only thing I didn't like was they had Tray Matthew at backup SS when he should be starting FS.

Was this caused by EA or by the guy that named the players?
If it was by EA, nothing we can do about that.

We just want to make sure that the guy that named the players didn't mess something up.

The_Niddler wrote:

ChampDizzle wrote:Georgia has quite a few frosh that made it which only helps in dynasty mode. Only thing I didn't like was they had Tray Matthew at backup SS when he should be starting FS.

Was this caused by EA or by the guy that named the players?
If it was by EA, nothing we can do about that.

We just want to make sure that the guy that named the players didn't mess something up.

EA screwed him, he is going to lay the lumber on the opposition this year.

The roster set that Oracle has in his locker has players moved to different positions. At lead on Arkansas it does. They have #17 Brandon Mitchell at QB when out of the box he is at WR.

razor, I ask the same question again....is this EA's doing?
If you do not load those rosters, is he still setup that way?

If EA is who messed it up, then there is not much we or anyone can do about that.

The_Niddler wrote:razor, I ask the same question again....is this EA's doing?
If you do not load those rosters, is he still setup that way?

If EA is who messed it up, then there is not much we or anyone can do about that.

When you go on-line to play the rosters revert back to the default positions/ratings, just with player names. The edited rosters have no effect on the league other than online/off-line dynasties.

Thanks mike, I did not know that.
So in that case, it is shame on EA. So the rosters we downloaded are fine. Good to know.

The_Niddler wrote:razor, I ask the same question again....is this EA's doing?
If you do not load those rosters, is he still setup that way?

If EA is who messed it up, then there is not much we or anyone can do about that.

It's definitely EA's fault as he is actually not even on the team anymore. He transferred to NC State after getting beat out for the starting QB job by Brandon Allen during spring practice.

He will revert back to a WR when an NDL game is actually played with them.

My concern about that is with his skills at QB he is currently listed as the #1 QB for Arkansas however he will actually be a WR anand Brandon Allen is the starter. What if someone picks Arkansas thinking they will have him at QB when in reality they can't do that because he is actually WR #17 on the game?

razorback44 wrote:

The_Niddler wrote:razor, I ask the same question again....is this EA's doing?
If you do not load those rosters, is he still setup that way?

If EA is who messed it up, then there is not much we or anyone can do about that.

It's definitely EA's fault as he is actually not even on the team anymore. He transferred to NC State after getting beat out for the starting QB job by Brandon Allen during spring practice.

He will revert back to a WR when an NDL game is actually played with them.

My concern about that is with his skills at QB he is currently listed as the #1 QB for Arkansas however he will actually be a WR anand Brandon Allen is the starter. What if someone picks Arkansas thinking they will have him at QB when in reality they can't do that because he is actually WR #17 on the game?

While I understand your concern, we cannot control what EA does.

razorback44 wrote:

The_Niddler wrote:razor, I ask the same question again....is this EA's doing?
If you do not load those rosters, is he still setup that way?

If EA is who messed it up, then there is not much we or anyone can do about that.

It's definitely EA's fault as he is actually not even on the team anymore. He transferred to NC State after getting beat out for the starting QB job by Brandon Allen during spring practice.

He will revert back to a WR when an NDL game is actually played with them.

My concern about that is with his skills at QB he is currently listed as the #1 QB for Arkansas however he will actually be a WR anand Brandon Allen is the starter. What if someone picks Arkansas thinking they will have him at QB when in reality they can't do that because he is actually WR #17 on the game?

According to the rules he could be used as a back-up QB.

SUBSTITUTIONS:
QB: QB. (Any player with a 70+ in THP may be a BACK-UP)
HB: HB
FB: FB, HB
WR: WR
TE: TE, FB
OL: OL
DL: DL
LB: LB, DL
CB: CB, S
S: S, CB, LB

--RBs will no longer be allowed to play FB regardless of their blocking numbers, packaging allows for two tailbacks to be on the field at the same time..
--No offensive players on Defense and vice versa.
--The #1 and #2 overall WRs must be used in the #1 and/or #2 positions. Placing a quality receiver down on your depth chart to take advantage of matchups is unacceptable.

PACKAGES:
With regards to the above three bulleted items there will now be a slight limitation of packages. ALL packages are available to use and are "fair game" with these 3 exceptions.
-- #1 WR CANNOT be moved into the slot. There are about a dozen offensive formations that allow you #1 WR to be moved to the slot. The ONLY defensive formation that allows you to move your #1 CB into the slot is nickel. This is not equitable and therefore not allowed.
-- CB 5 Wide - in the 5-wide sets there is a package that allows for a CB to line up at WR. In staying consistent with "no defensive players on offense" this package cannot be used.
-- WR at HB - in some sets the #1 WR can be subbed in as a HB...but not in the NDL. Smile

I have Arkansas, and used him as my starting QB last year. Are you saying I can use him this year as well?

Twistanutz22 wrote:I have Arkansas, and used him as my starting QB last year. Are you saying I can use him this year as well?

According to how the rule is written right now any player with 70+ THP can be a back-up. You might want to check with admin and get "BACK UP" clarified since they have it written in all caps. That makes it seem like they wrote it where he could be used sparingly but not as the starter.

Thanks for all the hardwork guys - it's greatly appreciated.

I noticed with the VT roster a couple liberties were taken with guys that are IN the game but no longer on the team (i.e. RB#20 is Michael Holmes - not Daniel Dyer)

None the less, it's not a big deal as the sum of all parts is incredible. I have no idea how any of us played this game w/o names

Twistanutz22 wrote:I have Arkansas, and used him as my starting QB last year. Are you saying I can use him this year as well?

As an injury replacement third stringer, sure. As a "he's my 'backup' but I'm going to sub him into packages", no. He's no longer a QB.

Ok, thanks for the clarification jsence. I'm actually very happy with with my starter, Brandon Allen. He's a passer that can run... Exactly what I prefer. If Mitchell were available, I'd use him in certain packages.. But I'll just be leaving him at WR

Twistanutz22 wrote:He's a passer that can run... Exactly what I prefer.

Twistanutz22 =

Just bustin your balls....

WJ5811 wrote:

razorback44 wrote:

The_Niddler wrote:razor, I ask the same question again....is this EA's doing?
If you do not load those rosters, is he still setup that way?

If EA is who messed it up, then there is not much we or anyone can do about that.

It's definitely EA's fault as he is actually not even on the team anymore. He transferred to NC State after getting beat out for the starting QB job by Brandon Allen during spring practice.

He will revert back to a WR when an NDL game is actually played with them.

My concern about that is with his skills at QB he is currently listed as the #1 QB for Arkansas however he will actually be a WR anand Brandon Allen is the starter. What if someone picks Arkansas thinking they will have him at QB when in reality they can't do that because he is actually WR #17 on the game?

According to the rules he could be used as a back-up QB.

SUBSTITUTIONS:
QB: QB. (Any player with a 70+ in THP may be a BACK-UP)
HB: HB
FB: FB, HB
WR: WR
TE: TE, FB
OL: OL
DL: DL
LB: LB, DL
CB: CB, S
S: S, CB, LB

--RBs will no longer be allowed to play FB regardless of their blocking numbers, packaging allows for two tailbacks to be on the field at the same time..
--No offensive players on Defense and vice versa.
--The #1 and #2 overall WRs must be used in the #1 and/or #2 positions. Placing a quality receiver down on your depth chart to take advantage of matchups is unacceptable.

PACKAGES:
With regards to the above three bulleted items there will now be a slight limitation of packages. ALL packages are available to use and are "fair game" with these 3 exceptions.
-- #1 WR CANNOT be moved into the slot. There are about a dozen offensive formations that allow you #1 WR to be moved to the slot. The ONLY defensive formation that allows you to move your #1 CB into the slot is nickel. This is not equitable and therefore not allowed.
-- CB 5 Wide - in the 5-wide sets there is a package that allows for a CB to line up at WR. In staying consistent with "no defensive players on offense" this package cannot be used.
-- WR at HB - in some sets the #1 WR can be subbed in as a HB...but not in the NDL. Smile

Let's take some of the heat off Twist and move to a slightly different situation...

A team that shall not be named but a certain someone is hoping does not go 1-8 has a really jacked up default roster.

At WR Drew Dileo, the second best receiver based on OVR is placed 4th/5th on the default depth chart. Only auto reordering places Dileo at the #2 spot...and doing that bumps the default #2 down to the slot. Whats the move to go here? Do the default #1 and #2 have to stay put or is it based on OVR thus meaning whoever has this team has to autoreorder before an offensive snap.

Also, a WR is placed on the default depth chart as the 4th CB. Teams a mess! Everyone should stay away!

Oh Niddler, you rascal you

Twistanutz22 wrote:

Oh Niddler, you rascal you

Just playing around.

Twistanutz22 wrote:Ok, thanks for the clarification jsence. I'm actually very happy with with my starter, Brandon Allen. He's a passer that can run... Exactly what I prefer. If Mitchell were available, I'd use him in certain packages.. But I'll just be leaving him at WR

I could be wrong, I'd clarify maybe w Buckeye....but that's the way I've always understood the rule. I encountered the same thing w Randall Cobb when I'd play games w UK in other leagues, and I just left him at WR. Now that said, you can always run a Wildcat formation and sub him in since it's acceptable to have a WR/HB as the "QB" in the Wildcat, and get some diversity that way.