LEAGUE RULES

1.1: Commissioner's Role The Commissioner holds final executive authority over the league's operation, rule enforcement, and long-term direction. All staff, owners, management, and players operate under the Commissioner's oversight. 1.1.1: Hearing of Constitutional Amendment The Commissioner presides over any proposed amendment to this Constitution. Amendments may be proposed by the Board of Governors, League Directors, or Owners, but require the Commissioner's review and a Board of Governors vote (see 2.3) before taking effect. 1.1.2: Letter of Understanding Any new rule, policy change, or precedent-setting ruling not yet formalized in this Constitution must be issued as a Letter of Understanding, distributed to all Owners and Staff, until it is formally incorporated at the next Constitutional review. 1.1.3: Official Announcements All league-wide announcements (schedule changes, rule clarifications, disciplinary actions of league-wide relevance) are issued through the Commissioner's Office or the Media/Communications Officer on the Commissioner's authority. 1.1.4: Executive Orders The Commissioner may issue Executive Orders to address urgent situations not explicitly covered by this Constitution. Executive Orders remain in effect until reviewed by the Board of Governors, at which point they are ratified, amended, or repealed. 1.1.5: Staff Training The Commissioner is responsible for ensuring all league staff are onboarded and trained on their role's responsibilities, this Constitution, and league systems (transactions, discipline, stats). 1.2: Deputy Commissioners — League Directors 1.2.1: Management Assistance Deputy Commissioners assist Owners and Management with day-to-day operational questions, rule clarifications, and transaction guidance. 1.2.2: Procedural Enforcement Deputy Commissioners enforce league procedure (scheduling deadlines, transaction windows, lineup locks) on behalf of the Commissioner's Office. 1.2.3: Management Training Deputy Commissioners onboard new Owners/Management into league systems and expectations. 1.2.4: Role of the Deputy Commissioner Deputy Commissioners act with the Commissioner's authority in daily operations but defer to the Commissioner on any ruling involving suspension, franchise status, or Constitutional interpretation. 1.3: League Directors 1.3.1: League Management League Directors oversee the operation of an individual league within APHL (e.g., NHL, AHL, CHL Elite, CHL Pro, CHL Amateur), ensuring divisional rules, promotion/relegation, and scheduling are followed within their league. 1.4: Judicial Appeal Process and Player Representation Any party subject to a disciplinary ruling has the right to appeal (see Section Six, 6.7 and prior disciplinary procedures). Players may request representation from their Captain, GM, or a Board of Governors member during a formal hearing. 1.5: Conduct Commissioner's Office staff are held to the highest standard of neutrality. Any staff member found favoring a team or individual for personal reasons is subject to immediate review and possible removal by the Commissioner.

2.1: Role The Board of Governors is a representative body (drawn from Owners and/or senior staff) that reviews Constitutional amendments, ratifies Executive Orders, and serves as the final appeal body for league-wide disputes. 2.2: Suspensions The Board of Governors reviews any suspension appeal escalated beyond the Discipline Officer and Commissioner's Office (see Section Six). Board rulings on suspension appeals are final for the season. 2.3: Board of Governors Vote Constitutional amendments and Executive Order ratifications require a majority vote of the Board of Governors. Ties are broken by the Commissioner. 2.4: Board of Governors Selections Board members are selected by a combination of Owner vote and Commissioner appointment, serving fixed terms (recommended: one season, renewable). 2.5: Conduct Board members must recuse themselves from any vote or appeal directly involving their own team or close affiliates.

3.1: Committee Leader The Development Committee is led by a Committee Leader appointed by the Commissioner, responsible for player growth initiatives, onboarding, and league feedback loops. 3.2: Player Education The Development Committee produces onboarding materials, rule explainers, and gameplay guides to help new and existing players understand league systems (lineups, fatigue, salary cap basics as it applies to them). 3.3: Polling the Players for Their Vote The Development Committee runs periodic player polls/surveys on league satisfaction, rule proposals, and gameplay balance, reporting results to the Commissioner's Office and Board of Governors. 3.4: Conduct Development Committee members act as a neutral resource for players and must not use their position to advocate for a specific team's competitive interest.

4.1: Role Owners hold franchise rights to a team within APHL/CHL and are responsible for that team's overall direction, compliance, and management structure. 4.2: Roster Transactions Owners (or their designated Management/GM) are responsible for all roster transactions: trades, waivers, call-ups, and draft activity, in compliance with salary cap and roster limit rules. 4.3: Compliance Owners must ensure their franchise complies with all league rules, deadlines, and Constitutional requirements, including those delegated to their Management staff. 4.4: Accountability Owners are accountable for the conduct of their Management and players. Repeated violations by a franchise's staff or roster may result in Owner-level review. 4.5: Management Owners may appoint Management (GM, Assistant GM, Coaching staff) to handle day-to-day team operations, as defined in Section Five. 4.6: Management Office Each franchise must maintain an active Management Office (at minimum, one designated point of contact) reachable by league staff within the standard SLA. 4.7: Filing Management Appeals Owners may file an appeal on behalf of their franchise regarding any ruling affecting their team, following the same escalation process outlined in Section One (1.4). 4.8: Owner's Vote Owners hold voting rights on league-wide matters brought to a franchise vote (e.g., rule proposals, Board of Governors selection), one vote per franchise. 4.9: Owner Selections New Owners are selected/approved by the Commissioner's Office, with consideration of league fit, commitment level, and community standing. 4.10: Owner Commitment Owners are expected to remain active in league operations for the duration of their tenure. Extended inactivity without notice may result in franchise reassignment. 4.11: Conduct Owners are held to the league's general conduct standards and are expected to model professionalism for their franchise's staff and players.

5.1: Management Role Management (GMs, Assistant GMs, Coaching staff) handle the daily operational responsibilities of a franchise on behalf of the Owner: scheduling, lineups, roster management, and team leadership (captaincy appointments). 5.2: Management Contracts 5.2.1 NHL Management Management at the top competitive tier (NHL) is held to the highest activity and performance standards, given the tier's competitive weight in league standings and promotion/relegation implications. 5.2.2 AHL Management Management at the developmental tier (AHL) is expected to prioritize player development and roster rotation, preparing players for potential call-up to NHL-tier competition. 5.3: League Promotion Franchises and/or Management may be considered for promotion between tiers (e.g., CHL Amateur → CHL Pro → CHL Elite, or AHL → NHL) based on performance criteria and league capacity, as determined by League Directors. 5.4: League Intervention The league may intervene in a franchise's management (temporary league-appointed oversight) in cases of extended Owner/Management inactivity, repeated non-compliance, or franchise instability threatening league operations. 5.5: Management Removal Management may be removed by the Owner at their discretion, or by the Commissioner's Office in cases of serious misconduct or repeated non-compliance, following the standard review process. 5.6: Management Criteria Management appointees should demonstrate reliability, communication skills, and familiarity with league systems. Owners are encouraged to document their Management structure with the Commissioner's Office. 5.7: Conduct Management is held to the same conduct standards as Owners and league staff, including neutrality in disputes and professionalism toward players and opposing franchises.

6.1: Role Players are rostered members of a franchise expected to participate in scheduled games, follow league and game rules, and represent their team professionally. 6.2: Availability Players must submit weekly availability by the league deadline. Inaccurate availability (marking available and no-showing) is treated as an unexcused absence, not a scheduling issue. 6.3: In-Game Requirements Players must be present and ready at scheduled game times, follow assigned lineups/lines, and adhere to in-game conduct rules (no exploiting bugs, no targeting, no chat abuse). 6.4: Disconnection Process In the event of a mid-game disconnection, players must attempt immediate reconnection and notify their Captain/GM and the opposing team. Repeated or unresolved disconnection issues should be reported to Technical Admin for review; games affected by verified connection issues may be subject to replay or stat adjustment at Commissioner discretion. 6.5: Participation and Quitting Policy Players who intend to leave the league mid-season must notify their GM as early as possible. Unannounced departures leaving a roster short-handed may affect the player's standing for future league participation. 6.6: Ban Buy-outs A player serving a suspension or ban may petition for a buy-out (reduced suspension length in exchange for a defined penalty, e.g., forfeited roster spot priority or a probationary period) at the Discipline Officer's discretion, subject to Commissioner approval for season-length or permanent bans. 6.7: General Conduct Players are expected to follow all league and game rules, respect Captains/GMs/staff rulings, and pursue disputes through the proper escalation channel (Captain → GM → Discipline Officer → Commissioner → Board of Governors) rather than public conflict.

7.1: Founding a Franchise A new team is founded through the GM application. The applicant is the team's GM and brings five players from the GM's EASHL club, so a new team starts with six players: the GM plus five. 7.2: The Application The application gives the EASHL club name, the team city, the team name and abbreviation, and the five club players. Each of the five players is given a proposed salary and contract length. 7.3: Review and Approval Staff review every application and may adjust the salaries and contract lengths. An application cannot be approved unless every salary and contract is within the league minimum and maximum, every contract length is within the league limit, and the payroll of the five players fits under the salary cap. On approval the team is created, linked to its EASHL club, and the five players are signed to their contracts. 7.4: GM/Owner Has No Salary or Contract The GM/owner of a team has no salary and no contract and does not count against the salary cap. Every other player has a salary and a contract, including the Captain and Assistant Captains. Assistant GMs and coaches do not get this exemption. Contract offers cannot be made to a GM/owner, and staff cannot override a GM/owner's salary.

8.1: Staff Roles League staff share the Commissioner's workload. Each role has its own job and reports up the chain: - Assistant Commissioner: runs daily operations when the Head Commissioner is away, approves routine transactions within set limits, and escalates anything involving a conflict of interest or an unclear rule. - Discipline Officer: reviews incident reports, issues rulings under the suspension tiers, and keeps the public disciplinary log. Recuses from any case involving their own team. - Stats Commissioner: checks submitted stats against the EA data and screenshots before they are final and corrects problems before standings update. - Scheduling Coordinator: publishes the weekly slate, handles reschedule requests and tracks makeup games. - Trade/Waiver Analyst: checks salary cap compliance on every trade, clears waivers on schedule and flags roster limit problems. - Media/Communications Officer: posts recaps and announcements and keeps the public roster record, including captains. - Moderator: enforces conduct in Discord and the forum and passes serious cases to the Discipline Officer. - Technical Admin: keeps the site, bot and stat systems running and triages bug reports. 8.2: Staff Conduct and Appointment Staff must step aside from any ruling that involves their own team or close affiliates. Official actions are logged. Staff may not use their position for a competitive advantage, such as inside information on trades or waivers. Staff are appointed by the Head Commissioner, serve at will, and can be removed by the Head Commissioner. 8.3: Response Times Staff aim to meet these turnaround times: - GM messages and disputes: 24 hours - Trade approval or denial: 24 hours - Waivers: processed daily at a fixed time - Incident report review: 48 hours - Technical bug triage: 48 hours 8.4: Captain and Assistant Captain Every team has one Captain and at least one Assistant Captain. The Captain relays lineup and strategy from the GM to the roster, is the first stop for in-game disputes before they reach staff, and helps new and call-up players settle in. The Assistant Captain steps in when the Captain is away. The GM may change the Captain at any time but must tell the league, because captains appear on the public roster. A team with no Captain or Assistant Captain on file gets a warning, then a league-appointed interim captain. 8.5: Playing Time and Rotation GMs are expected to rotate the full active roster over the season. A healthy, available player who goes several games in a row without a lineup spot may file a playing-time grievance with the Discipline Officer. A grievance that is upheld gets a warning and review first, then a required rotation plan, then a review of the GM's standing. GMs should also manage two-line rotations with the fatigue system in mind rather than overplaying the top lines. 8.6: GM Scheduling and Lineup Duties GMs confirm game times with the opposing GM at least 48 hours ahead, submit reschedule requests with 24 hours notice, and make sure enough players are confirmed for each game. Lines must be in before the weekly lock and must reflect players who can actually play. A missed scheduling deadline is a warning, then loss of reschedule privileges for one cycle, then a League Council review. A late lineup is a warning, then an automatic lineup applied by staff, then a review of the GM's standing.

1.1: Availability All players must submit their availability for the upcoming week's schedule by the league's weekly deadline (set by the Scheduling Coordinator). Availability submissions are binding — marking "available" and then failing to show is treated as an unexcused absence under Section 6.2 of Article I, not a scheduling issue. 1.2: Right to be Scheduled Every active, available player has the right to be considered for a scheduled game slot during the week they submitted availability. GMs may not withhold a player from all scheduling consideration without cause; disputes go through the Article I escalation chain. 1.3: Right to Play Every rostered player who is available and scheduled has the right to actual in-game participation, subject to the lineup and fatigue/line-rotation system. A player scheduled for a game but held out entirely without explanation may file a grievance per Article I, Section Four (4.3). 1.4: Weekly Lines Lines must be submitted by the GM/Management before the weekly lock deadline. Locked lines are final for that week's games unless a roster change (injury, call-up, trade) requires an emergency edit, which must be approved by the Scheduling Coordinator or Assistant Commissioner before the affected game. 1.5: Restrictions and Exemptions Players may not be scheduled for more games in a week than the league's maximum game-night cap Exemptions to weekly scheduling requirements (illness, real-life conflict, approved leave of absence) must be submitted in advance and are reviewed by the GM and, if disputed, the Scheduling Coordinator Repeated exemption requests without documentation may trigger a roster status review

2.1: NHL and AHL Schedule The NHL and AHL each run independent schedules published at the start of the season by the League Director for that tier. Schedules are built around confirmed franchise availability windows and released before the season begins, with weekly matchups locked according to Section One. 2.2: Game Times Standard game times are set league-wide (e.g., a fixed weeknight window) to maximize player availability across both tiers. GMs may agree to alternate times within the same game night window, subject to Scheduling Coordinator approval per 1.5. 2.3: Holiday Game Schedule Games falling on major holidays are subject to a modified schedule (postponement or shifted game time) at the Commissioner's Office discretion. Holiday schedule changes are announced at least one week in advance via official league communication (Article I, 1.1.3).

3.1: EASHL Pro Clubs Set-Up 3.1.1: Team Uniforms Set-Up Each franchise must have its team uniform/kit finalized in-game (EASHL Pro Clubs) before the season begins, matching the franchise's registered team identity/colors on file with the league. 3.1.2: Team Arena/Rink Set-Up Franchises must have their in-game arena/rink setup finalized before the season begins. Changes mid-season require notice to the Scheduling Coordinator so opposing teams aren't caught off guard on game night. 3.2: Game Night Session Set-Up The home team (or designated host, per league convention) is responsible for creating the EASHL Pro Clubs session/lobby at the scheduled game time and inviting the away team's roster. 3.3: Game Night Timeline Players should be online and in the lobby at least 10–15 minutes before the scheduled puck drop The session should be created no later than the scheduled start time A grace period (recommended: 10–15 minutes) applies before a no-show/forfeit is considered (see Section Five) 3.3.1: Game Night Procedure Home team creates the session and invites the away roster Both teams confirm starting lineups match locked weekly lines Stats input responsibility is confirmed (Section 3.5) Game begins; any disconnection follows Section Four procedures Post-game, stats are submitted per Section 3.5 3.4: Server Selection (Beta) 3.4.1: How Does It Work? Server selection is a tool/process used to determine which platform region's servers a cross-platform or cross-region matchup will use, aiming to minimize connection issues (lag, disconnections) for both teams. 3.4.2: How Do I Use It? Home team (or the team designated by the matchup rules) initiates server selection before creating the session, following the current server selection tool/process published by the Technical Admin. 3.4.3: PSN NHL Server Selection Determination For NHL-tier matchups on PlayStation Network, server selection follows the priority order published by the league (e.g., home team's region unless a documented connection issue history dictates otherwise). 3.4.4: Xbox NHL and Xbox/PSN AHL Server Selection Determination For NHL-tier matchups on Xbox and all AHL-tier matchups (Xbox or PSN), server selection follows the equivalent published priority order for that platform/tier combination. Any disputes over server selection are resolved by the Technical Admin before the game proceeds. 3.5: Inputting Stats 3.5.1: Responsibility The home team is responsible for inputting/submitting game stats unless otherwise agreed upon by both GMs before the game, or unless the league's stat system designates responsibility automatically (e.g., OCR-based Stat Recorder). 3.5.2: Inputting Options Stats may be submitted via the league's OCR-based Stat Recorder system or, where unavailable, manual submission with screenshot/photo evidence per 3.5.3. 3.5.3: Required Stats and Pictures At minimum, final score, individual player stats, and goalie stats must be submitted with a clear screenshot of the in-game post-game stat screen(s) as verification. 3.5.4: Forfeit Games Stats Forfeited games are recorded per the forfeit procedure in Section Five (5.3.1) and do not require standard stat submission; the forfeit result is entered directly by league staff. 3.5.5: Computer Stats Any stats accumulated by an AI/computer-controlled player (per the AI replacement rules) are excluded from official leaderboards and individual player stat totals, consistent with Article I roster/fill-in rules. 3.5.6: Goalie Stats Goalie stats (saves, goals against, shutouts) must be submitted alongside skater stats and are subject to the same screenshot verification requirement. 3.5.7: Disconnection Stats Stats accrued before a verified disconnection count toward the player's season totals; stats for the portion of the game missed due to disconnection (covered by an AI or replacement) follow 3.5.5. 3.5.8: Player Replaced Mid-Game If a player is replaced mid-game (injury simulation, disconnection, or emergency substitution), the replacing player's stats for that game are tracked separately from the original player's stats, per the Stats Commissioner's reconciliation process.

4.1: A Player Loses Connection 4.1.1: Player Loses Connection Prior to the Game's Start If a player disconnects before puck drop, the game may be delayed for a reasonable grace period (recommended: 5–10 minutes) to allow reconnection before proceeding with an AI replacement or alternate roster player. 4.1.2: Player Loses Connection on the Opening Face-Off A disconnection occurring at the literal opening face-off may be treated as a false start; both teams may agree to restart the session. If teams cannot agree, the game proceeds with the affected player replaced per 4.1.3. 4.1.3: Player Loses Connection During a Game The disconnected player should attempt immediate reconnection. The game continues with an AI replacement or bench player filling in during the reconnection attempt, consistent with Article I, 6.4. 4.1.4: Unable to Return If a player cannot reconnect within the allotted window (recommended: 10 minutes of game time or real time), the game continues to completion with AI/replacement coverage for that player's position for the remainder of the game. 4.2: Goaltender or Multiple Player Disconnections 4.2.1: Goalie Disconnections A goaltender disconnection is treated with priority urgency given its impact on game integrity; the game may pause longer than the standard grace period (recommended: up to 10 minutes) to allow the goalie to reconnect before AI coverage takes over. 4.2.2: Multiple Player Disconnections If multiple players from the same team disconnect simultaneously (e.g., a host migration event or regional outage), both GMs should consult with the Technical Admin on whether the game should be replayed in full rather than continuing with heavy AI coverage. 4.3: Restitution Penalties A team found to have caused repeated or suspicious disconnections (manipulating connection to gain competitive advantage) is subject to review by the Discipline Officer and may face restitution penalties (e.g., game forfeiture, stat nullification) per Article I disciplinary tiers. 4.4: Coincidental Penalties Disconnections deemed coincidental (verified connection/ISP issues, platform-side errors) affecting both teams roughly equally do not result in penalties to either side; the game stands as played unless both GMs and league staff agree to a replay. 4.5: Restarting Process When a restart is warranted (per 4.1.2 or a Technical Admin determination), both teams must be ready to rejoin the session within a set window (recommended: 10 minutes) of the restart being called, or risk forfeit procedures under Section Five. 4.6: Additional Information All disconnection disputes not explicitly covered above are reviewed by the Technical Admin, with escalation to the Commissioner's Office for any dispute affecting game outcome or standings integrity.

5.1: Replays A game may be replayed in full when: (a) a verified technical failure prevented fair completion, (b) both GMs mutually agree, or (c) the Commissioner's Office rules a replay is necessary to preserve competitive integrity. Replay decisions are final once issued. 5.2: Reschedules Games may be rescheduled with a minimum of 24 hours' advance notice submitted to the Scheduling Coordinator, per Article I, Section Two (2.1) and Article IV (GM/Owner responsibilities). 5.2.1: Reschedule Restrictions Reschedule requests inside the 24-hour window require Scheduling Coordinator approval and are granted only for legitimate cause (documented emergency, platform-wide outage) A franchise is limited to a maximum number of reschedules per season (recommended: 2–3) before further requests require Commissioner's Office approval 5.3: Forfeits 5.3.1: Forfeit Procedure If a team fails to field a legal minimum roster within the grace period (Section 3.3), the game is declared a forfeit. The forfeiting team receives a loss; the opposing team is credited a win with a standard forfeit score (e.g., 1-0) unless a partial game was played, in which case the in-progress score may stand at the Commissioner's discretion. 5.3.2: Forfeit Restrictions A franchise that forfeits multiple games in a season is subject to review under Article IV (GM/Owner non-compliance) and may face additional discipline beyond the standard loss. 5.3.3: Gentlemen's Agreement Both GMs may mutually agree to alternate arrangements (partial roster play, friendly rescheduling) outside strict forfeit rules when both sides are amenable, provided the agreement is reported to the Scheduling Coordinator for the record.

6.1: Standings Tiebreaker Order When two or more franchises are tied in the standings (for playoff seeding, promotion/relegation cutoffs, or awards consideration), ties are broken in the following order: Head-to-head record between the tied franchises Goal differential Total goals scored Fewest forfeits/disciplinary infractions during the season Coin flip / Commissioner's Office determination, if still tied 6.2: Application Tiebreaker rules apply uniformly across NHL and AHL tiers, and are calculated by the Stats Commissioner ahead of any promotion/relegation (Article I, Section Seven) or playoff bracket announcement.

1.1: Sign-Ups Players register with the league through the official sign-up process, providing platform/gamertag information, position preference, and any prior league experience. Sign-ups are reviewed by the Development Committee and assigned per Section Two status definitions and Section Three (3.4) random assignment rules. 1.2: Salary Cap Each franchise operates under a league-wide salary cap, set per season by the Commissioner's Office. No franchise may exceed the cap at any point during the season, including at the moment a transaction is processed. 1.3: What Counts Towards the Salary Cap All active roster player contracts (Section 1.7) Retained salary from a prior trade (per 3.5.4/3.5.5) Any buy-out cap hits from Section 3.1.6 or 4.5 Players on Injured Reserve do not count against the active cap unless otherwise specified by IR rules (3.3.3) 1.4: Exceeding the Salary Cap A franchise may not complete any transaction (sign, trade, call-up) that would push it over the salary cap. Transactions attempted in violation are void; repeat attempts to circumvent the cap are reviewed by the Trade/Waiver Analyst and may result in disciplinary action under Article I, Section Five. 1.5: Roster — Positional Limits, Restrictions and Exceptions Each franchise must maintain positional minimums/maximums (e.g., minimum 2 goalies, positional balance across forward lines and defensive pairs) as defined by the current roster limit rules. Exceptions (e.g., temporary shortages due to injury) require Trade/Waiver Analyst approval. 1.6: Free Agent Bidding 1.6.1: Free Agent Bidding Process Unsigned/free agent players are made available for bidding at designated points in the season (season start, post-waiver clears). Franchises submit bids within cap space; the highest compliant bid wins the player's rights. 1.6.2: Bidding Restrictions Bids may not exceed available cap space A franchise may not retract a submitted bid once the bidding window closes Bidding windows and rules are set by the League Director for each tier 1.7: Player Contracts 1.7.1: Contract Distribution Contracts are assigned based on player status (Section Two), draft position (Section 4.7), or bidding result (1.6), following the league's salary scale. 1.7.2: Contract Restrictions Contract length and value must fall within league-defined bands for the player's status Contracts cannot be altered mid-season outside of an approved trade or re-sign window (Section Four) 1.8: Unrestricted and Restricted Free Agency (UFA/RFA) 1.8.1: Unrestricted Free Agent (UFA) A player whose contract has expired and who has met the league's minimum service/contract threshold (recommended: has completed a defined number of seasons or contracts under their current or any franchise) becomes an Unrestricted Free Agent. A UFA may sign with any franchise in the off-season free agency window, with no compensation owed to their previous franchise. Player who meet the UFA status after 10 Season played in APHL, CHL a player must meet the 10 seasons played as well. Players or League you play in can not combine season in both leagues. A player must play 10 seasons in 1 league to become a UFA in that League. 1.8.2: Restricted Free Agent (RFA) A player whose contract has expired but who has not yet met the minimum service/contract threshold for UFA status becomes a Restricted Free Agent. The player's most recent franchise retains the right of first refusal on any offer the player receives. 1.8.3: How RFA Offers Work Another franchise may submit an offer sheet to a RFA The player's original franchise has a defined window (recommended: 48–72 hours) to match the offer and retain the player at those terms If the original franchise declines to match, the player signs with the offering franchise, and the original franchise may be entitled to compensation (e.g., a draft pick) per league-defined compensation tiers based on the contract value 1.8.4: Qualifying Offers To retain RFA rights over a player heading into free agency, a franchise must extend a Qualifying Offer (a minimum-value contract offer) by the league's published deadline. Failing to extend a Qualifying Offer converts the player to a UFA. 1.8.5: UFA/RFA Restrictions A franchise cannot exceed the salary cap (1.2) when signing a UFA or matching an RFA offer sheet RFA offer sheets are subject to the same bidding restrictions as free agent bidding (1.6.2) where applicable A player's UFA/RFA status is tracked and confirmed by the Stats Commissioner ahead of each off-season free agency window

2.1: Understanding Player Statuses Every rostered player carries one status designation that determines contract eligibility, draft treatment, and movement rules. Statuses are assigned at sign-up or transition points (draft, promotion, re-sign) and tracked by the Stats Commissioner/league database. 2.2: Veteran Status (V) After 5 Seasons Players who have completed a defined minimum number of seasons in the league (recommended: 5 full season) and are no longer subject to entry-level contract restrictions. 2.3 Pro Status (P) Any Player who has played at least 1 full Season will gain the status of a Pro Player. 2.4: Amateur Status (A) Newly signed players without prior league draft history, typically entering via free agency or random assignment rather than the entry draft. 2.5: Prospect Status (PS) Drafted or developmental players held at the AHL tier (or a franchise's development pipeline) before being eligible for full-time NHL call-up. 2.6: Randomly Assigned (RA) Players placed onto a roster via the league's random assignment process (Section 3.4) rather than free agent bidding or the draft, typically used to fill roster gaps at season start. 2.7: Drafted Players (DP) Players selected in the NHL Entry Level Draft (Section 4.7), carrying draft-slot-based entry contract terms per the draft pick salary scale. Entry Level Draft: Players will have assigned Salary based on selection. #1 overall Pick in Draft will have a standard salary of 3.5 Million and 3 year contract

3.1: Seasonal Bans Structure 3.1.1: Seasonal Ban Requirements A seasonal ban is triggered when a player or Owner/Manager accumulates violations meeting the threshold defined in the strike system (3.1.7), separate from in-game suspensions under Article I. 3.1.2: Seasonal Ban Procedures The Discipline Officer reviews the violation history, issues the seasonal ban with documented reasoning, and logs it in the public disciplinary record. 3.1.3: Seasonal Ban Appeal (Players) Players may appeal a seasonal ban to the Commissioner's Office within 7 days of issuance, following the same appeal structure as standard suspensions (Article I, Section Six, 6.7) but escalating directly given the season-length severity. 3.1.4: Seasonal Ban Appeals (Owners, Managers) Owners/Managers appeal seasonal bans to the Board of Governors, given the franchise-level impact of a Management-level ban. 3.1.5: Seasonal Ban Punishment A seasonal ban removes the player/Manager from active participation for the remainder of the season, with roster/management coverage arranged per standard vacancy rules (Article IV, Section Seven). 3.1.6: Seasonal Ban Buy-outs A banned party may petition for a buy-out — a reduced ban length in exchange for a defined cap penalty (player) or probationary term (Manager/Owner) — subject to Discipline Officer and Commissioner approval. 3.1.7: Understanding the Strike System Violations accumulate as strikes on a rolling basis (recommended: strikes reset at season end unless tied to a permanent-ban-level offense). Strike thresholds trigger escalating consequences: warning → suspension → seasonal ban → permanent ban, consistent with Article I disciplinary tiers. 3.1.8: Definitions Strike: A logged violation counting toward the seasonal ban threshold Seasonal Ban: Removal from active participation for the remainder of the current season Buy-out: A negotiated reduction of a ban's length in exchange for a defined penalty 3.2: Waiver Wire and Send Downs 3.2.1: Placing a Player on Waivers A franchise may place a player on waivers to remove them from the active roster, making them available for claim by other franchises for a defined waiver period (recommended: 24–48 hours). 3.2.2: Claiming a Player Off Waivers Franchises with available cap space and roster room may submit a waiver claim; if multiple franchises claim the same player, priority follows inverse standings order (lowest-standing team gets priority) unless otherwise specified. 3.2.3: Waiver Wire Restrictions A player cannot be re-added to the same franchise's roster once claimed by another team Waiver claims must be cap-compliant at the time of the claim Franchises may be limited in the number of waiver claims per week 3.2.4: Waiver Exceptions, Exemptions, and Conditions for Conditional Waivers Certain player statuses (e.g., Prospect status players being sent to AHL) may be exempt from standard waivers ("conditional waivers"), following separate rules published by the League Director. 3.2.5: Transfer Wire The Transfer Wire is a separate mechanism for moving players between tiers (NHL ↔ AHL) or franchises outside of the standard waiver claim process, typically used for depth/roster balance moves rather than removing a player from a franchise's control. 3.2.6: Transfer Wire Restrictions Transfer Wire moves must remain cap-compliant and are subject to the same claim-priority rules as standard waivers unless the League Director specifies otherwise for a given transfer window. 3.2.7: Owner Player Contract Opt-Out An Owner may opt out of a specific player's contract (effectively releasing them) under defined conditions (e.g., buy-out window, cap relief need), following the process set in Section 4.5 (Retirement) and the buy-out framework in 3.1.6 where applicable. 3.3: Call Ups 3.3.1: Full-Time Call Ups A Prospect or AHL-tier player may be called up to the NHL roster on a full-time basis, subject to salary cap and roster limit compliance at the NHL level, and processed by the Trade/Waiver Analyst. 3.3.2: Full-Time Call Up Restrictions Full-time call-ups must be finalized before the next scheduled NHL game to count for that game's roster, and may be subject to a minimum time-served requirement at the sending tier before eligibility. 3.3.3: Requesting to be Placed on the Injured Reserve (IR) A franchise may request IR placement for a player unavailable due to a documented reason, providing cap relief per 1.3. IR requests are reviewed and approved by the Trade/Waiver Analyst or League Director. 3.3.4: Emergency Call Up (ECU) An Emergency Call Up allows a franchise to temporarily call up an AHL/Prospect player to cover a roster shortage (e.g., IR, sudden inactivity) ahead of an immediate game, without triggering standard call-up restrictions. 3.3.5: Emergency Call Up Restrictions ECUs are limited in duration (recommended: single game or short-term window) and the player must be returned to their original tier once the emergency need is resolved, unless converted to a Full-Time Call Up per standard process. 3.4: Random Assignment 3.4.1: Player Assignment New or unassigned players may be randomly assigned to a franchise with an open roster spot, typically used at season start to fill remaining vacancies after free agent bidding concludes. 3.4.2: Player Assignment Restrictions Random assignment respects cap space and positional limits; a franchise cannot be assigned a player that would push it over the cap or violate positional restrictions (1.5). 3.4.3: Player Rights Assignment In cases where a franchise holds "rights" to a player (e.g., prior draft rights, prior season rostering) without an active contract, those rights may be assigned/retained per league rules governing rights tracking. 3.4.4: Player Rights Assignment Restrictions Rights assignments expire after a defined period of inactivity (recommended: rights lapse if unsigned by [X] point in the following season) and are subject to League Director review on disputed claims. 3.5: Trading 3.5.1: Trade Deadline All trades must be submitted and approved before the league's published trade deadline for the season. No trades are processed after the deadline except league-approved exceptions (e.g., emergency roster necessity, reviewed by the Commissioner's Office). 3.5.2: Submitting Trades Both franchises must submit matching trade details (players, picks, retained salary) to the Trade/Waiver Analyst for cap compliance review before the trade is finalized. 3.5.3: Trade Restrictions Trades must be cap-compliant for both sides post-trade Players may be subject to a no-trade restriction under specific contract or status conditions A franchise may be limited in trades per week/season to prevent roster instability 3.5.4: Trade Compensation Criteria Trades must include reasonably equivalent value (players, picks, or retained salary) as judged by the Trade/Waiver Analyst; lopsided trades suspected of circumventing competitive balance may be flagged for review. 3.5.5: Trade Compensation Procedures Retained salary in a trade counts against the retaining franchise's cap per 1.3 for the duration specified in the trade terms. 3.5.6: League Trade Reversal The league may reverse a trade found to violate trade restrictions, involve collusion, or otherwise undermine competitive integrity, following review by the Trade/Waiver Analyst and ratification by the Commissioner's Office. 3.5.7: Player Trade Request A player may formally request a trade through their GM; the request does not obligate the franchise to trade the player but must be acknowledged and logged. 3.5.8: Trade Request Restrictions Repeated or disruptive trade requests may be reviewed by the Discipline Officer if they cross into general conduct violations (Article I, 6.7). 3.6: Management Seasonal Promotions Management (GM/Assistant GM/Coaching staff) may be promoted between franchises or tiers mid-season or at season end based on performance and league need, at the discretion of the Commissioner's Office and affected Owners.

4.1: Re-signs 4.1.1: Re-sign Restrictions Re-signs must occur within the designated off-season re-sign window and remain cap-compliant under next season's projected cap. Re-sign terms must follow the standard contract bands for the player's status (Section Two). 4.1.2: Sign and Trades A franchise may re-sign a player specifically to facilitate an immediate trade ("sign and trade"), subject to the same cap compliance and trade restriction rules as standard trades (3.5.3). 4.2: Off-Season Trades Trades may continue during the off-season under relaxed scheduling (no deadline pressure) but remain subject to the same cap compliance and compensation criteria as in-season trades. 4.3: Off-Season Transfer Wire The Transfer Wire (3.2.5) reopens during the off-season for tier-balance moves ahead of the next season's roster lock. 4.4: Off-Season Waiver Wire Waivers may be used in the off-season to clear roster spots ahead of free agency/the draft, following the same claim-priority rules as in-season waivers (3.2.2). 4.5: Retirement A player may retire from the league voluntarily, releasing their rights and removing their contract from any franchise's cap. Retired players may return in a future season through standard sign-up/free agency channels unless subject to a permanent ban. 4.6: Management Selections Off-season is the primary window for Owner appointment of new Management (GM/Assistant GM/Coaching staff) per Article I, Section Five, ahead of the next season's roster-building process. 4.7: NHL Entry Level Draft 4.7.1: Draft Eligibility New sign-ups without prior league contract history, and any players designated Amateur status (2.3) who have not been assigned via free agency, are eligible for the NHL Entry Level Draft. 4.7.2: Draft Process Draft order is set by inverse standings (or a league-defined draft lottery system) from the prior season. Franchises select eligible players in turn; selected players receive Drafted Player (DP) status and an entry contract per the draft pick salary scale (4.7.3). 4.7.3: Draft Pick Salary Scale Every drafted player is auto-signed to an entry-level contract the moment they're selected — no offer or acceptance step, unlike free agency (1.6) or UFA/RFA signings (1.8). Scale Structure: #1 overall pick: top-pick salary, set per league per season by the Commissioner's Office (default: $3,000,000) Last pick of the draft: league minimum salary (default: $500,000) Every pick in between: calculated by linear interpolation between the top-pick salary and the minimum salary, based on where that pick falls in the overall draft order Contract length: fixed number of years for all draft picks in a season (default: 3 years), regardless of round or pick position Total picks: rounds × number of teams in that league's draft (default: 5 rounds × 8 teams = 40 total picks) Salary Formula: For a given pick number P out of N total picks, with top salary T and minimum salary M: t = (P - 1) / (N - 1) Salary = T - (t × (T - M)) Salary is rounded to the nearest $1,000. Pick #1 always receives exactly the top-pick salary; the final pick always receives exactly the minimum salary; every pick in between scales smoothly along that line. Per-League Customization: The Commissioner's Office sets the top-pick salary independently for each league (CHL Elite, CHL Pro, CHL Amateur, and separately for the NHL Entry Level Draft) — e.g., Elite could run a higher top-pick salary than Amateur The minimum salary and contract length can likewise be set per league/season Once the top-pick salary, minimum salary, rounds, and team count are set for a season, the full pick-by-pick salary table is generated automatically — no manual entry required for individual picks Example (using defaults: $3,000,000 top / $500,000 min / 40 total picks): Pick Approx. Salary Contract Length 1 $3,000,000 3 years 10 ~$2,360,000 3 years 20 ~$1,680,000 3 years 30 ~$1,000,000 3 years 40 (last) $500,000 3 years Restrictions: Draft pick salaries must still be cap-compliant for the drafting franchise at the moment of assignment; a franchise cannot draft a player whose entry-level salary would push it over the cap Entry-level contracts assigned through the draft cannot be renegotiated until the player's contract expires and they enter free agency (Section One, 1.8) or re-signs (4.1)

1.1: Preamble This Rule Book governs conduct, gameplay, and dispute resolution across all APHL and CHL tiers (NHL, AHL, CHL Elite, CHL Pro, CHL Amateur). It works alongside Articles I–III of this Constitution; where a conflict arises, this Rule Book's judicial process governs how that conflict is resolved. 1.2: General Conduct All participants — Owners, Management, Staff, and Players — are expected to conduct themselves professionally and in good faith toward opponents, teammates, and league staff at all times, in-game, on the website/forum, and in official league Discord channels. 1.3: Jurisdiction This Rule Book applies to all league-sanctioned activity: scheduled games, official league communication channels, and any conduct that materially affects league operations, standings, or another participant's ability to compete fairly — regardless of the platform on which it occurs. 1.4: Complaint or Violation Disputes Any participant may file a formal complaint regarding a suspected rule violation. Disputes are resolved through the Judicial Process outlined in Section Two, not through public conflict or unilateral retaliation.

2.1: Understanding the Judicial Process The Judicial Process is the league's formal mechanism for investigating and ruling on complaints. It exists to ensure every ruling is evidence-based, consistently applied, and appealable — rather than left to informal or one-sided resolution. 2.2: Filing Formal Complaints 2.2.1: Complaint Categories Complaints are filed under one of the following categories: In-Game Conduct, Off-Field/Communication Conduct, Roster/Transaction Violation, Management/Owner Violation, or Technical/Disconnection Dispute. The category determines which staff role initially reviews it (Discipline Officer, Trade/Waiver Analyst, or Technical Admin). 2.2.2: Filing False Complaints Knowingly filing a false or bad-faith complaint is itself a conduct violation and may result in discipline against the complainant, up to and including the punishment tier the false complaint sought to impose on the accused party. 2.2.3: Providing Evidence Complaints must be submitted with supporting evidence (screenshots, clips, chat logs) wherever possible. Complaints lacking any evidence may still be reviewed but carry less weight and may be dismissed if unverifiable. 2.2.4: Viewing Ruling Decisions Finalized rulings are logged in the public disciplinary record (Article I, 1.1.3 / 4.3), though sensitive evidence (private communications, personal information) is redacted from the public view. 2.2.5: Judging Complaints Complaints are judged by the relevant staff role under 2.2.1, based on the preponderance of evidence available, and applying the punishment tiers defined in Article I and this Article. 2.2.6: Violation Punishments Punishments scale by severity and repeat occurrence, ranging from a warning to a game suspension, seasonal ban, or permanent ban, consistent with the tiers established in Article I (Section Six) and Article III (3.1). 2.2.7: League Removal Policy A participant may be removed from the league entirely for severe or repeated violations (e.g., glitching for competitive advantage, harassment, collusion) as determined by the Commissioner's Office, following the standard judicial review process. 2.2.8: Capital Punishment Ban Policy "Capital punishment" bans — immediate, permanent removal without the standard tiered escalation — are reserved for the most severe violations (e.g., cheating/glitch exploitation for competitive gain, serious harassment, doxxing). These bans require Commissioner's Office authorization and are reviewable only by the Board of Governors. 2.2.9: Right to an Appeal Every ruling under this Article carries the right to appeal, following the escalation chain established in Article I (Section Six, 6.7) — except capital punishment bans, which escalate directly to the Board of Governors. 2.2.10: Time Frame for Serving a Punishment Punishments take effect immediately upon ruling unless a pending appeal explicitly stays the punishment (at the Commissioner's Office's discretion for borderline or high-impact rulings). 2.2.11: Public Complaints Airing a dispute publicly (forum, Discord, social media) before or instead of filing a formal complaint is discouraged and may itself be treated as a conduct violation if it constitutes harassment or disrupts league operations. 2.3: Standard of Participation All participants are expected to know and follow this Rule Book. "I didn't know the rule" is not, on its own, a valid defense against a ruling, though it may be considered as a mitigating factor for first-time, low-severity violations. 2.4: Staff Timeline for Complaint Rulings Staff are expected to issue an initial ruling on a filed complaint within 48–72 hours of submission, barring cases requiring extended evidence review. 2.5: Statute of Limitations Complaints must be filed within 7 days of the incident in question. Complaints filed outside this window may be declined unless the delay is justified (e.g., evidence only recently became available). 2.6: Withholding Information Any participant found to be withholding relevant evidence during a judicial review, once directly asked to provide it, may face additional discipline for obstruction, separate from the underlying complaint.

3.1: Pre-game EASHL Pro Club Set-Up in Private Game Set-Up All games must be created as private EASHL Pro Clubs matches with correct team/club settings (uniforms, arena, ruleset) matching league standards, per Article II (3.1). 3.2: Game Night Deadlines All game-night deadlines set in Article II (Section Three) are enforceable rules under this Article; missing them is treated as a rule violation subject to the judicial process, not just a scheduling note. 3.3: Server Selection Determination Server selection must follow the process defined in Article II (3.4). Deliberately manipulating or refusing server selection to gain a connection advantage is a rule violation. 3.4: Diving for the Puck Deliberately and repeatedly diving/sliding for the puck outside of normal gameplay attempts, in a manner intended to exploit game physics rather than make a legitimate play, is prohibited. 3.5: Self Board Play Deliberately using the boards to exploit puck physics or game mechanics in a way not intended by normal gameplay (as opposed to standard board-play strategy) is prohibited. 3.6: Ragging the Puck Excessive, prolonged puck-holding intended purely to run out the clock without making a competitive play — as opposed to legitimate offensive zone possession — may be reviewed as unsportsmanlike conduct if it disrupts fair competition, particularly in lopsided-score situations. 3.7: Goaltender Interference Deliberate contact with an opposing goaltender outside of incidental/legitimate net-front play is prohibited and may be reviewed for in-game penalty and, if repeated/egregious, disciplinary action. 3.8: Glitching Exploiting any bug, glitch, or unintended game mechanic for competitive advantage is strictly prohibited and is treated as one of the most serious in-game violations, up to capital punishment ban consideration (2.2.8) for deliberate, repeated, or match-altering use. 3.9: In-Game Loop Deliberately looping the same exploit-adjacent play pattern (offensive or defensive) to abuse an AI/game engine weakness rather than compete normally is treated as a glitching-adjacent violation under 3.8. 3.10: AI Player Stats Stats generated by an AI-controlled player (per Article I, 6.4 and Article II, 3.5.5) are excluded from official leaderboards and season totals; attempting to inflate personal stats via manipulated AI coverage is a violation. 3.11: Resolving Broken Rules During a Game 3.11.1: Procedures When a rule violation under this Section occurs mid-game, the affected team should document it (screenshot/clip) and continue play; formal resolution happens post-game via complaint filing (Section Two) rather than pausing the match, except where a glitch requires an immediate restart per Article II (4.5). 3.11.2: Goals A goal scored as a direct result of a rule violation (e.g., a glitch) may be nullified upon review and removed from the official score. 3.11.3: Penalties A missed or incorrectly applied in-game penalty related to a rule violation may be adjusted after the fact only insofar as it affects the recorded outcome/stats, not by replaying game time. 3.11.4: Possession Possession-based advantages gained through a rule violation are not retroactively reversible in-game but are documented as part of the violation record for judicial review. 3.12: Adjusting Stats After an In-Game Infraction 3.12.1: Goal Incident A goal confirmed to result from a rule violation is removed from both the final score and the individual stat lines of the players involved. 3.12.2: Penalty Incident Penalty minutes and related stats tied to a confirmed rule violation are corrected in the official record by the Stats Commissioner. 3.12.3: Possession Incident Possession-related stat anomalies tied to a confirmed violation are annotated in the record even where the underlying stat cannot be cleanly reversed.

4.1: Availability Players must submit accurate weekly availability per Article II (1.1). Falsifying availability is a rule violation distinct from a simple no-show. 4.2: No-Shows Failing to appear for a scheduled, confirmed game without prior notice is a rule violation subject to the suspension tiers in Article I and the strike system in Article III (3.1.7). 4.3: Maintaining an Active Console Account and APL User Profile Players must keep their console/platform account and APL site profile active and accurate (correct gamertag, contact info) throughout the season. Failure to do so may result in a player being deemed inactive/unreachable for roster purposes. 4.4: Demanding/Brokering a Trade Players may formally request a trade (Article III, 3.5.7) but may not publicly demand a trade, pressure a GM through repeated escalation, or attempt to broker their own trade terms with another franchise directly. Violations are reviewed as conduct issues. 4.5: Quitting the Team or League A player who quits mid-season without proper notice (Article I, 6.5) leaves their franchise short-handed and may face a review of their standing for future league participation, including a potential seasonal or permanent ban for repeated occurrences. 4.6: Ineligible Player Fielding a player who is suspended, banned, over a roster/positional limit, or otherwise ineligible under this Constitution is a rule violation against the fielding franchise, regardless of intent. 4.7: In-Game Communication Communication during games (voice/text chat) must remain within general conduct standards (1.2); harassment, slurs, or targeted abuse during gameplay is treated with the same severity as off-platform conduct violations. 4.8: Website Etiquette Forum and league website conduct (posts, comments, profile content) must follow the same general conduct standard as in-game communication. Spam, harassment, or disruptive posting is subject to Moderator and Discipline Officer review. 4.9: Second Tag Issues — Account Recovery Issues Players experiencing gamertag/account changes or recovery issues must notify the league promptly so their roster/profile record can be updated; failing to disclose a tag change that affects roster tracking may be treated as a compliance issue. 4.10: Conduct Unbecoming Any conduct — on or off platform — that reflects poorly on the league or another participant, even if not explicitly enumerated elsewhere in this Rule Book, may be reviewed under this general "conduct unbecoming" standard at the Discipline Officer's discretion. 4.11: Detrimental Act to the Organization Actions that materially harm a player's own franchise (e.g., deliberately underperforming, sabotaging team chemistry, leaking internal team communication) may be reviewed as a detrimental act, separate from general conduct violations. 4.12: Refusal to Play A player who is available, scheduled, and healthy but refuses to participate in a game without valid cause is treated as equivalent to a no-show (4.2) for disciplinary purposes.

5.1: Late Lines Submitting weekly lines after the lock deadline (Article II, 1.4) without an approved exception is a rule violation against the franchise's Management. 5.2: Invalid Roster Fielding a roster that violates positional limits, salary cap compliance, or eligibility rules (4.6) is a Management-level violation, regardless of which individual player caused the issue. 5.3: Circumvention or Falsifying Any of the Site's Systems, Forum, or Rules Attempting to manipulate, exploit, or falsify league systems (stat submission, cap tracking, forum records) is treated as one of the most serious Management-level violations, subject to League Removal Policy consideration (2.2.7). 5.4: Disclosure of Private Information Sharing another participant's private information (real name, personal contact details, platform account details beyond gamertag) without consent is strictly prohibited and may result in severe discipline up to permanent removal. 5.5: Player Rights Violation Interfering with a player's rights under this Constitution (e.g., denying a legitimate trade request review, withholding availability consideration without cause per Article II, 1.2) is a Management violation. 5.6: Player Tampering Contacting or attempting to recruit a player currently under contract to another franchise, outside of legitimate free agency/trade channels, is prohibited and reviewed as tampering. 5.7: Forfeits Repeated forfeits (Article II, 5.3) beyond the league's tolerance threshold are treated as a Management-level compliance issue subject to additional review under Article I (Section Five). 5.8: In-Game Stats Requirements Failing to submit required stats/screenshots per Article II (3.5) in a timely manner is a Management violation affecting league record-keeping. 5.9: Disconnection Procedures Management is responsible for ensuring their roster understands and follows disconnection procedures (Article II, Section Four); a pattern of disconnection-related disputes tied to one franchise may trigger Technical Admin review. 5.10: Waiver Violations 5.10.1: Claiming and Waiving Players Circumventing waiver claim priority (Article III, 3.2.2) or colluding with another franchise on a waiver claim/release is a rule violation. 5.10.2: Waiving an Inactive Player Placing a genuinely inactive/unreachable player on waivers to clear a roster spot is permitted, but must be accurately represented — falsely claiming a player is inactive to justify a waiver move made for other reasons is a violation of 5.3. 5.11: Making Transactions in "Bad Faith" Transactions structured primarily to circumvent the salary cap, tamper with competitive balance, or exploit a loophole rather than serve a legitimate roster purpose may be reviewed and reversed under Article III (3.5.6), with additional discipline for the Management involved. 5.12: Second Tag Issues Management failing to update or report a roster player's tag/account change (see 4.9) in a timely manner may be held responsible for resulting roster tracking errors. 5.13: Conduct Unbecoming Owners and Management are held to the same "conduct unbecoming" standard as players (4.10), with a higher expectation of professionalism given their leadership role within the franchise. 5.14: Ownership Annotations The Commissioner's Office maintains an internal annotation record for each Owner/Management team, logging rulings, warnings, and prior violations to inform future disciplinary decisions and franchise standing reviews.

This section is intentionally left for the Commissioner's Office to maintain and update directly, as banned X-Factors and illegal movement mechanics change with each game version/title update. 6.1: Banned X-Factors [To be updated by league staff] 6.2: Illegal Movement / Skill Moves [To be updated by league staff] 6.3: Enforcement [To be updated by league staff — e.g., how a violation here is reported, reviewed, and penalized, likely following the Section Two Judicial Process and Section Three in-game infraction handling] Section Seven: Prestige & Rankings This section applies league-wide, across both APHL and CHL. 7.1: Prestige System Each player earns and loses prestige points based on game results. Wins earn points, losses deduct points. The amount earned or lost is affected by the tier gap between opponents — beating a higher-tier player earns more, losing to a lower-tier player costs more. 7.2: Prestige Tiers There are 19 prestige tiers ranging from No Rank to Fire 1. Players need a minimum of 7 games played before their prestige tier is displayed. Tier advancement and demotion happen automatically based on a player's prestige score. 7.3: Season Reset Prestige scores may be subject to a soft reset at the start of each new season at Admin discretion. The reset brings scores closer to the midpoint rather than wiping them entirely.

These rules cover what happens when a player drops, a goalie disconnects, or a team quits during a league game. Stats are pulled from EA and checked against the screenshots both teams submit. 7.1: Who Gets Stats - Only players on a team's league roster earn stats. There are no guest players in any league. - EA may fill an empty spot with an AI or computer player. AI players never receive stats. - Every roster player's stats count in both a restarted game and its replay, as long as they belong to a human player. 7.2: A Skater Drops Out - 1st or 2nd period: the game is restarted so the player can return. The score and the time remaining are kept. - 3rd period: the game plays on without the player. No restart. 7.3: The Restart Procedure 1. The team of the player who disconnected quits the game first. EA then shows a DNF win for the other team. 2. Both teams start a new private game. 3. The teams run the clock down to the time that was remaining when the disconnect happened. Play resumes from that point with the same score. 4. Restarts are only allowed in the 1st or 2nd period. A DNF is not a final result. The game is restarted until it is completed with a final score and stats for the players. 7.4: A Goalie Disconnects - The goalie is the most important player in the game. If the goalie drops, EA ends the game automatically. - The league replays the game. - If the same goalie drops twice, there may be a connection problem. That team must get a replacement goalie from its roster. 7.5: Refusing to Restart (Forfeit) If a team refuses to restart a game, the result is an automatic forfeit: - The other team is awarded a 3-0 win. - No player stats are recorded for the forfeited game. - The team that quit and every active player on its roster take the largest prestige loss in the prestige system, and the promotion floor does not protect them. The other team and its active players receive a normal win. 7.6: Awarded Goals When a game ends in a DNF, EA may award the winner goals up to a 3-0 score. No player is credited with an awarded goal. 7.7: Screenshots - Both teams submit screenshots after every game, not just one. They are the backup in case EA did not register the stats correctly. - The EA data and the screenshots are compared. This stops a team from claiming goals that players do not show. - If a score or stat does not match, an admin reviews it before it is final. 7.8: Quick Reference

Situation	What happens
Skater drops in the 1st or 2nd period	Restart, same score and time remaining
Skater drops in the 3rd period	Game plays on without the player
Goalie disconnects	Game ends and is replayed
Same goalie drops twice	That team must use a replacement goalie from its roster
Team refuses to restart	Forfeit: 3-0 win for the other team, no stats, prestige penalty for the team that quit
DNF result in EA	Not final. Restart until the game is completed
Awarded goal on a DNF	Not credited to any player

8.1: Power Rankings Staff publish power rankings during the season. Every team is ranked by a formula built from the games played: season record (25%), recent form over the last five games (30%), goal difference per game (20%), strength of schedule (10%) and the team's prestige rating (15%). An overtime or shootout loss counts as part of a win in the record. Early in the season every team is pulled toward the middle so one game does not swing the table. Staff add a short note for each team and may move a team away from where the formula put it. Every move needs a recorded reason that league leadership can see. Arrows show how a team moved since the last published edition. Power rankings are opinion: they do not affect standings, seeding, playoffs, prestige or contracts. 8.2: Advanced Stats The Advanced Stats page shows shooting percentage, shots for and against, power play and penalty kill, time on attack, passing and faceoffs for teams, and shooting percentage, shot attempts, power play goals, faceoffs, takeaways and giveaways for skaters. The numbers come from the EA data and only count games that staff have applied or verified. Goals on this page are the goals credited to players. If EA awarded or added a goal, the total can differ from the official score by a goal or two. The official score and the standings always come from the result recorded by staff. Players are tracked by their EA account, so a trade or a gamertag change does not split their numbers. The skater leaderboard needs a minimum number of shots, set by staff. EA does not send shot locations, so there are no shot maps. 8.3: Goal Log and Game Summaries EA does not record when a goal was scored, so staff log the goals of each completed game: the scoring team, the period, the time, the scorer, up to two assists and the strength (even strength, power play, short handed, empty net or penalty shot). A team cannot have more goals logged than it scored. The Game Summaries page shows the log with the score by period. A game whose goals are not all logged is shown as a partial log, and the period totals may not add up to the final score until it is finished. Shootout goals are logged but are not part of the score by period. If a goal looks wrong, report it to league staff with a screenshot or clip. 8.4: Record Books The record books track team and player records (career, single game, goalie and rookie) and milestones every 100 in the main stat categories. Only players on a league roster count: guests and AI players never earn records. A traded player keeps the records he set with his old team until they are broken, and competes for his new team's records from the trade forward.

At the end of each season, Admin archives the season results including the champion, runner-up, award winners, final standings, and notable records. This information is permanently stored in the Hall of Fame.

Admin may write a season recap narrative that is published alongside the archived stats. Recaps may highlight key moments, standout performances, and season storylines.