2.2 Auto Fill Depth Charts

[David Winter]

I'd have to check to confirm, but right now I believe I have it loading as RB1=Full Back, RB2=Half Back, RB3=3Back.
 
It's not terribly difficult to change that, but again, it's hard coded.

[Marauders]

Which RB would be the FB.....I would normally have different ratings choices for how I see FBs used.

 
Yes, a FB needs to block more than a HB.
 
Then again, a poor blocking HB, no matter how good a runner, can be benched.  See Adrian Peterson as a reference.

[David Winter]

Well then the proposed system breaks down automatically because you want to have different skills being applied to different players in the same position. The proposed system asks for obtaining the skills from the first team profile entry for that position. If the first profile entry is SPD & STR then thats what all your RB's will be sorted against. Your RB with good blocking skills could end up as the 3B (or even a non starter if you have more than 3RB's on your roster).

[Frank Brickowski]

Either i do not understand the way the team profiles work, or the team profiles are not working properly towards the auto fill depth chart.  I know i have two TE's/SBs on my depth chart.  The backup TE/SB beats the starting TE/SB on every rating, but is still the backup.  That is what i'm having trouble with.

[Frank Brickowski]

Keep in my mind on my team profile i have the first TE qualifications as "blocking and "catching"

[David Winter]

Frank can you send me your league so I can see what's going on. thanks.

[Hubbard]

Yes, I am saying ignore RB2 and 3 in the profile. The reason I say this is because if I want my best RB to have high SP and AG and he gets hurt, I don't want him to be replaced by a RB with high INT and HND.
In my mind the depth chart is more for injuries and fatigue substitutions. The formation view is more for situational subs such as a need for a RB with high HND skills in a spread formation.

[David Winter]

Hmm well the depth chart is more than just for injuries. It's how the game fills the starting positions for all formations. So while the system of ignoring the subsequent profile items might work for running backs where there's only one slot per position, I do not believe it would work for receivers where there are many slots per position.
 
So far I think the weighted system covers most of the basis but I'd like a few more people to weigh in.
 
thanks
David

[Marauders]

Perhaps if the first instance in the profile determined which skill attributes are weighted, it would work.
 
The Bold skill attributes are taken from the team profile.  What would the weight be? 2x?  If the program adds 1x the two profile skills to the hard coded attributes, it would be 2x for skills that are duplicated.  Obviously, adding 2x the attributes would be give a 3x multiplier to the profile skills selected.  How much push do we want those two selected skills to have over the other skills?  Remember here that the unused skills are not used in the hard coded skills.
 
RB = (SPDx2 + AGLx2 + STR + INT + END + DIS + BLK + CAT + HND)

WR = (SPDx2 + CATx2 + AGL + STR + INT + END + DIS + BLK + HND)

QB = (PSSx2 + PSAx2 + INT + PPR + SPD + AGL + STR + END + DIS + HND)

DB = (SPDx2 + COVx2 + AGL + STR + INT + END + DIS + CAT + HND)
 
On a side note, for most teams the highest rated RB would be the halfback rather than the fullback.

[David Winter]

you mean like this?

RB = (SPD + AGL + STR + INT + END + DIS + BLK + CAT + HND) + (Profile1 + Profile2)
WR = (SPD + CAT + AGL + STR + INT + END + DIS + BLK + HND)  + (Profile1 + Profile2)
QB = (PSS + PSA + INT + PPR + SPD + AGL + STR + END + DIS + HND) + (Profile1 + Profile2)
DB = (SPD + COV + AGL + STR + INT + END + DIS + CAT + HND)  + (Profile1 + Profile2)

Profile1 and Profile2 are the two skill choices from the first profile item for that position found. So this does one of two things. It either multiplies one of the existing hard coded values by 2 (because it's added twice) or it adds an additional skill that isn't normally included for that position.

BTW, PPR probably shouldn't be included in the hard coded values. There is no good or bad for pocket passer, it's more of a play style, than a quality of skill.

[jdhalfrack]

BTW, PPR probably shouldn't be included in the hard coded values. There is no good or bad for pocket passer, it's more of a play style, than a quality of skill.

Agreed. I don't include it in my OVERALL player ratings of QBs, either.

That's my two sense (as unimportant as it was in this setting [;)])

JD

[Marauders]

David Winter asked:

you mean like this?

RB = (SPD + AGL + STR + INT + END + DIS + BLK + CAT + HND) + (Profile1 + Profile2)
WR = (SPD + CAT + AGL + STR + INT + END + DIS + BLK + HND) + (Profile1 + Profile2)
QB = (PSS + PSA + INT + SPD + AGL + STR + END + DIS + HND) + (Profile1 + Profile2)
DB = (SPD + COV + AGL + STR + INT + END + DIS + CAT + BLA) + (Profile1 + Profile2)
LB = (SPD + COV + AGL + STR + INT + END + DIS + CAT + BLA) + (Profile1 + Profile2)
OL = (SPD + AGL + STR + INT + END + DIS + BLK) + (Profile1 + Profile2)
DL = (SPD + AGL + STR + INT + END + DIS + BLA) + (Profile1 + Profile2)
KI = (KST + KAC)
PU = (KST + KAC)

Profile1 and Profile2 are the two skill choices from the first profile item for that position found. So this does one of two things. It either multiplies one of the existing hard coded values by 2 (because it's added twice) or it adds an additional skill that isn't normally included for that position.

Yes, that is what I mean.

BTW, PPR probably shouldn't be included in the hard coded values. There is no good or bad for pocket passer, it's more of a play style, than a quality of skill.

I thought about that as I was writing that post. While I believe that a quarterback is better off staying in the pocket and getting his passes off, because yards per attempt are almost always much higher than yards per carry for a quarterback, it is not always the case, so it would likely be better to leave it out as a hard coded value. It also gives QB, WR, RB, DB, and LB positions all nine hard coded values.

On a side note: does DIS or INT play a part in the kicking game?

[Marauders]

BTW, PPR probably shouldn't be included in the hard coded values. There is no good or bad for pocket passer, it's more of a play style, than a quality of skill.

jdhalfrack stated: Agreed. I don't include it in my OVERALL player ratings of QBs, either.

That makes sense.

That's my two sense (as unimportant as it was in this setting)

Actually, this is a great place for feedback. Keep it coming.

I am unsure which two senses you are making reference to though. Perhaps sight and sound?

[:)]

[David Winter]

Okay well the proposal above is fairly straight forward to implement. Probably a couple of hours work at most.
 
So this solution combines the weighted proposal + the use the first profile item / position proposal. So everyone gets a little bit of what they're asking for [:)]
 
RB (SPD + AGL + STR + INT + END + DIS + BLK + CAT + HND) + (Profile1 + Profile2)
WR/TE-SB (SPD + CAT + AGL + STR + INT + END + DIS + BLK + HND) + (Profile1 + Profile2)
QB/HO (PSS + PSA + INT + SPD + AGL + STR + END + DIS + HND) + (Profile1 + Profile2)
DB (SPD + COV + AGL + STR + INT + END + DIS + CAT + BLA) + (Profile1 + Profile2)
LB/CM (SPD + COV + AGL + STR + INT + END + DIS + CAT + BLA) + (Profile1 + Profile2)
CT/OL/BL (SPD + AGL + STR + INT + END + DIS + BLK) + (Profile1 + Profile2)
DL (SPD + AGL + STR + INT + END + DIS + BLA) + (Profile1 + Profile2)
KI (KST + KAC)
PU (KST + KAC)
KR (SPD + AGL + HND + INT + END + DIS + CAT) + (Profile1 + Profile2) 
  

[David Winter]

Actually, this is a great place for feedback. Keep it coming.
I am unsure which two senses you are making reference to though. Perhaps sight and sound?

 
It's a new M Night Shyamalan movie; The 2nd Sense. Bruce Willis walks around sniffing out dead people... "I smell dead people."
 
[:D] LOL... sorry.. that had to be said.

[Marauders]

So this solution combines the weighted proposal + the use the first profile item / position proposal. So everyone gets a little bit of what they're asking for [:)]

 
I agree.
 
What I would like is some community feedback on if Profile1 & Profile2 should be added once or twice.  How much weight should they get?  In my opinion, having it weighted only once will put more well rounded players at the top of the depth chart, but I'd like to see what other Maximum Football players would like.

 

[Marauders]

ORIGINAL: David Winter

Actually, this is a great place for feedback. Keep it coming.
I am unsure which two senses you are making reference to though. Perhaps sight and sound?

It's a new M Night Shyamalan movie; The 2nd Sense. Bruce Willis walks around sniffing out dead people... "I smell dead people."

[:D]

With JD, it is likely sight and sound, because he is often traveling through another dimension, a dimension not only of sight and sound, but of mind. A journey into a wondrous land whose boundaries are that of imagination.

[elmerlee]

David, am I understanding that as things now work on the depth carts that your currently using ONLY the two skills listed in the team profile for a certain position to set the depth chart? I'm just trying to figure out how this works until you implement something.

[jdhalfrack]

I am unsure which two senses you are making reference to though. Perhaps sight and sound?

Damnit... you know what I mean... CENTS... [;)]

I've been staring a a computer screen for like 65 straight hours... the editor is staring to give me fits.... [:(]

Oh well...

JD

[MjH]

ORIGINAL: David Winter

KI (KST + KAC)
PU (KST + KAC)

Would it be appropriate to add another value (+10, +20?) to the kicker and punter calculation depending on whether the player is designated as a kicker or a punter? If you just use the two kicking attributes, wouldn't one player end up doing all of the kicking?