Guide · ULTIMATE 9

init() ULT 9: a settled card, an assist-free run

kamome sano's init() is the second A Past Best Untold ULT 9 logged here, and its source is the cleanest of this set's three runs: the result card has finished counting — SCORE 096'898'239, the Rank box lit AA, the game's own First Clear tag printed under the IOTA row — and no assist wording appears in any frame. The chart holds 1,273 judged notes (EXACT 1,145 + 68, NEAR 41, BREAK 19), which the community wiki's chart table matches digit for digit. MAX LINK 374 against only 19 BREAKs gives the shape of the dive: one long chain taken through the wide field beams that name this rung. Twelve frames below follow it from the pre-dive card to the settled result, each deep-linked to its second.

Songinit() — kamome sano
DifficultyULT 9 read on screen · MIN 2 · EVO 5 · FBD 11 (community wiki — the rail is never in shot)
ULT 9 notes1,273 — EXACT 1,145 + 68 · NEAR 41 · BREAK 19 (frame count, matched digit for digit by the community wiki)
The runFirst clear 096'898'239, rank AA · MAX LINK 374 · MISS GAUGE 15 · assist-free

Sources

Frames come from TrappyTheDemon's [In Falsus Sightread] init() - kamome sano | ULT 9 (177 s, and the upload has no subtitle track), so nothing here is taken from commentary — every figure is read off the game's own screens at the seconds the steps link to. Why this card is quotable: its SCORE box has finished, and 096'898'239 appears identically at t=158 on the frozen HUD, in SCORE, and in the full-amount DIFFERENCE row beside an empty HIGH SCORE box, with the Rank box lit AA. A check frame at t=170 still reads 096'061'062 with an empty Rank box, which is what proves the later reading is final. Community-wiki data, not frame reads: MIN 2 / EVO 5 / FBD 11, the tap / hold / field / flick split (184 / 280 / 632 / 177), the FBD 1,469 count, 180 BPM and the Arcaea original credit — https://infalsus.miraheze.org/wiki/Init(), checked 2026-09-22; this film never shows the difficulty rail. Score, MAX LINK and Miss Gauge are single-source, from an assist-free run. The recorder's PKTR LIVE badge rides the left edge of four frames, never over a number panel; the frames are unmodified.

Card, field, CONNECT overlay

  1. 1

    The rung, straight off the card

    init()'s pre-dive card reads 9 above DIFFICULTY ULTIMATE with ILLUST credited to そゐち — a kana spelling low resolution likes to mangle — and that 9 is repeated on the pinned HUD card and on the jacket's corner badge in the result screen. HIGH SCORE is a dash, so this account had never dived it, and the encounter line already names the pairing the run will close: STORY ⇄ TOKIO.

    DIFFICULTY ULTIMATE 9 with a dash in HIGH SCORE on init()'s In Falsus card, jacket credited to そゐち
    ULTIMATE 9 with no score on file, jacket by そゐち.Watch at
  2. 2

    SPEED 7.00 over six lanes

    The highway loads at 000'000'000 with the song card pinned — init() / kamome sano, ULT 9, SPEED 7.00. Four key lanes carry A S D F, and the side rails read Umschalt and Leer on this German client. On a chart this wide, scroll speed is the first real decision: slow it down and the field beams stop being distinguishable from the taps underneath them.

    The highway is bare for init() ULT 9 in In Falsus: A S D F keys, a Leer side rail, SPEED 7.00 on the song card
    000'000'000: A S D F, German side rails, SPEED 7.00 on the card.Watch at
  3. 3

    CONNECT, with the deck out of reach

    The CONNECT overlay sits over the field with its card row half-hidden behind the character art — enough to see that a full deck is loaded, not enough to name the cards, so this page lists none. Two things do read clearly: the STORY ⇄ TOKIO encounter tabs, and the absence of any Assist Mode Enabled line, which the particle-filled IOTA row on the result card later corroborates.

    No Assist Mode Enabled line appears on init()'s In Falsus CONNECT overlay, its loaded deck sitting behind the art
    A loaded deck behind the art — and no assist wording anywhere.Watch at

The first chains and the first NEAR

  1. 4

    Chain 36 inside twenty seconds

    The opening is generous: 002'799'144 with the chain already at 36 and one EXACT on the line. init() starts with room to breathe, and that is the trap — every one of the run's 19 BREAKs is collected later, while the long chains this chart is remembered for begin right here.

    Chain 36 arrives inside twenty seconds of init() ULT 9 at 002'799'144, one EXACT on the In Falsus line
    Chain 36 at 002'799'144 — the easy stretch of init() ULT 9.Watch at
  2. 5

    Two hold beams in parallel

    A violet hold beam and a cyan one run down neighbouring lanes at 015'989'131 with three EXACTs stacked on the line. Sustained notes in parallel are the chart's first real ask: one hand parked, one still moving. The community wiki puts 280 hold notes into this ULT 9, which is what those underlays add up to.

    Violet and cyan hold beams run side by side at 015'989'131 as init() ULT 9 stacks three EXACTs in In Falsus
    Violet and cyan holds side by side at 015'989'131.Watch at
  3. 6

    One NEAR, and where the chain went

    The chain has dropped to 16 at 036'416'096, with a NEAR sitting beside an EXACT — no direction tag on this stamp, so the frame says only that the press drifted off the window. init() finishes with 41 NEARs and 19 BREAKs, so early sloppiness like this is most of what the card will charge for.

    One NEAR beside an EXACT at chain 16 marks the early cost of init() ULT 9 in In Falsus, 036'416'096
    A NEAR beside an EXACT, chain reset to 16.Watch at

Mid-chart: wide beams, long chain

  1. 7

    The wide field beam

    At 045'810'389 a field beam covers nearly the whole highway and the chain is back up at 55. This is init()'s signature: full-coverage slabs that want a flat hand rather than a sprint — and the reason the chart reads as 632 field notes in the wiki's split, the largest single channel on the rung.

    A field beam spans nearly the whole In Falsus highway for init() ULT 9 at chain 55, score 045'810'389
    The signature sweep: one beam across almost every lane.Watch at
  2. 8

    Chain 173 and still climbing

    A violet field beam rides the right of the highway at 059'361'319 while the counter runs to 173, a lone EXACT under it. Two-thirds of the way through, the chain has not been touched since the reset at 16 — the 374 the card eventually reports is built in stretches like this one.

    Chain 173 rides a violet field beam at 059'361'319 deep into init() ULT 9, a lone EXACT on the In Falsus line
    Chain 173 at 059'361'319, one EXACT on the line.Watch at
  3. 9

    Flicks at chain 281

    Yellow flick arrows arrive over the beam work at 067'671'983 with the chain at 281 — the highest reading on film before the card's 374. Flicks are where a hold-weighted run usually snaps, since the stroke has to overshoot the lane while the other hand keeps a beam held; here the chain survives them.

    Yellow flick arrows appear at chain 281 on init() ULT 9 in In Falsus, climbing toward the card's 374 link
    Flick arrows at chain 281, score 067'671'983.Watch at

The settle, the encounter, the card

  1. 10

    The HUD stops at 096'898'239

    Last note spent, field empty, counter frozen at 096'898'239 with the chain at 119. That matches the result card's SCORE and its DIFFERENCE row exactly — the corroboration this page requires before quoting any final score, and the reason init() can be cited straight where the Hanabi log cannot.

    init() ULT 9 ends with the In Falsus counter already at 096'898'239, chain 119 over an empty highway
    The frozen HUD: 096'898'239, chain 119, empty highway.Watch at
  2. 11

    CONNECTED, the purple kind

    What crosses the emptied field in this cut is the purple CONNECTED banner, 096'898'239 still on the counter — the encounter half of the payout, closing at ENCOUNTER RESULT 000'052'436 on the card that follows. Worth naming precisely: no cyan DIVE CLEARED field banner appears in this footage, and the DIVE CLEARED line you can read is the small one printed inside the result card.

    Purple CONNECTED lettering rides the emptied init() ULT 9 highway at 096'898'239 in In Falsus, chain still at 119
    CONNECTED — the encounter banner, not the field-clear one.Watch at
  3. 12

    A settled card: 1,273 notes and rank AA

    Everything is counted and lit. SCORE 096'898'239, Rank AA, EXACT 1,145, a second EXACT row at 68, NEAR 41, BREAK 19 — 1,273 judged notes, the same figure the community wiki's ULT column carries. MAX LINK 374, MISS GAUGE 15, HIGH SCORE blank beside DIFFERENCE +096'898'239, and the game's own First Clear tag sitting under an IOTA row of six purple bonus drops rather than an Assist Mode banner.

    A settled init() ULT 9 card in In Falsus: 096'898'239, AA lit, 1,273 notes across four rows, First Clear tagged
    The card behind every number here — counted out, ranked, tagged First Clear.Watch at

FAQ

How many notes does init() ULT 9 have?

1,273, read off a card whose counter has finished: EXACT 1,145, EXACT 68, NEAR 41, BREAK 19. The community wiki's chart table lists the same 1,273 for this rung (https://infalsus.miraheze.org/wiki/Init()), so the total is corroborated rather than a lone reading. The split behind it — 184 tap / 280 hold / 632 field / 177 flick — is wiki-side: the card invites a click for the full breakdown and nobody clicks. The wiki's FBD 11 count of 1,469 has no frame evidence at all in this video, and neither does the ladder (MIN 2 / EVO 5 / ULT 9 / FBD 11), which never comes into shot.

Can this score be trusted — was the run assisted?

It is a clean record, as far as frames can say so. The result card's IOTA row shows six ordinary purple BONUS drops (each reading 177 x3) rather than the ASSIST MODE banner another log in this set prints, and the CONNECT overlay carries no Assist Mode Enabled line. With the score counted out, the Rank box lit AA and a First Clear tag on the card, 096'898'239 stands as an unassisted first clear. What stays single-source is the score itself: one filmed run, no second recording to compare it against.

What makes init() ULT 9 hard, and what does the run use?

Coverage rather than finger speed. The chart's weight sits in wide field beams and parallel holds — 632 field notes on the community wiki's count — so a flat hand and a stable reading position pay off more than alternating fast. Only 19 BREAKs against a MAX LINK of 374 says the run keeps its chains and pays for the stray NEARs instead (41 of them), finishing with MISS GAUGE 15 intact. This run uses SPEED 7.00 with a full CONNECT deck and the STORY ⇄ TOKIO encounter.

Where does init() come from, and how do you unlock it?

Two things are on screen: init() sits in the same A Past Best Untold selection as Hanabi, jacket credited to そゐち, and this dive closes on a CONNECTED encounter banner. Everything else is community-wiki data — an Arcaea original first released 2022-01-20, reached through the arc's story node — and our songs table files it the same way, as an Act 2 story-progress song. This page does not claim to have frame-verified the unlock step, and the video itself never states one, so treat the condition as a wiki claim.

Written for infalsustips.com from our own demo testing and community research. Fact-checked against: In Falsus Wiki (Miraheze) (CC BY-SA 4.0) · In Falsus Wiki (Fandom) (CC BY-SA)

Data reflects demo v0.3.1 · being re-verified on 1.0 · Unofficial fan site — In Falsus © lowiro