12-09-2015, 03:55 PM
The entire thing should be a separate plugin, because there will be multiple client plugins and they have to share the arena data somehow - the LobbyAPI plugin must check if two arenas (for two different plugins) overlap etc.
Technically, you could make an API layer which would be that single file that is dropped into each client plugin and provides a nice clean API with tables, and internally serializes those tables somehow and sends them over to the actual plugin via CallPlugin.
I think this thread should be more high-level: Define objects the API plugin will be working with - arena, lobby, player, spectator, score etc. Then define relations between the objects. From there we'll see what functions will be needed. Consider this an early prototype for the documentation, an introduction of sorts for someone who wants to write a minigame plugin but has no idea how minigames work.
Technically, you could make an API layer which would be that single file that is dropped into each client plugin and provides a nice clean API with tables, and internally serializes those tables somehow and sends them over to the actual plugin via CallPlugin.
I think this thread should be more high-level: Define objects the API plugin will be working with - arena, lobby, player, spectator, score etc. Then define relations between the objects. From there we'll see what functions will be needed. Consider this an early prototype for the documentation, an introduction of sorts for someone who wants to write a minigame plugin but has no idea how minigames work.