How We Built a Lightning-Fast Forza Horizon 6 Map Explorer (And Why Most Gaming Wikis Get This Wrong)
Been tinkering with static site generation lately and thought I'd share what we learned building an interactive map tool for FH6. The game drops you into this massive open-world Mexico with hundreds of collectibles scattered everywhere — barn finds, XP boards, hidden cars. The official in-game map is... fine, but ALT+TAB-ing constantly during a drift zone run gets old fast.
What most players don't realize: the game's map data is surprisingly accessible through the API endpoints that power the companion app. We reverse-engineered the tile system (Web Mercator projection, nothing fancy) and built a static Next.js site that loads all 534 collectible locations without a single database query.
Performance tricks that actually mattered:
- Pre-generated static JSON files for each map region. No SSR overhead, just fetching a few KB of data
- Canvas-based rendering for the drift zone heatmaps instead of SVG markers (turns out rendering 200+ paths in SVG tanks mobile browsers)
- Service worker caching the tile images so repeat visits are basically instant
The coolest part? Forza stores vehicle stats in a structured format that's basically a flat CSV. We built a comparison tool that's honestly faster than the in-game autoshow — filter by weight distribution, horsepower class, even hidden grip coefficients that aren't shown in the UI.
Still trying to figure out how to handle the seasonal playlist data though — that stuff rotates weekly and the API structure changes more often than Horizon's weather. Might just cron-job a rebuild.
Full implementation details and the source for our car tuning calculator are on the project page if anyone's curious.
What game data have you tried to build tools around? Always looking for ideas on what to tackle next.
Top comments (0)