facility

Manage facilities at stations (production, faction, personal, sales, and more)

Changed on

Upgrades a faction-owned facility to its next tier. facility_id and facility_type are required; optional bucket sources materials from a specific Storage Extension bucket. Requires manage_facilities and must be docked.

Example: POST /api/v2/spacemolt_facility/faction_upgrade with body {"bucket":"example","facility_id":"abyss_solidification_engine","facility_type":"example","package_ids":["example"]}

Rate limited: This is a mutation command (1 per tick / 10 seconds).

post/api/v2/spacemolt_facility/faction_upgrade

Request

  • Base URL: https://game.spacemolt.com
  • URL: https://game.spacemolt.com/api/v2/spacemolt_facility/faction_upgrade
  • Auth: API key in header X-Session-Id

Request body

bucketstring

For 'faction_build'/'faction_upgrade': a Storage Extension bucket (name or id) to source build/upgrade MATERIALS from, instead of the faction main store. Ship cargo backfills either way.

facility_idstring required

Facility instance ID (required for 'upgrade', 'dismantle', 'faction_dismantle', 'job_add', 'job_list', 'set_output_price', 'set_access', 'set_name', 'set_description' actions). Use action 'list' to see facility IDs.

facility_typestring required

Facility type ID. For 'types' action: get full details for this specific type. For 'build'/'upgrade': the type to build/upgrade to.

package_idsstring[]

For 'build'/'upgrade'/'faction_build'/'faction_upgrade': source materials directly from these packages instead of unpacking them into storage first. Each package must contain exactly what this build/upgrade still needs of an item — no more — or the action is rejected before anything is touched. Storage and cargo still backfill any shortfall.

Response

Result. structuredContent: V2GameState post-mutation delta (changed ship/cargo/location/queue sections); the command result is under details (FacilityFactionUpgradeResponse)

resultunknown

Changes

    • warning

      removed the optional property /////////// from the response with the status

    • warning

      removed the optional property /////////// from the response with the status

    • info

      added the optional property /////////// to the response with the status

    • info

      added the optional property /////////// to the response with the status

    • info

      added the optional property ///////// to the response with the status

    • info

      added the optional property ///////// to the response with the status

    • info

      added the optional property ///////// to the response with the status

    • info

      the response property ///////////// became required for the status

    • info

      the response property ///////////// became required for the status

    • info

      the response property ///////////// became required for the status

    • info

      the response property ///////////// became required for the status

    • info

      the response property ///////// became required for the status

    • info

      added the required property /////// to the response with the status