Primitives :: Unofficial EVE Frontier Development Notes

energy.move

Sat, 21 Feb 2026 12:23:00 +0000

The energy.move module is a fundamental Layer 1 Composable Primitive within the EVE Frontier world contracts. It provides the “digital physics” for power generation, consumption, and reservation across in-game structures. 1. Core Component Architecture The module is structured around two primary entities: the global configuration and the local state of energy-producing objects. classDiagram class EnergyConfig { +UID id +Table assembly_energy } class EnergySource { +u64 max_energy_production +u64 current_energy_production +u64 total_reserved_energy } EnergyConfig --|> EnergySource : defines requirements for Key Data Structures EnergyConfig: A shared object that acts as a global registry. It maps assembly_type_id to the specific amount of energy required for that structure to function. EnergySource: A storeable struct embedded within game objects (like a Manufacturing Unit). It tracks the individual power capacity and current load of that specific object. 2. The Energy Lifecycle The lifecycle of energy production involves transitioning from an idle state to active production, followed by the dynamic reservation of power by other systems.

fuel.move

Sun, 08 Mar 2026 00:00:00 +0000

The fuel.move module is a Layer 1 Composable Primitive that governs the lifecycle of consumable resources within EVE Frontier assemblies. It manages storage, consumption over time (burning), and efficiency logic. 1. Core Component Architecture The module separates global configuration (efficiency) from the specific fuel state within an assembly. classDiagram class FuelConfig { +UID id +Table fuel_efficiency } class Fuel { +u64 max_capacity +u64 burn_rate_in_ms +u64 quantity +bool is_burning +Option type_id +Option unit_volume +u64 burn_start_time +u64 previous_cycle_elapsed_time +u64 last_updated } FuelConfig --|> Fuel : modifies consumption rate of Key Data Structures FuelConfig: A shared object that maps fuel_type_id to an efficiency percentage (10–100%). Higher efficiency reduces the actual units consumed over time.

in_game_id.move

Wed, 28 Jan 2026 20:47:44 +0000

The in_game_id.move module is a Layer 1 Composable Primitive that provides a standardized identity system for all entities within EVE Frontier. It enables the creation of deterministic and unique identifiers that bridge the gap between off-chain game systems and on-chain Sui objects. 1. Core Component Architecture The module is centered around the TenantItemId struct, which serves as the primary key for object identification across the entire ecosystem. classDiagram class TenantItemId { +u64 tenant_id +u64 item_id } Note for TenantItemId “Used as a key in the ObjectRegistry for deterministic ID derivation.”

inventory.move

Sun, 08 Mar 2026 00:00:00 +0000

The inventory.move module is a Layer 1 Composable Primitive that implements the logic for storage operations, including depositing, withdrawing, and bridging items between the game and the blockchain. 1. Core Component Architecture The module defines two main structures: the Inventory container and the Item objects stored within it. classDiagram class Inventory { +u64 max_capacity +u64 used_capacity +VecMap items } class Item { +UID id +String tenant +u64 type_id +u64 item_id +u64 volume +u32 quantity +Location location } Inventory "1" *-- "many" Item : stores Key Data Structures Inventory: A storeable struct used within assemblies. It manages capacity through a VecMap, which offers an ideal balance for this use case despite high gas costs for large maps. Item: A key and storeable struct representing a stack of items. Every item must have a parent container, such as an Inventory or a ship. It includes a Location to enforce spatial mechanics. 2. Bridging Mechanics (Game ↔ Chain) The inventory primitive serves as the primary gateway for moving assets between the EVE Frontier game server and the Sui blockchain.

location.move

Fri, 13 Mar 2026 00:00:00 +0000

The location.move module is a Layer 1 Composable Primitive that manages the spatial positioning of entities in EVE Frontier. It is central to the game’s “digital physics,” specifically handling information asymmetry through cryptographic obfuscation. 1. Core Component Architecture The module defines the representation of a coordinate and the logic required to verify proximity without necessarily revealing exact positions. classDiagram class Location { +vector location_hash } class LocationProofMessage { +address server_address +address player_address +ID source_structure_id +vector source_location_hash +ID target_structure_id +vector target_location_hash +u64 distance +vector data +u64 deadline_ms } class LocationProof { +LocationProofMessage message +vector signature } LocationProof *-- LocationProofMessage : contains Location --|> LocationProof : validated by Key Data Structures Location: A storeable struct containing a cryptographic hash of coordinates (Poseidon2 hash). Storing hashes instead of cleartext coordinates allows for on-chain verification of spatial entities (like turrets or rifts) while keeping their exact locations private. LocationProofMessage: A signed message containing detailed proof information: the server and player addresses, source and target structure IDs with their location hashes, the distance between structures, additional data, and a deadline for expiration. LocationProof: A wrapper containing the LocationProofMessage and its cryptographic signature from an authorized server. LocationRegistry: A shared registry that maps assembly IDs to revealed Coordinates, enabling selective on-chain publication of exact locations. Coordinates: A revealed coordinate payload storing solarsystem as u64 and x, y, z as String values so negative and fractional coordinates can be preserved. LocationRevealedEvent: Emitted whenever a location is revealed into the registry, carrying the assembly identifiers, hashed location, and cleartext coordinates together. 2. Privacy through Obfuscation The “digital physics” of EVE Frontier require that certain locations (like hidden bases or ambushes) remain secret.

metadata.move

Sun, 08 Mar 2026 00:00:00 +0000

The metadata.move module is a Layer 1 Composable Primitive designed to handle descriptive and non-functional data for game entities in EVE Frontier. It provides a standardized way to attach “soft” information, such as names and descriptions, to on-chain objects. 1. Core Component Architecture The module is built around a simple, extensible struct that can be embedded into any Layer 2 Assembly. classDiagram class Metadata { +ID assembly_id +String name +String description +String url } Note For Metadata - Used to provide human-readable \ncontext for on-chain objects.

status.move

Wed, 28 Jan 2026 21:09:22 +0000

The status.move module is a Layer 1 Composable Primitive that manages the operational states of entities in EVE Frontier. It defines the “on/off” logic and deployment phases for game assemblies, ensuring that other primitives (like energy or fuel) only function when the object is in the correct state. 1. Core Component Architecture The module centers on a state machine that tracks whether an object is online, offline, or currently undergoing a state transition.