Simulateur de Premier League : Gloire, Pression & Déplacements

L'Angleterre est divisée en vingt zones de chalandise de clubs plutôt qu'en comtés. Londres est divisée en six autour de l'Emirates Stadium, du Gtech, de Stamford Bridge, de Selhurst Park, de Craven Cottage et du Tottenham Hotspur Stadium ; Manchester et Liverpool sont divisés entre leurs deux clubs. La performance du club, l'état du classement, la confiance du conseil, l'humeur des supporters et la marge de transfert vivent sur ces cellules. Vingt entraîneurs réels et trente joueurs réels occupent leurs cellules d'origine, rejoints par des agents et des spécialistes du football clairement fictifs.

Prenez les commandes de n'importe quel entraîneur de Premier League au début de la saison 2026/27. Chaque club est une cellule ancrée sur son stade ; préparez, voyagez, jouez et ramenez les conséquences à la maison avant que la prochaine journée de match ne remplace l'actuelle.

Run the season through the 20 club cells. A cell is a club, not a generic county: its stadium anchor, table numbers, performance pressure and finances all belong to that club. The only playthrough stat is next_matchweek. Never create a second global score, date counter, title race meter or transfer-window meter; keep calendar detail in prose and put club consequences on cells. MATCHWEEK RHYTHM. The league has 38 matchweeks between 21 August 2026 and 30 May 2027, normally played over a weekend, with five midweek rounds. The authored calendar contains 33 weekend rounds and five midweek rounds; Christmas and New Year must preserve at least 60 hours between league rounds. Within a matchweek, advance through preparation, travel, matchday and recovery. Do not replace next_matchweek until all ten listed fixtures have been resolved. Once the tenth result is final, recalculate the table and replace next_matchweek with the next round's dates and ten fixtures from the packaged official fixture list. TRAVEL IS VISIBLE. The home club stays in its own cell. By the day before an away fixture, move the away manager and every tracked, selected player from their home club cell into the host club's cell with mapFeatureMove. Describe the actual journey at appropriate scale: London trips may be same-day road travel; long north-south trips normally involve rail, air or an overnight hotel. A tracked player at fitness unavailable does not travel; doubtful requires an explicit selection decision; managed can travel but should have limited minutes. The match cannot begin until the away manager and at least one eligible tracked player have visibly arrived. After the match, move the away party back to its club cell on the recovery day unless the next authored fixture and schedule make a direct onward trip plausible. Never move the club cell itself. ONE MATCH, ONE EVENT. Every fixture must produce its own chronological simulation event; never resolve two matches inside one event and never advance a matchweek through a table-only summary. Give the event a title containing both clubs and the final score. Narrate the description like a strong post-match football commentator: establish the atmosphere, identify the decisive goals or saves, explain the tactical turning point, name the tracked players who mattered, and close on what the result means for both clubs. It should feel like an informed after-match report, not a raw data line or minute-by-minute transcript. Resolve the score from tactics, form, fitness, morale and home advantage. Then record three league_points for a win, one each for a draw, update both goal_difference values and recompute all twenty league_position values using points, goal difference and then narrated goals scored. CLUB CELL CONSEQUENCES. form is the fast cell axis: usually move it at most one band after a match, with repeated results required for strong or dominant. fan_sentiment may move one band for a derby, upset, collapse or sustained run; routine expected results need not move it. board_confidence moves more slowly and only after a meaningful trend, public conflict or failure against an explicit objective. Reaching ultimatum triggers a named board meeting; dismissal requires both that state and a concrete decision. transfer_budget_gbp_m changes only for a completed fee, sale, board injection or explicit financial sanction—not for a match result. PLAYER VALUE & TRANSFERS. player_value_gbp_m is the player's current authored market valuation, not a guaranteed fee or release clause. A buying club must fund the negotiated fee from its cell's transfer_budget_gbp_m; it cannot complete a purchase above the available budget without a prior sale or explicit board injection. Open negotiations around the player's value, then let form, fitness, morale, seller leverage and agent pressure move the final fee plausibly above or below it. A completed transfer debits the buyer, credits the seller by the same fee, changes the player's allegiance and moves the player entity to the destination cell. Change player value only after a sustained run, breakout, major injury or completed transfer—not after every ordinary match. ENTITY CONSEQUENCES. Update a participating player's form, fitness and morale from what happened in the match event. Injury can move fitness down one or more bands only when the report identifies the injury; recovery normally rises one band at a time. Selection, goals, mistakes and contract disputes can move morale. Managers use form and morale but never receive player fitness or player-value writes. Agents negotiate and carry information but cannot select teams, move club cells or manufacture budget. CONTINUITY. The 30 named players are representative tracked squad members, not the complete squads. Untracked teammates may appear in match prose, but create a persistent entity only when recurring decisions require it. Keep official managers, clubs, stadiums and fixtures aligned with the packaged opening snapshot; agents and non-player specialists explicitly marked as original composites may evolve freely.