Home

Illuminate your journey.

FieldLight is a mobile shell for creature companions. Studio is where trusted sources, custom datasets, sprites, labels, and relationships become syncable packs the app can render.

The mission is simple: beginners can sync official packs quickly, while advanced creators can build, version, and share custom worlds for the community.

Official Packs Creator Packs Community Hub

Quick Setup

Open the app, get a Pokédex.

Choose an official quick-start pack, preview the app experience, then generate a QR code or sync token.

Advanced Setup

Creator workbench

Mix APIs, sprite sources, raw JSON, metadata, module labels, mappings, and editable records.

Community

Hub foundation

A future home for official and community packs, ratings, comments, forks, filters, and featured collections.

Runtime Principle

The app is the shell.

Packs define labels, modules, relationships, sprites, metadata, and the vocabulary shown in FieldLight.

Pack Vocabulary

The pack owns the public names.

An internal creatureDex can appear as Pokédex, Paldeck, Locationdex, Pokéarth, or any pack-defined label.

Data Principle

Calculation metadata matters.

Stats, natures, type charts, teams, boxes, and relationships stay editable because the app uses them at runtime.

Quick Setup

Just give me a Pokédex.

Choose an official quick-start pack, check the app-style preview, then generate a QR code or sync token for FieldLight. No mapping, local API, or raw JSON required.

Official quick-start packs

Recommended Use Pokémon / PokeAPI

Select the trusted starter pack and keep the setup path simple.

Included Default sprites

Use the pack's recommended sprite source for the app preview and sync payload.

Preview Live app view

The preview shows the pack vocabulary and app menus before syncing.

Looks good?

Generate QR Code / Sync Token

Generate a hosted FieldLight Signal, verify that the resolver is reachable, then scan the QR or copy the token. Export, publishing, and app install remain separate.

PokeAPI is ready as the recommended starter pack.

Hub

Community packs will live here.

The Hub is planned for sharing, rating, commenting on, forking, filtering, and featuring FieldLight packs. It stays intentionally simple until saving, profiles, and stable sync publishing are ready.

Future

Search and filters

Find packs by game, world, modules, provider, update date, popularity, or compatibility.

Future

Community signals

Ratings, comments, leaderboards, issue notes, and featured packs will help the ecosystem stay healthy.

Future

Overlay packs

Competitive, event, romhack, and sprite overlays should layer onto base packs cleanly.

Advanced Setup

Build a pack step by step.

Choose data and art sources, describe the modules your world needs, then prepare a FieldLight pack for review. Developer tools are still available when you need diagnostics.

Studio View Mode

Choose how much Advanced Setup shows.

Creator View keeps the setup path focused. Developer View reveals prototypes, diagnostics, local tools, and fallback/debug surfaces.

Advanced Setup Mapper

Map a live API into FieldLight containers.

Paste a public JSON endpoint, inspect real source records, connect them to FieldLight containers, then review the draft artifact before any future Signal save.

Creator-safe workspace No Hub write, Signal creation, app install, publishing, sync, or Local Draft mutation happens here.
Start workspace

Begin with an empty shell, import a public source, or open an existing pack later.

Reference guide Creature collector Character builder Loot database Crafting guide Location/quest guide
1
Source Explorer

Import a public JSON API and browse the detected collections before choosing FieldLight mappings.

Paste a public JSON API URL, then load the source to browse records.

Preview only. Nothing is saved, published, synced, installed, or turned into a Signal QR here.

Load a source to browse collections and records.
2
FieldLight Mapper

Choose which source collections and fields become FieldLight containers, titles, sprites, tags, stats, and relationships.

Load a source, then choose how its records map into FieldLight. Mapping choices stay in this browser until you explicitly prepare them. Source will appear here after loading.

Detected modules will appear here after the source loads.

source modules: not loaded
source collections: not loaded

Container choices appear here after a source loads.

container choices: not loaded

Choices are preview-only until you explicitly prepare the mapping draft.

Field role choices appear here after a source loads.

field roles: not loaded

Field roles follow the selected source record.

Prepare browser-memory mapping

Load a source, choose containers and field roles, then prepare a browser-memory mapping draft with explicit confirmation.

  • Source/sample must be loaded successfully.
  • Source-aware preview must be visible.
  • Container choices must be reviewed.
  • Field role choices must be reviewed.
  • Creator confirmation is required before browser-memory draft state is prepared.
No mapping draft has been prepared.

This does not save, publish, sync, create a Signal, or install anything.

3
Mobile Runtime Preview

See what your users would see from the selected source record.

Creature Dex Item Dex Equipment Dex Skill Dex Recipe Dex Modifier Dex Reference Chart Stat Block Build Loadout Location Dex Quest Dex Custom Containers

Relationships and builder effects will be mapped in a later step.

What users will see Choose a source
No source loaded
Load a source to preview a record

Select a record to see a user-facing preview.

preview waiting
Status
Waiting for source data
Signal draft preview

signal_draft_idle: map a loaded live API source into browser-memory choices before Signal readiness can be reviewed.

No Signal-ready artifact exists yet. Hosted Signal generation remains a later storage/resolver gate.
Normalized artifact preview

normalized_artifact_idle: preview a live API source and prepare browser-memory mapping choices before artifact readiness can be reviewed.

No normalized artifact preview exists yet. Nothing is exported, saved, published, synced, or turned into a Signal QR.

live_api_artifact_export_idle: no local artifact export has run. This is a local file download only; it does not write Supabase, resolver rows, Signal QR, publish, sync, or runtime state.

Generic Runtime Shell parity remains a separate gated phase.

Creator path

Build, check, and export a draft pack.

Follow this path left to right: choose sources, map data, check readiness, protect local draft work, export a normalized artifact, then prepare a draft handoff. Developer View remains the diagnostic escape hatch.

1 Choose sources

Load the sample or confirm the data and artwork inputs in the source setup panels below.

2 Map data

Match source containers to modules, then review field choices.

3 Review readiness

Check mapping preview, review checklist, blockers, and warnings.

4 Protect draft work

Use browser-local save, restore, import, and export safeguards.

5 Export artifact

Export normalized pack JSON as a draft artifact, not a published pack.

6 Prepare handoff

Review draft handoff readiness and export a local JSON handoff when eligible.

Mapping + readiness

Decide how source data becomes a draft pack before exporting.

Mapping is the creator decision layer. Readiness is the checkpoint that tells you whether those decisions are ready for an explicit normalized export or draft handoff.

Container/module mapping

Choose which source collections become FieldLight modules, lists, and relationship groups.

Field mapping

Choose the fields used for names, IDs, descriptions, sprites, metadata, and relationship references.

Readiness before export

Warnings mean review before export. Blockers mean fix the mapping or source before export.

Draft safety and exports

Local Draft stays browser-local. Normalized export and Draft Handoff export remain explicit file actions.

Creator View summarizes the decisions. Developer View has diagnostics. Nothing here publishes, syncs, installs, mutates Local Draft, or makes the pack available in the app.

Final creator checkpoint

Preparing draft handoff status.

Draft only. Not published. Not synced. Not available in the app yet.

Review the read-only handoff preview when deeper diagnostics are needed.
Waiting for draft handoff status. No file is generated yet. No local draft handoff export receipt yet.

Publishing readiness

Publishing is not available yet.

Exported draft handoff is not published. Nothing is synced, uploaded, registry-backed, or app-available.

Export a validated draft handoff first. Future publishing will require explicit creator confirmation.
Registry, account, cloud, resolver, and runtime install architecture is not implemented.
Publish Candidate Preview

Waiting for draft handoff status. This preview is read-only and does not publish.

Not published. Not synced. Not registry-backed. Not account-owned. Not app-available.
Registry Record Preview

Waiting for publish candidate status. This preview is read-only and does not write registry records.

Not published. Not uploaded. Not synced. No registry record, account ownership, resolver record, or runtime install exists.
Registry Submission Package Preview

Waiting for registry record preview status. This local package preview is not submitted or published.

Local file only. Not uploaded, not synced, not written to registry, and not app-available. Waiting for package status. No file is generated yet. No local registry submission package export receipt yet.
Static Dev Registry Preview

Waiting for registry submission package status. Studio preview is read-only; dev registry write/read prototypes are CLI-only.

Studio writes and reads no registry files. Not submitted, not published, not uploaded, not synced, and not app-available. Planned path will appear after the submission package preview is ready.

Advanced handoff verification, parse diagnostics, runtime shell internals, Signal, and QR fallback/debug panels stay in Developer View.

Advanced Setup prototypes

Prototype Dashboard

Jump to active creator workflow prototypes. These previews do not publish, sync, write registry records, or change mobile runtime behavior.

Pack structure

Start with the shape of your world.

Pick the kinds of information this pack needs to present. These choices guide which modules, relationships, and previews Studio should prepare.

Creatures Attacks / Moves Abilities / Traits Items Locations Type Chart Natures / Stats Boxes / Teams

Module containers

Modules become the app sections your players browse.

Creaturedex / Pokédex Attackdex / Moves Abilitydex / Traits Itemdex Naturedex Type Chart Locationdex / Pokéarth Boxes / Battle Teams
Legacy / Developer Tools: Local API & Backups

Use these controls only when running the local content API. Published Studio packs should use manifest links instead of a LAN or loopback address.

Start the FieldLight content API, then load a dataset pack.

Choose data and art sources

FieldLight keeps encyclopedia data, competitive overlays, and sprite packs separate so you can mix reliable sources without locking the app to one upstream.

Recommended base PokeAPI REST

Primary encyclopedia source for Pokemon, forms, moves, abilities, items, natures, types, and generations.

Experimental adapter GraphQL PokeAPI

Useful for testing nested queries, pagination, caching, selective sync, and mapping flexibility.

Competitive overlay Pokemon Showdown

Best suited for learnsets, legality, battle mechanics, rulesets, and validation metadata after a base pack exists.

Independent assets Sprite Packs

Sprite sources can be PokeAPI, PokeSprite, a CDN, Discord export, or any manifest that references stable FieldLight IDs.

Understand source roles

Each source type is best at a different job. This guide helps you choose a stable base before adding optional overlays or custom art.

Source
Encyclopedia
Competitive
Sprites
Best Use
PokeAPI REST
Primary
Limited metadata
Optional
Recommended default pack source.
GraphQL PokeAPI
Experimental
No
Optional
Stress-test nested mapping, caching, and selective sync.
Pokemon Showdown
Overlay only
Primary overlay
No
Rules, legality, learnsets, and battle validation.
Sprite Pack
No
No
Primary
Custom art, icons, HD packs, or pixel-art packs by stable ID.

Connect pack data

Point Studio at the data source for this pack. PokeAPI REST is the recommended default while additional adapters mature. Static JSON checks only verify access; they do not import, publish, sync, or install a pack.

Creator sample

Try the Pokémon sample draft path.

Loads the generated-dev Pokémon sample into a temporary draft preview. Nothing is saved to Local Draft, published, synced, installed in the app, or exported automatically.

sample_idle: temporary preview only. Export remains explicit.

Source: /official-packs/pokemon-pokeapi/snapshots/generated-dev/manifest.json Pack route: /official-packs/pokemon-pokeapi/snapshots/generated-dev/pack.json Not saved to Local Draft. Not available in the app yet.

Click the sample load action first. Nothing is saved, exported, published, synced, or installed automatically.

  • Load the sample only when you want a temporary preview.
  • Use Mapping next to inspect module and field choices.
  • Review readiness and Local Draft safety before saving anything.
  • Choose normalized export or draft handoff export only when you explicitly need a file.
No connection tested yet.

Choose artwork and sprites

Art stays independent from data. You can pair official data with custom artwork, or use a shared sprite source with custom records.

  • Use stable FieldLight IDs: pokemonId, formId, itemId.
  • Declare each image variant: normal, shiny, female, shiny-female, artwork, icon, or item-icon.
  • Mark each source as pixel-art, hd-art, or mixed so the sprite pipeline knows whether to upscale.
No sprite source tested yet.

Optional sprite manifest

Use a manifest when importing artwork from Discord, a CDN, a folder export, or another community pack.


          


          

            
Pack summary preview

            
Review the loaded data at a glance before moving into mapping, readiness checks, or export.

            

          

        

      


      

      

      

        Legacy / Developer Tools: Dataset Editors & Raw JSON
        

          Manual collection editors, import merge tools, backup controls, and raw JSON are preserved for technical users without dominating the beginner path.
        


        

          

        

          
          

          

          

            
            
            
          

        

      


      

        
        

          

            
            
          

          

            
            
          

          

            
            
          

          

            
            
          

          

            
            
          

          

            
            
          

          

            
            
          

          

            
            
          

          

            
            
          

          

            
            
          

          

            
            
          

          

            
            
          

          

            
            
          

        

        

          
        

      


      

        
        
Use this for gender differences, regional forms, color/pattern forms, Mega, Gigantamax, or other alternate form data.

        

          

            
            
          

          

            
            
          

          

            
            
          

          

            
            
          

          

            
            
          

          

            
            
          

          

            
            
          

          

            
            
          

          

            
            
          

          

            
            
          

          

            
            
          

          
          
          
          

            
            
          

        

        

          
          
        

      


      

        
        
Create multiple normal/shiny/gender/artwork asset records for the selected Pokemon form in one step.

        

          

            
            
          

          

            
            
          

          

            
            
          

          

            
            
          

          

            
            
          

          

            
            
          

          

            
            
          

          

            
            
          

          

            
            
          

        

        

          
          
        

      


      

        
        
Open a Pokemon, form, or version profile first, then prefill the shared fields below.