Component store

What a component is

Save/load that survives level travel. An inventory with a UI bound to the player pawn. A playable character kit with camera, movement, and input already mapped. Each ships as an install recipe the agent runs against your project — your GameMode, your player Blueprint — instead of a folder you have to integrate by hand.

Browse and buy on the store page. Purchases are tied to the same account and license key as the plugin.

Installing one

1. Ask the agent what you own: it calls ex_store_list, which returns the components licensed to you for this engine version.
2. ex_store_install downloads the recipe, runs any integrations against Blueprints and assets that already exist, and presents the whole thing as one approval — not forty.
3. ex_store_installed reads the project's install registry at Config/ExaroStudio/installed-components.json, so the agent always knows what is already in the project.

In practice that is one sentence in the chat panel:

Why it works this way

• Recipes, not merges. The component adapts to your project's names and structure rather than dropping a parallel copy of the game framework beside yours.
• One approval, full preview. The install is a mutating tool call like any other, so you read the summary before anything lands.
• Registry-aware. Reinstalling is idempotent — the agent checks the registry first instead of duplicating components.