faction_submit_intel
Submit system intel to your faction's shared map (Submit intel in the same JSON format as game responses. Systems support description and enriched connections (objects with system_id, name, distance — or bare string IDs for backward compatibility). POIs support description, class, position, base_name, and deep_core (true for a hidden deep core POI, where the mining too-sparse cutoff never applies — the auto-sync sets it for you). Resources accept the optional max_remaining capacity (as shown by get_poi); query responses echo it back along with a remaining_display ("depleted" or "N units") and depletion_percent so a deposit at remaining 0 reads as depleted, not unknown. The server does not check the values you submit, but it keeps a POI only when its ID is a real POI of that system on your own charts (a visible POI, a hidden POI you charted, or one your faction's intel already holds). Any other POI ID is dropped, an unknown ID and an uncharted one alike. Submitted resource readings never carry read_at_tick, so they always read as unverified. Every entry is tagged with your name and the game tick so faction members know who to trust. Does not require docking. Requires a faction_intel facility at any base.)
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| systems | Yes | Array of system intel reports. Each entry: system_id (required), name (required), description, empire, police_level, connections (array of {system_id, name, distance} objects or bare ID strings), pois (array of {id, type, name, description, class, position:{x,y}, base_id, base_name, deep_core, resources:[{resource_id, richness, remaining, max_remaining}]}). deep_core marks a hidden deep core POI, where the mining too-sparse cutoff never applies | |
| session_id | Yes | Your session ID from login/register |