2D football match viewer in PixiJS / Canvas — continuous 0–90 replay from event data (TypeScript)

Striker Path is a live football career game (web today, iOS in review). We need a standalone TypeScript match viewer that plays a full match from minute 0 to 90 with a running clock — continuous, accelerated, no cuts — in the cartoon comic style of SoccerStar. Think of it as a 2D replay engine that reads a match log and animates it. WHAT YOU BUILD A self-contained package (no framework, no backend) that mounts into a container element and exposes load(matchLog), play/pause/seek/setSpeed, and a few events. It draws: the pitch with both goals, 22 players as sprites, the ball, a camera that follows play, a live clock and scoreboard. Key moments (goal, card, save, offside) zoom or overlay WITHOUT cutting or fading. PixiJS (WebGL, canvas fallback) or plain Canvas 2D. 60 fps in a mobile WebView and on desktop. Deterministic: same log, same replay. THE DATA The viewer reads a positional stream: the ball and all 22 players every 500 ms of match time, who has the ball, the clock, plus a separate list of events (goal, card, save, offside, substitution) for overlays and the scoreboard. You interpolate between consecutive ticks, drive the camera and draw; you never decide where anyone goes — the simulation does. You get a sample file in exactly this format on day one (synthetic content, real shape) and a one-page contract describing it. WHAT YOU DON'T DO The match simulation, the artwork (we supply the pitch, ball, character busts and overlays as images), audio, or the integration into our web app and mobile app — we do that. Style rule: characters are static front-facing busts that move around the pitch — no limb animation, no poses. That's the game's identity. STACK TypeScript, PixiJS or Canvas 2D, Vite or similar for the build. No React required. No Unity/Godot/Phaser. BUDGET & MILESTONES Fixed price, total under €1,000, in four milestones: (1) one continuous minute from the sample log with the mount/data API, (2) full 0–90 with clock, score, speed, seek and camera, (3) key-moment zoom/overlays and asset hooks, (4) packaging, README, measured performance. Milestone 1 is small on purpose — it's how we both check the fit. WHAT IT SHOULD LOOK LIKE Three recordings of the game we are recreating (SoccerStar, 2013). Watch a minute of any of them before answering: https://www.youtube.com/watch?v=YyunEXgt91g https://www.youtube.com/watch?v=I7GFtxc8f9w https://www.youtube.com/watch?v=QOT2CU09OQQ Note what carries the match: the header with minute and score, the crowd behind the action, the players as large static busts that slide in and out of frame, the ball in front of them, and the thin strip at the bottom showing the whole pitch with the ball's position. Nothing is a cut — the scene pans and the busts move. That is the target: a hand-built engine with that feel, not a dashboard with a pitch in it. We supply the art. LANGUAGE Spanish-speaking freelancers preferred for smoother day-to-day communication, but English is perfectly fine — don't let that stop you from applying. TO APPLY Start your proposal with the word "kickoff". Include (1) a short video of something continuous and real-time you've built with PixiJS/Canvas/WebGL, and (2) one paragraph: our log gives one position per event — how would you move a player between two events? We select from proposals; no interview calls.