Players Engine

Devlog · Entry 01

Why I'm building PlayersEngine

· Nic Vannetti · 5 min read

I'm starting this devlog a few months into the project, so this first entry is the story so far. From here on I'll write as things happen — decisions, mistakes, lessons from the closed beta. No marketing voice, no announcements dressed up as essays. Just notes from one person building a thing.

The itch

I've been playing games for more than twenty years and writing software for most of my adult life. Somewhere along the way I noticed something strange: my gaming life — easily my longest-running hobby, thousands of hours, hundreds of titles, friendships that outlasted jobs and cities — has no home anywhere.

Think about where your own gaming history actually lives. Your PC library is split between two or three storefronts, each with its own friends list that doesn't talk to the others. Your console history lives on whichever platforms you've owned, behind logins you half remember. Your stats for one competitive title are on some third-party tracker; for another, they're nowhere. The mobile games you sank a season into left no trace at all. Every launcher knows a slice of you, and no slice talks to any other.

If you've ever switched platforms — or just switched mains — you've felt the cost. Years of history effectively evaporate. The new community you join sees a blank profile and a default avatar. You were somebody; now you're nobody, again.

The networks we have weren't built for this

The obvious answer should be "just use social media", and the fact that it isn't the answer is the whole reason this project exists. Mainstream networks treat gaming as content, not identity. You can post a clip and it competes with food photos and news outrage in an algorithmic feed tuned for broadcast, not belonging. Your profile says who you are to advertisers; it says almost nothing about who you are as a player.

The gaming-native spaces are better but partial. Discord is brilliant for the group you're already in — and almost useless for being discovered outside it. Every server is an island, and everything you say sinks into scrollback within days. Forums and subreddits organise around topics, not people: great for "how do I beat this boss", terrible for "who am I in this hobby". Trackers and stat sites know your numbers but nothing about your story.

So the average gamer in 2026 maintains a dozen disconnected identities, none of which they own, none of which add up to anything. That's the gap.

What I'm doing about it

The one-line version is the same one on the front page of this site: a new kind of platform where your gaming journey matters — connect, compete, and build your legacy, together. A social platform built gamer-first, where the profile is the point, not an afterthought. I'll let the product say the rest when it's in front of you; this devlog is about the building of it, not a feature tour.

Why now, and why me

A few things had to be true before a project like this made sense for one person to attempt. Gaming had to become culturally mainstream — done; it's the biggest entertainment medium on the planet. Platform APIs had to exist so a player's history could follow them — patchy, but real. And cloud infrastructure had to get cheap enough that a bootstrapped solo developer could build for scale without paying for it up front — that one I'll cover properly in the next entry, because the answer shaped the whole architecture.

As for why me: there's no good answer except that I kept waiting for someone else to build it, and they kept not building it. I've spent my career on backend systems, I've spent my life in games, and at some point the overlap stopped being a coincidence and started being a to-do item.

Where things stand

The platform is real and running, and a closed beta is underway — small, invite-based, onboarding in waves. A group of players is using it daily and telling me, with the bluntness only gamers can deliver, exactly what's broken. It's the most useful feedback of my professional life. Future entries will dig into the stack, the solo-with-AI workflow I've landed on, how the beta pipeline works, and the problems in gaming communities I think are worth writing about in their own right.

If any of that sounds interesting, the entries are short and the archive is one click away. And if you'd rather just try the thing — there's a button in the header.

← All devlog entries