Skip to content

Soften home server capacity claim and remove specific example#1134

Open
mcfnord wants to merge 1 commit intojamulussoftware:next-releasefrom
mcfnord:home-server-capacity-nr
Open

Soften home server capacity claim and remove specific example#1134
mcfnord wants to merge 1 commit intojamulussoftware:next-releasefrom
mcfnord:home-server-capacity-nr

Conversation

@mcfnord
Copy link
Copy Markdown
Contributor

@mcfnord mcfnord commented Apr 30, 2026

(This came from discussion at #1133.)

The "eg 10 Mbit/s down and 1 Mbit/s up" example was tied to a specific connection speed that doesn't reflect current home broadband pitfalls, such as wireless connections.

This needs translation.

  • [X ] I'm sure that this Pull Request goes to the correct branch

The "eg 10 Mbit/s down and 1 Mbit/s up" example was tied to a specific
connection speed that may not reflect current typical home broadband.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
@mcfnord
Copy link
Copy Markdown
Contributor Author

mcfnord commented Apr 30, 2026

I had 1 Mbit/s up until last year and it never hosted more than 1 or 2 successfully!

Usually, problems are on the _Client_ side and should be fixed there. Have a look at the [Troubleshooting page](/wiki/Client-Troubleshooting) if needed.

However, various problems can also arise when setting up Servers - especially when run on a low-bandwidth home connection. It's usually fine to have less than 5 players on a slower-speed home connection (eg 10 Mbit/s down and 1 Mbit/s up). You can read more about network requirements at [different quality settings here](Server-Bandwidth).
However, various problems can also arise when setting up Servers - especially when run on a low-bandwidth home connection. It can work fine to have less than 5 players on a slower-speed home connection. You can read more about network requirements at [different quality settings here](Server-Bandwidth).
Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

can, maybe might should appear here. I see hosting at home as the Achilles Heel of the whole technology. Many people start there, thinking they really want or need to, and many of those people have a bad experience, due to upstream speed or even wireless residential bottlenecks.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I tend to agree -- we shouldn't really suggest less than 2Mbps each way per client. With 4.0.0, we'll need to up that, too - the Max Quality work will need to make it clear what the Server needs.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The introduction of wireless residential seems to throw a lot of the traditional throughput arithmetic out the window. We're conflating capacity with consistent timeliness and in my experience this breaks down often in residential scenarios. We might suggest avoiding hosting a server on a wireless connection altogether, and we might suggest that fiber is fine for hosting at home.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes - agreed: hosting on wireless ... words fail me.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants