Plugin System

[blinkuz]

Is there any documentation for the plugin system, or at least an example showing the minimal structure a plugin needs to work?

I’d like to extend the Gateway API with more administrative features, mainly actions that are currently only possible through the WebApp, so we can have additional tools that interact with the API.

[justkeepquiet]

Hi,

Is there any documentation for the plugin system, or at least an example showing the minimal structure a plugin needs to work?

Documentation and example will be added in the future.

I’d like to extend the Gateway API with more administrative features, mainly actions that are currently only possible through the WebApp, so we can have additional tools that interact with the API.

This functionality is not currently available because the API does not support the WebApp protocol. It may be implemented in the future, but I cannot promise it.

[blinkuz]

Thanks for getting back to me. After looking at the plugin loading code, I think I can already make a functional one.

I initially thought the WebApp used the same protocol and communicated through the Hub just like the hubFunctions in the API. I’m interested in contributing to this repository, but I’m new to the world of TERA private servers, though I do have programming experience, so I’m open to any advice regarding the WebApp protocol so I can try to implement it in TERAAPI and submit the contribution.

So far, I’ve been digging into the WebApp.dll code and have more or less identified the classes responsible for handling connections and converting network packets. What I still don’t understand is which server these packets are sent to. From what you’re telling me, I can rule out the Hub, so do these connect directly to one of the game’s main servers?