NIKKE LabGuidesv2026.10.18-58d4dd43
ImportOpen simulator

Guides

Guides and reference

Find instructions for simulator setup, comparisons, account data, results, and troubleshooting. Account importing is optional.

Look for the ? buttons beside settings and results. Hover or focus to read, click or tap to keep help open, and press Escape or tap outside to dismiss. Essential warnings stay visible beside the controls.

Simulator workflow

Setup, simulate, compare, audit

Use the same target and assumptions when comparing two setups.

  1. 01

    Setup

    Choose the squad, target, timing, and loadouts.

    Open related guide
  2. 02

    Simulate

    Run the scenario and review warnings.

    Open related guide
  3. 03

    Compare

    Pin a reference, change one variable, and rerun.

    Open related guide
  4. 04

    Audit

    Use Timeline, Event log, Burst audit, and Damage audit.

    Open related guide

Common tasks

Choose what you need to do

Each shortcut opens the relevant guide or reference section.

UI

Choose a unit investment

Use Investment Lab results to plan OL, skills, cubes and dupes.

01

Run a first simulation

Set a squad and target, then complete a baseline run.

02

Compare two setups

Change one variable and review the completed-run deltas.

03

Explain a damage result

Find one hit in Event log and inspect it in Damage audit.

04

Import account data

Import your roster online or use a local Account Service capture. This is optional.

05

Plan a co-op lineup

Compare player-owned builds for a fixed five-unit team.

06

Fix an unexpected result

Check warnings, assumptions, and common setup errors.

Guide library

Browse by task or feature

Search the full list or narrow it by audience and category.

21 guides

Start here

Simulator setup

Results and analysis

Account data

Team planning

Mechanics

Troubleshooting

Quick reference

Core workflows

These notes cover the steps users need most often.

01 · First simulation

Complete a baseline run

  1. Choose the five squad slots and confirm Burst availability and order.
  2. Keep Union Shooting Range for the default baseline, then check duration, target DEF, and element.
  3. Review each unit's stats, skills, cube, doll, and Overload lines.
  4. Run the simulation and resolve any warning that affects the intended comparison.
  5. Choose Use current run as reference before changing the setup.
Read the detailed guideOpen the simulator

02 · Results and auditing

Move from totals to one event

  1. Use Summary to compare team damage, unit damage, DPS, share, and Burst counts.
  2. Use Damage breakdown to see how much each normal attack, skill, Burst, or secondary source contributed.
  3. Use Timeline and Burst audit to check application time, duration, and stack count.
  4. Filter Event log to the unit and damage source, then open Damage audit for the exact hit.

Under each buff contribution, Triggered by identifies the event that applied it. Expand Recorded trigger chain to follow causes such as Helm healing Crown and activating Royal Attire, or entering Full Burst. Refreshes, stacks, and duration adjustments identify their latest recorded cause for that hit.

Damage-audit what-if changes apply only to the selected hit and do not rewrite the scenario total.

Read the Scenario Compare guide

03 · Troubleshooting

Check the scenario before the formula

  • Confirm the target preset, DEF, element, duration, core, range, and accuracy assumptions.
  • Check squad order, Burst availability, cooldowns, skills, cube, doll, and every edited Overload line.
  • Rerun after edits; a prior completed result does not update itself.
  • Check whether the unit or mechanic is verified, assumed, provisional, or excluded.
Ask in the Discord community

Optional account data

Import account data without re-entering every build

NIKKE Lab Account Service is the official import method. When online import is available for your account, sign into NIKKE Lab with Discord and paste your official ShiftyPad profile link in Import online. Choose the live account level, level 400, or a custom level, then review the proposed changes before applying or saving them. No setup or JSON download is needed for online import. Targeted imports allow 60 accounts per ten minutes; full rosters and unusually large selections have separate allowances. The panel shows remaining allowance and automatically waits through cooldowns. Matching builds from this tab can be reused for 15 minutes; choose Refresh from ShiftyPad when you need new data.

Online capture requires both ShiftyPad roster and outpost sharing to be visible to everyone. NIKKE Lab processes the account data on its server and returns a sanitized snapshot directly to your browser. Captures are not saved to a cloud Library unless you explicitly choose to sync them. The import screen shows whether the hosted connection is ready.

Local capture remains available: run Account Service, sign into its separate Chrome window, capture your roster, and choose Import captured JSON in NIKKE Lab. For Co-op local capture, choose Custom level 40 and enter the character codes shown in the workspace. Co-op online import selects level 40 and requests only the chosen NIKKEs automatically. Existing saved snapshots and compatible JSON files remain usable.

In Account Library, choose Add account data to import a JSON file or capture online without leaving the page. Review the account and choose Save to Library. To refresh an existing snapshot, select it and choose Update account data, then Update selected account. This replaces its roster while keeping its saved name and identity. Older or smaller captures require confirmation; different accounts or stat profiles must be saved separately. These saves persist on this device. Choose Sync now to carry them to your Discord Library and other devices.

Account import & setupRead privacy notesOpen Account Library

Optional cloud Library

How cloud sync works

Discord sign-in is optional. The local Library and simulator continue to work without an account, and nothing uploads until you choose a first-sync action.

01 · Connect

Sign in from Account Library

  1. Open Library and choose Sign in with Discord.
  2. Discord opens in the current tab. Authorize the connection there, and Discord returns you to the Library when sign-in finishes.
  3. Discord requests only the identify permission. Keep the sign-in in the same browser tab until NIKKE Lab returns.
  4. After sign-in, return to Library and choose how the browser should join the cloud Library.

Discord sign-in is used only for the private cloud account. NIKKE Lab stores only the Discord user ID, current username, and optional global display name; it does not retain Discord access or refresh tokens. Sign-in does not import game data, grant bot access, or upload a Library record by itself.

02 · First sync

Merge or use the cloud copy

  • Merge both libraries keeps local-only and cloud-only records. Exact matches link automatically; different versions and cloud deletion markers wait for a choice.
  • Use cloud and replace this device verifies every cloud body before changing local storage, then replaces saved Library records in that browser. If a local write fails, NIKKE Lab attempts to restore the local records backed up in memory.
  • Download backups before using the replacement option when local records are important.

03 · Later changes

Use Sync now after editing

Local IndexedDB remains the working copy. After saving, renaming, or deleting snapshots or setups, return to Library and choose Sync now. Offline changes stay local until a successful sync.

If both copies changed, NIKKE Lab uses record-specific actions such as Upload device version and Download cloud version. If one side was deleted, the buttons explicitly say which local or cloud copy will be restored or deleted and ask for confirmation. The service does not silently choose one.

After a record is linked, deleting it locally or in the cloud propagates only when you explicitly choose Sync now, unless the other copy also changed. Those cases become conflicts instead of silent deletions or restoration.

04 · Export and delete

Know which copy an action affects

  • Signing out stops access on that browser and keeps both local and cloud records.
  • Export all cloud records downloads the active synced records for the signed-in account.
  • Delete cloud Library removes cloud copies but leaves that browser's local records. Sync pauses afterward so those local copies are not immediately uploaded again.
  • Delete cloud account removes the identity link, sessions, and active cloud Library; local copies remain.
Read the complete storage and privacy notice

Questions and reports

Send the right details to the right place

Use Discord for workflow questions. For a reproducible product bug, include the page, browser, steps, expected result, actual result, and any visible error message. Do not send account-export JSON, passwords, cookies, access tokens, or other credentials.

Ask in DiscordReport a product bugReport a security issue

Mechanics status

How implementation confidence is labeled

Read the label beside a mechanic before using the result as evidence.

Verified
Confirmed by repeatable testing or a reliable public source.
Assumed
A reasonable model used where exact behavior is not yet confirmed.
Provisional
Implemented from partial evidence and subject to revision.
Excluded
Not included in the current simulation.
Read methodology and known limits