WikilyWIKILY
Tous les jeux19 wikis · choisissez votre jeu
19
Menu

Documentation

Quest order, creature variants and calculators

Updated 2026-09-29

Keep the source IDs, then choose how readers see the records.

Quest objectives in order

Diagram: objectives on parallel branches can share a stage. A stage groups dependencies; it does not prescribe the order of independent branches.
  1. Import the verified stage and predecessor IDs with the objectives. Wikily does not infer graph order from the imported rows.
  2. In the quest shared layout, select the objectives Table. Set its rows to come from a Lua Formula variable, or click the script name if one is already connected.
  3. Choose Edit source. Filter by the bound quest ID, then sort by the numeric stage. Give same-stage rows a consistent display order.
  4. Show unverified order separately. Records marked unreachable are not reached from the quest's start in the exported graph; retain them in the data for review.

File row order is not quest order. After a game update, regenerate stages from the quest graph instead of renumbering objectives by hand.

One creature, several variants

CatalogOne card per creature, with its portrait and range of levels.
Creature pageA comparison of the variants and links to their detail pages.
Variant pageThat record's exact stats and loot. Its existing URL stays useful.
Diagram: stored member IDs connect the family to its variants even if a name or level changes.
  1. Create a family dataset with one row per creature and a JSON list of member IDs. Keep a persistent slug in both family and variant rows; preserve it after renames.
  2. Point the overview Catalog at that dataset.
  3. In its shared layout, add the Related block using the settings above.
  4. Generate family pages with stable slugs. Keep each variant's own page and loot links.

A calculator readers can change

Diagram: input blocks update the formula on the page. The inputs, formula and result are all editable in the normal page editor.
  1. In the page's Variables & Scripts panel, add a Reader input for each value.
  2. Add a Formula, choose Lua script, and enter the game's verified calculation.
  3. Add Reader input blocks and a Text block showing the result token.
  4. Preview a minimum, a typical build and a value near a rounding boundary.

Embeds accept supported providers. If an external calculator's host is rejected, a native calculator gives readers the same inputs and leaves its logic editable here.

When the game updates

Same source IDRefresh the record. Preserve its slug, page binding and media reference.
New variantAdd its ID to the family membership, upload its render and generate its detail page.
New quest objectiveRebuild the graph stages and predecessor links before refreshing objectives.
Missing or renamed IDReview the match and URL deliberately. Do not replace it by matching a display name.
Unknown graph or formulaLeave the order or result unverified until the new behavior is established.

Open the dataset's Updates tab, select Update this dataset from a file, review the field mappings and apply the update. Applying it saves the dataset immediately. Then check a changed record, a new record and a family comparison on the affected pages.

For script controls and examples, see Variables & Scripts and Writing Lua scripts.