https://github.com/slashscreen/server-client-architecture
https://github.com/slashscreen/server-client-architecture
Last synced: about 2 months ago
JSON representation
- Host: GitHub
- URL: https://github.com/slashscreen/server-client-architecture
- Owner: SlashScreen
- Created: 2018-07-17T15:57:52.000Z (almost 7 years ago)
- Default Branch: master
- Last Pushed: 2018-09-30T19:05:01.000Z (over 6 years ago)
- Last Synced: 2025-02-09T19:36:18.589Z (3 months ago)
- Language: Python
- Size: 20.5 KB
- Stars: 0
- Watchers: 3
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# server-client-architecture
Hey! I had an idea in my head for a server-client interaction pipeline for creating multiplayer games, and so here we are.
# What's going on?
What's happening is that there are 2 scripts: a client (`gamewindow.py`) and a server (`gameserver.py`) that talk to eachother right now through `localhost:6789`.
The `client` sends a packet containing a dict (`playerdict`) that contains all the information concerning the box the user controls (WASD).
The `server` recieves the packet, and updates `world` accordingly, with whatever new information is sent by the `client`.
The `server`, in turn, sends the client the `world` dictionary, allowing it to access all of the other players' positions and draw them to the screen.