evoid-godot
Godot game integration — Intent Handler system
Quick Start • Intent Handler • Features • API
Quick Start
uv add evoid-godot
Method 1: Intent Handler (Recommended)
from evoid_godot import register_handlers
# Register Godot adapter as Intent handlers
register_handlers()
Method 2: Direct API
from evoid_godot import create_game_handler
handler = create_game_handler()
Intent Handler
evoid-godot registers game-related Intents for Godot integration.
Features
- WebSocket connection to Godot games
- Topic-based pub/sub system
- Game hosting with splash screen config
- Multiplayer support
Configuration
TOML
[engines]
godot = "godot"
API
register_handlers()
Register Godot adapter as Intent handlers.
GameHost Methods
| Method | Signature | Description |
|---|---|---|
register_build |
register_build(game_id, build_dir, title, splash) |
Register a game build |
start |
async start(game_id) |
Start hosting game |
How It Works
Godot client sends Intents via WebSocket. The adapter converts them to EVOID Intents and routes through the pipeline. Game events like player_move use EPHEMERAL level (fast, no auth). Real-money actions like purchase_item use CRITICAL level (full audit).
Dependencies
evoid>=0.4.0
Links
License
MIT
Metadata
Release files for evoid-godot 0.2.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| evoid_godot-0.2.0-py3-none-any.whl | Python 3 | none | any | Details for evoid_godot-0.2.0-py3-none-any.whl |
Release files / evoid_godot-0.2.0-py3-none-any.whl
| Download URL | evoid_godot-0.2.0-py3-none-any.whl |
|---|---|
| Size | 11.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
945ccd4e5d6a859d6e8527c3fb7b77dd49141581bb4ea6fe4c423174c9b72b0a
|
|
BLAKE2b-256 checksum How to use checksums |
c20dc90c40a2f5a57c20ce752e52faed5273db5593c8fa8ac42171c5e6a96f9e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.12.3 {"installer":{"name":"uv","version":"0.12.3","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
Security for evoid-godot 0.2.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.