Looking for Unreal Engine Devs — MMO Infrastructure Idea (Need Help Building It)

I’m going to be direct.

I’m not a senior Unreal engineer or backend architect.

I’m someone with an idea — and I want to see if there are developers here who think it’s worth turning into something real.


:light_bulb: The Idea (High-Level)

Building MMOs in Unreal Engine is still way harder than it should be.

Every team ends up rebuilding the same core systems:

  • Networking + replication systems
  • Backend infrastructure from scratch
  • Persistence and player state systems
  • Server scaling / sharding logic
  • Cross-world or multi-zone architecture
  • Inventory / progression frameworks

Even “standard” multiplayer games end up reinventing 80% of this.

So the idea is simple:

What if Unreal Engine had a reusable MMO infrastructure layer — like a modular SDK you plug into your game instead of building everything yourself?

Not a game framework.

Not a SaaS backend lock-in.

A developer-owned MMO foundation layer for Unreal Engine.


:gear: What This Could Become (If Done Right)

I’m not claiming this is the final design — this is the direction I’m trying to explore with people who actually know this space.

But imagine:

  • Plug-in backend architecture for Unreal Engine
  • Persistent world + player state system
  • Scalable server/zone framework
  • Optional cross-world systems (modular, not forced)
  • Standardized multiplayer architecture templates
  • Clean integration with UE5 replication / GAS / EOS if needed
  • Self-hosted or cloud-deployable backend services

Basically:

A starting point for MMOs instead of a blank slate every time.


:warning: Reality Check

To be clear:

  • I do NOT have a working system
  • I do NOT have a backend already built
  • I am NOT claiming this is technically solved

This is an early concept — and I fully expect experienced engineers will tear it apart, reshape it, or explain why parts of it don’t make sense.

That’s exactly what I want.


:fire: Who I’m Looking For

If you’ve ever worked on or near MMO systems, multiplayer architecture, or Unreal networking — I want your input.

Specifically:

  • Unreal Engine C++ developers (networking / replication)
  • Backend engineers (distributed systems, APIs, scaling)
  • MMO or large-scale multiplayer dev experience
  • DevOps / cloud infrastructure experience (optional but valuable)
  • Even people who have failed at building this kind of system

Honestly, I’m not looking for “idea agreement.”

I’m looking for people who can say:

“Here’s what actually works, and here’s what doesn’t.”


:high_voltage: Why This Might Be Worth Your Time

If something like this is even partially viable, it could become:

  • An open-source foundation for MMO development in Unreal
  • A shared infrastructure layer that multiple projects build on
  • A way to cut down years of backend duplication in game dev

Or it could turn into a learning experiment that documents how MMO systems actually should be structured.

Either way — it’s worth exploring.


:open_mailbox_with_raised_flag: If You’re Interested

Drop a reply or DM with:

  • Your Unreal / backend experience
  • Any multiplayer or networking systems you’ve worked on
  • Your honest take: is this idea completely unrealistic or worth exploring?

No fluff needed. Even a “this won’t work because X” is useful.


:brain: Final Note

I’m not trying to pitch a finished product.

I’m trying to find the people who immediately understand the problem space and think:

“Yeah… I’ve dealt with this before. This actually should exist.”

If that’s you — I’d love to talk.

:money_bag: Follow-Up: Player Subscription Model to Fund Infrastructure (Live Games)

One thing I want to add to the idea — and I’d really like feedback from people who’ve actually shipped online games — is a possible player-funded infrastructure model once a game is live.

The idea is simple:

Instead of studios fully front-loading server + backend + maintenance costs, the active player base subscribes, and those subscriptions directly fund the ongoing infrastructure and development costs of the world.


:puzzle_piece: How This Could Work (Conceptually)

Once a game is live and stable:

  • Players optionally subscribe (monthly or seasonal)
  • That subscription revenue is allocated toward:
    • Server infrastructure (compute, scaling, hosting)
    • Backend services (persistence, authentication, world state)
    • Ongoing maintenance and live ops
    • Possibly continued feature development

So instead of a fixed-cost model where the studio absorbs everything, it becomes:

“The world is funded by the people actively living in it.”


:video_game: Why This Idea Came Up

MMOs and large online games already kind of function like this indirectly:

  • Sub-based MMOs (like classic models)
  • Battle passes / seasonal monetization
  • Cosmetics funding live ops
  • DLC expansions funding continued development

This is just trying to formalize that into a direct infrastructure support system tied to actual runtime costs.


:warning: Important Reality Check (This Part Matters)

I’m not assuming this is viable — I know there are serious challenges:

  • Player willingness to pay ongoing subscriptions is unpredictable
  • Free-to-play expectations are dominant in many markets
  • Cost scaling might not align cleanly with player count
  • Risk of “paying for the right to access servers” perception issues
  • Requires extremely transparent value delivery

So this is very much an open question, not a proposal.


:handshake: What I’m Trying to Figure Out

I’d really like input from people who’ve worked on:

  • Live service games
  • MMO economies
  • Subscription vs F2P monetization systems
  • Backend cost scaling for multiplayer games

Specifically:

Has a “player-funded infrastructure pool” ever actually worked cleanly at scale?

Or is this just another version of existing subscription models under a different framing?


If nothing else, I’m trying to connect the technical side (MMO infrastructure SDK idea) with a realistic long-term funding model, and I don’t want to assume the wrong structure early.

Feedback appreciated — especially critical takes.