Skip to content

Conversation

@albertok
Copy link
Contributor

@albertok albertok commented Aug 2, 2025

Solves #401 and a little something extra.

  1. Co-ordinates launched instances so one is the server and the others connect to it.
  2. Simulates network latency and packet loss

Simply add it to your scene tree and configure the desired network simulation.
It will fire separate signals for the host and clients to bootstrap from.

image

Closes #401

@elementbound elementbound changed the title #401 auto connect and network conditions simulation feat: Autoconnect with network conditions simulation Aug 2, 2025
@albertok
Copy link
Contributor Author

albertok commented Aug 2, 2025

@elementbound Review notes have been addressed. :)

@elementbound elementbound force-pushed the network-autostart-and-latency-generator branch from e8d7c30 to 57a3e82 Compare August 15, 2025 20:04
@elementbound
Copy link
Contributor

elementbound commented Sep 14, 2025

Note to self on remaining stuff:

  • Ensure autoconnect doesn't accidentally run in CI
  • Do another check to see which methods would make sense as public and private
  • Update docs, since it's now an autoload

@elementbound elementbound merged commit d2a4426 into foxssake:main Sep 24, 2025
2 checks passed
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.

Automatically host and connect on start

2 participants