jakeObrian34
Student of software engineer , PES IS LIFE
- 29 August 2026
Hi everyone,
I’m a Software Engineer looking to build a dedicated team of developers to create an automated Matchmaking Launcher tailored initially for PES 2011.
The goal is to deliver an arcade-style, zero-friction multiplayer experience inspired by Parsec Arcade—removing all complex setups, account creations, and manual match reporting.
I’m a Software Engineer looking to build a dedicated team of developers to create an automated Matchmaking Launcher tailored initially for PES 2011.
The goal is to deliver an arcade-style, zero-friction multiplayer experience inspired by Parsec Arcade—removing all complex setups, account creations, and manual match reporting.
Core Engineering Vision & Key Requirements
- Zero-Friction UX: No account creation, no forms, and minimal clicking. Players open the app and instantly enter the queue.
- All-in-One Distribution: The setup bundle will directly include PES 2011, Parsec, and the ViGEmBus driver to ensure zero environment mismatch across client PCs.
- Dynamic Host Migration & Drop Rules: If the designated Host disconnects/leaves mid-match, hosting duties migrate dynamically, and the Host’s current opponent automatically advances in the bracket.
- Instant Re-Queue: Players eliminated from the knockout tournament are immediately routed back to the queue/loading screen to join new matches without restarting the app.
- Computer Vision Team Detection: Team identification in-game will be detected visually using team crest/logo recognition.
System Execution Flow
- Step 1: The user launches the app (PES 2011 Cup.exe).
- Step 2: The app automatically enters the matchmaking pool and displays a active loading/queue screen.
- Step 3: As soon as 4 players join the server, the backend randomly selects one player as the Host, opens Parsec and PES 2011 on that PC, and silently connects the remaining 3 players via the Parsec SDK.
- Step 4: Upon match completion, the system automatically reads the match memory/screen, prints the score into the app bracket, and advances the winner. After the final match, the app displays the Champion and prompts players to re-queue or exit.
- Step 5: The app automatically exports a local .txt log recording the tournament results, champion name, and timestamp.
Tech Stack & Roles Needed
- Frontend / Desktop Dev (Electron / Flutter Desktop / C#): To build the lightweight, arcade-style UI, bracket displays, and loading screens.
- Backend Dev (Node.js / Python / Supabase / WebSockets): To manage real-time matchmaking queues, random Host selection, bracket logic, and host-migration fallback triggers.
- Low-Level / Automation Dev (Python / C++ / OpenCV): To handle memory reading (ReadProcessMemory) or OCR (OpenCV) for score and crest detection, ViGEmBus controller mapping, and Parsec SDK silently routing.