V2 Match Engine: Get Ready…
📰 Match Engine V2 – What’s Coming and When
Something significant has been happening behind the scenes for a while now, and it’s close enough to share properly. The Soccer Supremos match engine is being rebuilt from the ground up – and implementation is essentially complete.
This is a plain-English summary of where things are, what’s changing, and what to expect over the coming weeks. No hype, no vague promises – just what’s actually in the build and when it goes live.
⚙️ Where Things Are Right Now
The last major piece of work landed this week, and testing is now under way. Over the next three weeks, V2 will be run through extensive end-to-end testing – entire leagues processed, outcomes checked, commentary reviewed, stats cross-referenced. The goal is to catch anything that needs adjusting before it touches live games.
The target go-live date is around the start of July. From that point, all turns will be processed by V2. There’ll be a settling period through July where I’ll be monitoring closely – if anything comes up, it’ll be addressed quickly.
💡 The testing so far has been positive. The foundations are solid and every change has been validated before landing. That said, no amount of internal testing matches real managers running real teams – which is exactly why the settling period matters.
🆚 V1 vs V2 – The Main Differences
The headline: V2 is a meaningful upgrade while keeping the game feeling familiar. You won’t feel like you’ve walked into something different. You will, however, start to notice that things make more sense – results follow what you’d expect more often, your decisions as a manager show up more clearly in the match stats.
Here’s the main table of changes, roughly in order of how noticeable they’ll be:
| Area | V1 (current) | V2 (coming) |
|---|---|---|
| Match outcome realism | Goals, cards, penalties and injuries could occasionally drift to extreme values | All match-stat ranges are actively bounded – outcomes feel grounded in the actual matchup |
| Result predictability | Weaker teams could occasionally upset much stronger sides for no clear reason | Results follow team strength, tactics, formation and aggression more consistently – upsets still happen, but with a reason behind them |
| Missed turnsheet penalty | Submitting no turnsheet had no in-match consequence | Skipping your turnsheet now visibly weakens your team for that match |
| Lazy tactic penalty | A bare-bones default setup played no differently from a fully-considered one | A default-only tactical setup produces a small but visible performance penalty |
| Aggression and discipline | Yellow and red card distribution wasn’t tightly tied to how aggressively you played | Aggressive tactics produce visibly more cards; passive tactics produce fewer |
| Player physical attributes | Height and weight had little effect on match events | Height and weight now subtly influence challenges – taller players win more aerial duels, well-built players win more physical contests |
| Star strikers | First and second-choice strikers were picked with similar likelihood to score | Star strikers score more often, with form, experience and shooting skill all factored in |
| Penalty taker | Mostly used your designated taker, but could fall back to a random player | Always picks your designated taker when one is set; the goalkeeper is never used as fallback |
| Corner and throw-in takers | Picked at random from midfield or defence | Picked by passing skill and form, with side-of-pitch awareness |
| Auto-substitutions on injury | Could occasionally send on a wrong-position player | Always picks the most appropriate replacement; bench specialist preferred where available |
| Match predictions | Single confidence call per match | Dual-confidence reporting (tight and loose threshold) – shows how confident the engine actually was and how close the call was |
| Commentary variety | 455 commentary lines in rotation | 885 commentary lines – nearly double the variety, plus richer phrasing alternatives within each line |
| Penalty shootout commentary | Hardcoded phrases, limited variety | Fully templated with natural variation – every shootout reads differently |
🔍 The commentary count alone is worth noting – 455 lines across an entire season means repetition becomes noticeable. Nearly doubling that, plus adding wording variation within each line, should make a real difference to the reading experience week to week.
📅 Rollout Plan
| Phase | When | What happens |
|---|---|---|
| Testing | Now – next 3 weeks | Extensive end-to-end testing across multiple leagues. Nothing changes for managers. |
| Go-live | Around start of July | V2 becomes the live engine. All turns from this point are processed by V2. |
| Settling period | July (and beyond if needed) | Close monitoring. Quick fixes if anything comes up. Manager feedback welcome. |
| New features | August onwards | Once V2 is settled, new features start landing – V2’s structure makes them buildable in a way V1 never did. |
⚠️ V2 is not identical to V1. Results will play out differently in some matches – that’s intentional. The aim is for those differences to feel like improvements, not surprises. If something looks genuinely wrong during the settling period, get in touch.
🔮 What Comes After
V1 has done its job, but it’s been harder and harder to build new features on top of it. Things managers have been asking about – more tactical depth, conditional substitutions, formation logic, set-piece specialists – weren’t practical to build on the V1 foundation.
V2 changes that. The internals are cleaner, the calibration is tested, and the structure actually supports what I want to build next. Once the settling period is done, the pace of new features picks up significantly. Most of the V2 work has been foundational – rebuilding the engine properly so everything else becomes possible.
The backlog is long and the list is good. More on that once V2 is live and settled.
Responses