Data Structure (archive.db - SQLite):
CREATE TABLE builds (
id INTEGER PRIMARY KEY,
island_code TEXT,
island_name TEXT,
description TEXT, -- User notes on the build
tags TEXT, -- Comma separated values
replay_path TEXT, -- Path to backed up replay file
screenshot_path TEXT, -- Path to user uploaded screenshot
last_played DATE
);
Tech Stack Recommendation:
Offset 0: "FBAP" magic bytes (4 bytes)
Offset 4: Version byte (0x01)
Offset 5: Compressed payload length (4 bytes, little-endian)
Offset 9: gzip( JSON metadata + actions )
Decompressed JSON snippet:
"header": "fortnite_version": "v28.01", "created": "2025-02-10T22:14:00Z" ,
"actions": [
"tick": 100, "piece": "floor", "material": "wood", "location": [125.3,75.0,32.5],
"tick": 104, "piece": "wall", "material": "wood", "location": [126.3,75.0,32.5], "rotation": 1,
"tick": 108, "piece": "ramp", "material": "brick", "location": [125.8,75.5,33.0], "rotation": 0
]
A well-organized portable archive is searchable and version-controlled. Recommended folder structure: fortnite builds archive portable
FortniteBuildsArchive/
├── /Retakes/
│ ├── /90s/
│ │ ├── Classic90_v1.json
│ │ ├── Protected90_v2.json
│ ├── /SideJumps/
├── /Tunnels/
│ ├── /Solo/
│ ├── /Duo/
├── /EditCourses/
│ ├── /TripleEdit/
│ ├── /MongraalClassic/
├── /ChapterLegacy/
│ ├── /C2S3_WaterBuilds/
│ ├── /C3S2_NoBuild (zero-build defensive boxes)/
└── README.txt (explains import method for each file)
Use Checksums: Generate a SHA-256 hash for each build file to ensure it hasn’t been corrupted during transfer. Data Structure ( archive
When you save a build, the game saves its position relative to your phone. If you want to place the build perfectly on a grid: Tech Stack Recommendation: Offset 0: "FBAP" magic bytes