Prepare ZIP files and the installation plan in Architect

From the Files step, open Architect to add your creation’s ZIP archives and prepare the content Rikoooo Hub will install.

1. Include the files the add-on needs to work, without personal files or unrelated content.
2. Once the file tree is available, inspect it and arrange the items to install.
3. Check the plan’s simulators and destinations. If the content differs by simulator, check each configuration.
4. Validate the plan and confirm that it is saved before continuing the submission. If a check identifies a problem, correct the items shown.

The Hub copies the files specified by the plan; placing a program or command inside the ZIP does not make it run. Declare any required external applications or settings separately.

The Files step shows the limit for each ZIP and the space available for the add-on. Stored ZIPs and uploads in progress count towards this space. Creating another draft does not increase the quota.

Example: prepare a ZIP containing one scenery package

Suppose your ZIP contains a folder called my-airport, with manifest.json, layout.json and a scenery subfolder. This name is fictional; preserve your creation’s actual names and folder structure.

The package folder should sit directly inside Community, without keeping the ZIP or adding an outer folder:

Community/
  my-airport/
    manifest.json
    layout.json
    scenery/

1. Add the ZIP in Architect and wait for its file tree to become available.
2. Find the package folder and preserve its internal structure. In the content to install, check that the folder and its files are included, without an unnecessary outer folder.
3. Check the plan’s destination and simulator. Select only the MSFS versions in which you have actually checked the scenery.
4. Open Installation summary. Review the destination and planned file count. The sections also describe the expected effects of an update, repair or uninstall. If this information is not available yet, wait for preparation to finish.
5. Correct the plan if needed, then choose Prepare and upload when available and confirm that the plan is saved before continuing.

This summary is a preview: it does not install anything on your PC or launch the simulator. It does not replace checking the scenery in a flight in every MSFS version you list.

Community is the destination in this example. If your content requires Community2024 in MSFS 2024, choose that destination in the plan settings. Hub uses the plan’s destination for each simulator; do not add an extra simulator-named folder inside the package.