How styly-dev/styly-netsync works
Project type and purpose
• This is a full-stack network synchronization solution for Unity (STYLY) clients.
• It delivers:
• A Python-based NetSync server (handling binary-protocol events, serialization, REST bridge, CLI)
• A Unity package (C# runtime + editor scripts) that connects in-game avatars to the server over the network
• A benchmark suite (Locust load tests, Prometheus metrics, Grafana dashboards)
• Dev container and CI/CD workflows for development, testing, and release
File structure
• Top level:
• .devcontainer (VS Code remote dev)
• .github/workflows (CI: tests, performance, PyPI publish)
• STYLY-NetSync-Server (Python package + CLI + adapters + tests + benchmark folder)
• STYLY-NetSync-Unity (Unity project + sample scenes + “com.styly.styly-netsync” package)
• README.md, LICENSE, AGENTS.md, CLAUDE.md
• Server folder: “src/styly_netsync” modules: server.py, rest_bridge.py, nv_sync, binary_serializer, adapters, client, events
• Benchmark: locustfile.py, docker-compose.yml, client factory, metrics collector, Grafana and Prometheus config
• Unity folder:
• Assets/Samples_Dev (sample scenes, prefabs, scripts)
• Packages/com.styly.styly-netsync (Editor scripts to launch server, runtime scripts: ConnectionManager, AvatarManager, RPCManager, NetworkVariableManager, BinarySerializer wrapper, Prefabs, Utilities)
README
• Under construction; no explicit architecture section → rely on file layout to infer data flows