CPunch
c0ba365cf5
- each CNPeer is given a unique chan *protocol.Event to pass events to the service.handleEvents() loop. this is now passed to CNPeer.Handler() as opposed to NewCNPeer(). - service has basically been rewritten. handleEvents() main loop uses reflect.SelectCase() now to handle all of the eRecv channels for each peer - new protocol Event type: EVENT_CLIENT_CONNECT - Added service_test.go; blackbox-styled testing like the others. TestService() starts a service and spins up a bunch of dummy peers and verifies that each packet sent causes the corresponding packet handler to be called. |
||
|---|---|---|
| .github/workflows | ||
| cmd | ||
| config | ||
| internal | ||
| login | ||
| shard | ||
| tdata@cc65dbb402 | ||
| tools | ||
| .gitignore | ||
| .gitmodules | ||
| build.sh | ||
| compose.yaml | ||
| Dockerfile | ||
| go.mod | ||
| go.sum | ||
| README.md | ||
gopenfusion
A toy implementation of the Fusionfall Packet Protocol and accompanying services, written in Go.
Landwalker demo
An implementation of a landwalker server is located in login/ && shard/. This includes a functional login server and a dummy shard (supporting the minimum amount of packets necessary). There is minimal support for NPCs, and minimal support for player interaction (chat & player movement being mostly it).
Startup the environment using
$ chmod +x ./build.sh && ./build.sh
$ docker compose up
The environment consists of a shard service, login service, redis && postgres containers. redis is used to pass login metadata between the login and shard services, while postgres is just used to store player accounts and characters.
login server is hosted at 127.0.0.1:23000, just join from your favorite client
Generating structures
Dump and decompile the Assembly - CSharp.dll assembly from the fusionfall main.unity3d, using a tool like ilspycmd. The full output source can then be passed to genstructs.py script located in tools/, which will handle scraping constants and calculating structure padding. See the script for details on usage.