# Public API {% hint style="danger" %} **This section is under construction!** {% endhint %} ## How does it work? Our server exposes its public API via network protocols. We use 2 separate connections to handle 2 ways of communication: * **Pub/Sub**: This is how we propagate changes to our scripts, as we call our server-defined events. * **Req/Res**: Used by scripts to execute remote methods on the server-side expecting a result. ### Technology stack We use `nanomsg` as our message broker, which gives us the ability to use various protocols (TCP, IPC, ...) and connection types. To exchange data, we use `msgpack` for binary serialization. ### Resources Term *resources* is loosely defined for scripts that implement logic for the server. These scripts could be game modes, small scripts such as announcements or an online map. Resources can be written in any language that supports the technology stack we use, since they are standalone network clients connected to the server. Check out [NodeJS](/languages/resource-nodejs.md) for an example of such language/ecosystem. If you're interested in writing another language's integration, check out the [our tutorial](/tutorials/developer-api.md). --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.oakwood-mp.net/public-api.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.