TF: After Midnight - Description/Rules/Records

After Midnight – Description & Rules
Dynasty Description
TF: After Midnight was created to allow TSO members with jobs/families who live on the west coast or have unusual work schedules to participate in a premier league that fits that demographic. For NCAA 2014, the league is using the SEC and ACC.
The league commissioner is recchem2000, who can be reached via pm with any questions/concerns.
League Roster
Recchem2000 – Alabama
Dru50 - LSU
Jayrah – Ole Miss
Whygodwhy1111 – Georgia Tech
G Money - Georgia
Bringbackjimmy - Texas A&M
Wyrmreaver - Notre Dame
Mexirican35 - Clemson
Ken Welsch - Virginia
Kapono – Florida St
SatansAngel1104 – Florida
Boom29 - Virginia Tech
Forum Participation
As this is a premier dynasty, forum participation is not only encouraged, it is mandatory. At a minimum, each member will be expected to participate in league discussions regarding game results, recruiting, conference races, individual awards and other accomplishments. Game summaries on CPU games may be limited to the basics (score, significant statistics), but the winner of each user vs user matchup will be expected to post a more thorough game recap, including trends noted during the game and key moments that impacted the final result.
Lack of participation on the forum will not be allowed, and will result in removal from the dynasty if it becomes an ongoing problem.
Difficulty Settings & Sliders
Game Difficulty – Offense (Heisman), Defense (All American)
Sliders – The sliders will be adjusted in each offseason, as deemed necessary by the league commissioner.
Advance Schedule
The dynasty will advance as quickly as reasonably possible. Each member is expected to make their games in this dynasty their NCAA priority, understanding that we all have lives and work/family responsibilities that take precedence over a video game. Members are expected to be available to play user vs. user games during the hours of 9pm to midnight PST on weeknights. The advance schedule will generally work towards an expected advance time of 11pm PST on the deadline day.
Coaches will generally be expected to play CPU games within 24 hours of the weekly advance, and the expectation will be that user vs. user matchups will be scheduled within a 48 hour window. It is incumbent on each user to contact the commissioner regarding any scheduling issues as soon as possible, and it is our expectation that user vs. user matchups can and should be scheduled prior to the weeks advance (the user vs. user game schedules for each week will be posted prior to each advance). If all games for a given week have been played, we will generally not wait for an individual to perform their recruiting prior to the week’s advance (although the commissioner will attempt to contact the individual to confirm the recruiting is done and allow a reasonable amount of time to perform recruiting).
Extensions of time will not be permitted generally for CPU games, and will be granted in some instances for extenuating circumstance for user vs. user matchups. Recchem will have final say regarding user games that cannot be scheduled, in order to determine if one user will play the CPU or if the game will be simmed, which will be determined on a case-by-case basis.
If a user will be out of town or unavailable for more than 2-3 days, please post this in the ‘Vacation/Absence’ thread in the forum as soon as possible. Substitutes or stand-in’s are allowed to assist you with playing CPU games and recruiting while you are away, however the user will be on AP for any user vs. user matchups during the absence. Generally, we will not hold up the advance schedule due to absence issues.
Offseasons will generally be scheduled for one evening as soon as reasonably possible following the conclusion of the season. However, if at least 50% of the group is not available for an offseason night during the week, we will likely advance 1 stage every 12 hours until the weekend and complete the rest on the first evening available. Substitutes are allowed and encouraged if you are unable to attend a scheduled offseason night.
Depth Chart/Redshirting Players
Coaches should be realistic in the setting of their depth chart and/or in redshirting players. In real life, highly ranked/recruited freshmen often play in the first season on campus, and similarly they should do so in our league. If you have an incoming freshman who would crack the 2-deep roster on your team based on OVR rating, they should be included in your depth chart and not redshirted without specific approval from the commissioner.
Additionally, your depth chart should generally follow your players OVR ratings. Use common sense and any questions should be discussed with the commissioner.
Recruiting Restrictions
In NCAA 14 the only restriction is that you should not recruit to over 73 players on your roster, although this may be adjusted during the cycle based upon the new recruiting system. In the offseason, any necessary cuts must be made from the incoming class of recruits.
Players Leaving
Players projected to be 1st, 2nd or 3rd round draft picks may not be swayed. Any others may be swayed based upon coach's prerogative.
Position Changes
The following rules apply for changing a players position in the offseason OR placing a player at a different position during the season (including through the use of formation subs). Specific formations such as the 2-4-5 which place OLB’s at DE are still acceptable even if the player (such as an OLB) would not meet the pre-requisites to play in those positions. Additionally, recruits that come in at a specific position may stay at that position even if they do not meet the below criteria.
QB – THP must be 70 or above (this applies to playing QB in non-wildcat based packages).
HB – No restrictions.
FB – Player must be under 6’3”, weigh at least 220lbs and have a speed of 86 or lower.
WR – No restrictions.
TE – Player must be 6’1” or taller, weigh at least 220lbs and have a speed of 86 or lower.
OL – No restrictions.
DE – Player must be 6’1” or taller, weigh at least 225lbs and have a speed of 82 or lower.
DT – Player must weigh at least 265 lbs and have a speed of 75 or lower.
OLB – Player must weigh at least 220lbs and have a speed of 86 or lower.
MLB – Player must weigh at least 230lbs and have a speed of 84 or lower.
CB/S – No restrictions.
K/P – No restrictions.
Any questions should be directed to the commissioner prior to changing a players position.
Gameplay Rules – General
Use of headsets – While some may not like being on the headset while playing, it is strongly recommend being on the microphone for user vs. user games. Being able to talk through issues in real time during the game is much more efficient than trying to type out questions/answers, and a bit of friendly trash talk is a great way to build up camaraderie with your dynasty mates. The easiest way to avoid game play arguments is to have a relationship with the guy on the other controller beyond posting on the forum.
Resolution of Issues – The hope is that everyone is mature enough to resolve any gameplay issues between each other during the game, but if that isn’t possible, all gameplay issues should be brought up to the commissioner via pm. Please include specifics about what the problem is, as well as video’s/highlights if possible. Arguing on the board about gameplay issues is discouraged.
Sportsmanship – Running up the score in CPU games or on your opponent in user vs. user games will not be tolerated, nor will general douchebaggery on the forums towards the other participants in the dynasty. If you are up 4 TD’s in the 2nd half of a game, take your foot off the gas a bit and run some clock.
Playbooks – Everyone will set their offensive and defensive playbooks by their 2nd user vs. user matchup. Once chosen, they can’t be changed until the following season. The 'multiple' defensive playbook is not allowed.
Custom Playbooks – The use of offensive custom playbooks will be allowed, so long as the formations/plays selected are in-line with a realistic game plan. Defensive custom playbooks are not allowed. All playbooks must be posted each season prior to your first user game, and once posted they cannot be changed until the following year.
Play Calling –Each person should be mix up their offensive and defensive formations and plays throughout the game. This doesn’t mean if you prefer man defense or want to structure your offense around the power-O running plays, you can’t do so. Just don’t run man cover 2 zone every play, and don’t run the same power-O play from the same formation 3-4 times in a row. Explore the playbook you’ve chosen and try and be diverse.
Scores & Statistics vs. the CPU – There will be a hard scoring cap of 70 points in games vs. the CPU, going above this amount will result in your game result being tossed out and a sim loss being posted to your record. The one exception to this is if you are involved in a shootout vs. the CPU you may exceed 60 points only if the final score is no more than a 2 score margin (10-14 points).
Additionally, running up statistics in CPU games won’t be tolerated. If you are winning by 28+ points in the 2nd half of a game, your starters should be on the bench. Starters scoring points in the 2nd half of a blowout will be benched for 1 or more future games, depending on the severity of the infraction. Likewise, scoring with your starters in the final 1-2 minutes of a game that is decided is not allowed. You have the ability to run the ball and chew clock, use it.
Game Plan Adjustments – Game play features such as aggressive/conservative settings and run/pass commit will be allowed, so long as they are used in game situations that would be realistic. In other words, leaving aggressive ‘jump the snap’ on all game is not OK, but turning it on for your opponents 2 minute drill when you know they are passing on every play would be allowed. The only exception is the conservative features on offense, which may be used at any time at the discretion of the coach.
Gameplay Rules Video

Gameplay Rules – Offense
Going on 4th down – Coaches should kick on 4th down in accordance with realistic gameplay; however there are certain circumstances where going for it on 4th down is allowable, see below:

• If you are behind 3 or more TD’s in the 3rd quarter or 2 or more TD’s in the 4th quarter, going for it on 4th down is allowed at any time.
• If you are losing with less than 3 minutes to play in the game, going for it on 4th down is allowed at any time.
• If you have 4th and less than a yard from inside the 50 yard line, going for it on 4th down is allowed at any point in the game.
• If you have a kicker with low kick power, you may go for it on 4th down from the 40 yard line in at any point in the game. Issues such as this should be communicated to your opponents in advance of the game so that they are aware.

Discuss any 4th down attempts you feel are questionable with your opponent via chat during the game to avoid disagreements.
Motion – Motioning backs and receivers is allowed, however if your opponent calls an audible during the motion you should wait a reasonable amount of time (a second or two) to allow the defense to reset prior to snapping the ball. Auto-motion plays are always allowed.
No-Huddle Offenses – These will be allowed if used in a sim fashion. This means that after plays that are for no gain or lost yards, the team should huddle. Additionally, the team should huddle after any incomplete passes. The offense must also allow the defense adequate time to call a play prior to snapping the next play.
Play Clocks – Players should attempt to select and call their plays in a reasonable amount of time. Players should not be ‘chewing clock’ or intentionally running down the play clock except in late game situations (last 2-3 minutes of each half). If a game is a blowout and both parties agree, the ‘chew clock’ feature may be implemented earlier in the game.
Play Action Passes – These plays should not be used in 3rd and long situations (6+ yards), unless you are running a fleXbox One offense, in which case play action may be utilized in 3rd and long.
QB Dropbacks –Purposefully dropping too far back in the pocket to avoid pressure during regular passing plays is not allowed. Defensive AI doesn't take into account how far back in the pocket the QB is, allowing for wide open out routes and passes into the flats.
A normal QB dropback would be considered to be no more than 7-10 yards at most from the initial line of scrimmage, in the case of an under center passing play. From the shotgun, dropbacks should be limited to 2-3 additional yards from the line of scrimmage, since the concept of the shotgun is that it is intended to remove the need for the QB to dropback on shorter routes and at most would only require 1-2 steps back for deeper routes to develop.
QB Scrambling –Unrealistic QB scrambling/sprinting is frowned upon on pass plays, including screens. Constantly dancing from sideline to sideline, running straight backwards or well behind the line of scrimmage without being under pressure is not realistic. This does not include option plays, designed QB runs or broken/pressured play situations.
Examples of unrealistic QB scrambling include:

• Sprinting backwards and/or to the sidelines off the play action fake. Rolling out with the QB is allowed, however this should be done without sprinting. Faulty AI on the defense causes defenders to break coverage nearly as soon as a QB leaves the pocket while sprinting and as we all know, QB’s throw on the run far more effectively in this game then they should.
• Sprinting backwards during a normal dropback is prohibited.
• Sprinting to the sidelines on a normal pass play that is not designed to be a rollout pass should only occur if there is pressure from the defense or you have waited 2-3 seconds in the pocket and no receivers are open. On a designed rollout pass, a normal rollout should be performed using the non-sprint QB running. If a QB sprints from the pocket, you should run the ball, not sprint out to throw the ball.
• Calling a normal pass play and then immediately running with the QB should be very rare. Using a 1-2 read system with an athletic quarterback and then running is considered sim as long as it is done within reason (i.e., not every single play). Quarterbacks that consistently average over 15 carries per game should be getting at least half of those carries via the option.

Two QB Offenses – If you have one passing QB and one running QB, you should limit the rotation of them. Yes, it has happened "some" in real life, but it doesn't translate well to the game. Mainly due to the fact that it is difficult for the defense to see who is jogging in and out of the huddle. For this reason, QB rotation should generally be used on a possession by possession basis. If you are on the mic with your opponent and agree to allow the two QB offenses in a different manner (such as informing your opponent prior to changing QB’s) that is also acceptable.
Wildcat Personnel Groupings – This should operate similar to the QB rotation. For playbooks that are designed to use a wildcat personnel grouping, offensive playcalling should realistically reflect this change. If the wildcat package does not include a QB, the wildcat personnel should stay on the field for a grouping of at least 3 plays and not switched in and out for individual plays here and there. If the QB remains on the field for the wildcat package this rule does not apply.
Options – Late pitches are not acceptable, if you succeed in a late pitch (even on accident) you should immediately run out of bounds for a loss or no gain. To clarify, a late pitch is one where your QB pitches the ball AFTER he has been hit by an opposing defender. A good pitch is where the pitch is made prior to contact with the QB. Violation of this rule will not be permitted, and any issues should be discussed with the commissioner.
Gameplay Rules – Defense
Matching Formations – Generally, the defense should be matching up personnel against the offensive package on the field. This means that while occasionally running your base defense against an opponent’s shotgun 4 wide packages is allowable, you should not be running a nickel/dime defense against a 2 TE set in a running situation.
Moving Players Before The Snap – On defense, shifting linebackers and the defensive line is permitted. However, if you manually move an individual defensive player before the snap you must control that player at the snap of the ball. This includes moving a player to cover an assignment. Constantly spreading or pinching your DL or LBs falls under the rules for mixing up your playcalling. Moving a defensive lineman off the line of scrimmage or more than one 'step' outside the OT is prohibited.
Blitzing – While blitzing is certainly a part of the game, please be realistic when calling blitzes. Any attempt to confuse the AI when blitzing is prohibited (ie. spreading your defensive line then shifting your LB's to create AI holes). This also falls under the rules for mixing up playcalling.
4-2-5/3-3-5 defenses – These defenses are allowed for use as a base defensive set.
1-5-5 defense – This defensive formation is currently allowed, but should not be used as your primary defensive formation.
Defensive Line Play – Coaches controlling defensive lineman must first engage an offensive lineman on any pass rush or running play. Use of the 'loop' technique is not permitted in any TF leagues (for those who are unaware, the 'Loop' refers to user controlling the DL and attempting to run yards around the OL, possibly with turbo involved). In general, when controlling a defensive lineman, you should always engage an opposing lineman and use rush moves to get clear. Additionally, use of the DE contain feature in the formation audible should be done in realistic fashion - in long yardage vs. a QB that is a definite running threat. Using the DE contain feature vs. a team that never runs their QB or using it in first and 10 situations or in conjunction with pinching the DL is not permitted.
Gameplay Rules – Special Teams
Fake Punts and FG’s – Any fake punt or field goal must follow the same rule used when going for it on fourth down. If you are allowed to go for it on 4th down in that situation, you can also fake the punt or field goal. Faking a FG or punt is part of the game and provides "the element of surprise," but please be realistic. These are utilized in NCAA but on a limited basis, so please keep that in mind.

BCS Champions
2011 - USC Trojans
2012 - CPU Oklahoma (due to EA screwjob 'glitch')
2013 - Penn State Nittany Lions(won in sim vs USC due to bowl game transfer failed glitch)
2014 - Penn State Nittany Lions
2015 - Ohio State Buckeyes
2016 - Stanford Cardinal

Conference Champions
Pac 12
2011 - USC Trojans
2012 - Stanford Cardinal
2013 - USC Trojans
2014 - USC Trojans
2015 - USC Trojans
2016 - Stanford Cardinal

B1G
2011 - Penn State Nittany Lions
2012 - Ohio State Buckeyes
2013 - Penn State Nittany Lions
2014 - Penn State Nittany Lions
2015 - Ohio State Buckeyes
2016 - Penn State Nittany Lions

Statistical Records (Recruited Players Only)
Passing yards - 2015 Penn State QB Derrick Lewis - 4,056 passing yards
Passing TD's - 2015 Penn State QB Derrick Lewis - 44 touchdowns
Passing INT's - 2016 Washington State QB Mark Johnson - 27 interceptions

Rushing yards - 2016 Stanford HB Matt Gibson - 1,755 rushing yards
Rushing TD's - 2016 Stanford HB Matt Gibson - 38 TDs

Receiving yards - 2015 USC WR Adrian Garcia - 1,402 receiving yards
Receiving TD's - 2015 Nebraska WR Jason Roberts / 2015 Penn State WR Ed Hall - 15 touchdowns

Tackles - 2016 Penn State MLB Evan Dixon - 107 total tackles
TFL - 2015 USC OLB Nate Ryan - 35 TFL
Sacks - 2016 Stanford LE Tyrone Jackson - 20 sacks
INT - 2016 Penn State MLB Evan Dixon - 9 interceptions
FF - 2016 Penn State MLB Evan Dixon - 8 forced fumbles

Freshman of the Year Award Winners:

2012 - Randall Green, MLB, Arizona Wildcats
2013 - Paris Miller, SS, USC Trojans
2014 - No winner

The description and rules have been updated for 2013. Everyone please read them when you can.

DirtycashDylan
Wyrmreaver
MexiRican35
whygodwhy1111
Jayrah
Cheez
SatansAngel1104
Boom29
Kapono

I suppose I should update these at some point

After Midnight

The rules thread has been updated per discussions with Zach.