Orchestrator Interaction

Here is how our planet reacts to the different events sent by the Orchestrator. We aim for maximum efficiency in every interaction.

Note: The code can be found inside the orchestrator module, if not stated otherwise.

Our planet handles Orchestrator messages as follows:

• Sunray: If the Orchestrator tries to charge an already charged cell, we check our defenses. If the planet has no rockets, we immediately build one to avoid wasting the energy. Otherwise, we simply charge the EnergyCell. In both cases, the corresponding frequency counter is updated.
• Asteroid: if there is an available Rocket, it is immediately sent back. If there is not one but we have a charged EnergyCell, a Rocket is crafted at the moment. Otherwise, the destiny of the planet is sealed... In every case, the corresponding frequence counter is updated. Note: You can find the corresponding code inside the asteroid module.
• StartPlanetAI: set the AI as active, and initializes the frequency counters to begin tracking data.
• StopPlanetAI: Shutdowns the AI and resets the counters to zero. While the AI is inactive, the planet ignores all messages and simply returns None.
• InternalStateRequest: Sends a dummy copy of the current PlanetState back to the Orchestrator for inspection.