Raven/osirose-new
SHA256
1
0
Fork 0
Code Issues 1 Pull Requests Actions Packages Projects 6 Releases Wiki Activity

Tons of fixes

Browse Source 
Added movement updates
Updated how entities are checked
Events sending between packet service all the way to the logic service
This commit is contained in:
raven
2025-06-25 12:30:07 -04:00
parent f75782885b
commit d906cd8d64
34 changed files with 3550 additions and 186 deletions
Download Patch File Download Diff File Expand all files Collapse all files

30
world-service/README.md
View File

@@ -69,6 +69,36 @@ The service can be configured using environment variables:
- `LISTEN_ADDR`: The address to listen on (default: "0.0.0.0")
- `SERVICE_PORT`: The port to listen on (default: "50054")
- `LOG_LEVEL`: Logging level (default: "info")
- `MAP_IDS`: Comma-separated list of map IDs to manage (e.g., "42,43,44,45")
- `WORLD_SERVICE_NAME`: Name of the world service instance (default: "default-service")
### Game Logic Connection Retry Configuration
The world service includes comprehensive retry logic for connecting to game logic instances that may not be ready immediately:
#### Connection Info Retrieval Retry
- `CONNECTION_INFO_MAX_RETRIES`: Maximum number of retry attempts for getting pod connection info (default: 3)
- `CONNECTION_INFO_INITIAL_DELAY_MS`: Initial delay between connection info retries in milliseconds (default: 2000)
- `CONNECTION_INFO_MAX_DELAY_MS`: Maximum delay between connection info retries in milliseconds (default: 10000)
#### gRPC Client Connection Retry
- `GAME_LOGIC_MAX_RETRIES`: Maximum number of retry attempts for gRPC connections (default: 5)
- `GAME_LOGIC_INITIAL_DELAY_MS`: Initial delay between gRPC connection retries in milliseconds (default: 500)
- `GAME_LOGIC_MAX_DELAY_MS`: Maximum delay between gRPC connection retries in milliseconds (default: 10000)
Both retry mechanisms use exponential backoff, doubling the delay after each failed attempt up to the maximum delay. The service will continue starting even if some game logic instances fail to connect, allowing for partial functionality.
### Kubernetes Service Creation
The world service automatically creates both Pods and Services for each game logic instance:
- **Pod**: Contains the game logic service container
- **Service**: Provides stable networking and service discovery
- Type: ClusterIP
- Port: 50056 (gRPC)
- Selector: Matches specific instance by app, map_id, and instance labels
The world service connects to game logic instances using Kubernetes Service DNS names (e.g., `world-default-service-42-service.default.svc.cluster.local`) instead of direct Pod IPs, providing better reliability and following Kubernetes best practices.
## Running the Service