DEV Community

Dinesh
Dinesh

Posted on

One Wrong ID Broke My Entire Multiplayer Setup

Everything looked correct. Plugins were enabled. But EOS still refused to connect.

This post is part of my daily learning journey in game development.

I’m sharing what I learn each day — the basics, the confusion, and the real progress — from the perspective of a beginner.

On Day 52 of my game development journey, I set up Epic Online Services (EOS) multiplayer properly inside Unreal Engine.


What I tried / learned today

I learned that EOS multiplayer requires specific plugins to be enabled first:

  • Online Subsystem EOS
  • Online Subsystem EOS Plus / EOS Utilities (if required)

After enabling them, I restarted Unreal Engine, which is very important.

Then I went to:

Project Settings → Online Subsystem

I added:

  • Product ID
  • Sandbox ID
  • Deployment ID
  • Client ID
  • Client Secret

All of these values come from the Epic Developer Portal.

I also edited the DefaultEngine.ini file and added the necessary EOS configuration lines. I learned that this config file is critical — without proper configuration, EOS will not initialize correctly.

What confused me

At first, EOS refused to connect.

I didn’t understand:

  • The difference between Product ID, Sandbox ID, and Deployment ID
  • Why login attempts kept failing
  • Where exactly to place configuration lines in DefaultEngine.ini
  • What the EOS testing environment (like EOS Null) is used for

Even one incorrect value completely broke the setup.

What worked or finally clicked

The biggest realization was this:

All IDs must match exactly with the Epic Developer Portal.

If even one character is wrong, EOS fails silently.

I understood that:

  • DefaultEngine.ini controls how the Online Subsystem initializes
  • Plugins must be enabled and the project restarted
  • Test configurations must match the selected deployment environment

Once everything matched correctly, the connection finally worked.

One lesson for beginners

  • Restart Unreal after enabling plugins
  • Double-check all IDs from the Epic Developer Portal
  • Save and verify your DefaultEngine.ini configuration
  • Keep the Client Secret secure
  • Always test with at least two clients

EOS setup looks complex at first, but once configured properly, it becomes reliable.


Slow progress — but I’m building a strong foundation.

If you’re also learning game development,

what was the first thing that confused you when you started?

See you in the next post 🎮🚀

Top comments (0)