Luminary Build Notes Pad
Browser-saved notepad on this page — plan weapons, vendors, and co-op roles without leaving the wiki.
Build theory in Luminary spans three weapon families, use-based proficiency, four town vendors, and three-player co-op roles — too many variables to hold in working memory during Early Access balance patches. This page hosts a build notes pad UI below the article: a textarea for drafting loadouts, vendor spending order, meal prep plans, and Tier farm routes with save and clear controls storing text locally in your browser. No Steam login, no cloud sync, no automatic share to party members.
Use this pad alongside Builds Hub guides for mechanics and Vendors and Crafting for economic math. The notepad captures your personal plan; guides explain why the plan works.
How the build notes pad works
The notes component renders on this page with:
- Textarea — freeform markdown-friendly plain text for weapon focus, stat priorities, co-op assignments.
- Save control — writes content to local browser storage on this domain.
- Clear control — wipes textarea and stored copy after confirmation.
- Saved indicator — confirms successful local persistence.
Placeholder hint suggests entries like weapon focus, vendor order, and co-op role — matching typical Early Access planning needs. Locale translations apply to button labels when wiki i18n syncs; note content is yours alone.
Storage survives page reloads and browser restarts until you clear site data or click clear. Incognito sessions discard notes when the window closes. Different browsers on the same PC maintain separate pads.
What to record — melee, ranged, and magic
Primary weapon commitment — Sword and Shield anchor, Bow kiter, or Magic Glove breaker per Melee Build, Ranged Build, and Magic Build. Note proficiency time split from Proficiency — max one primary before mid-game secondary swap.
Swap triggers — write encounter-specific swaps: Bow status apply, glove shield strip, sword stagger finish. Cross-check timing with Combat Basics.
Weapon tier list snapshot — paste week-one impressions from Weapon Tier List and date them — Early Access patches rebalance Bow and glove cooldowns frequently.
Vendor and gathering plan
Document spending phases mirrored in Vendors and Crafting:
- Blacksmith primary +1 before secondary weapons.
- Chef meal recipe tied to next Tower damage type.
- Armorer weakest slot if dying to trash.
- Arcanist interrupt or mobility purchase.
Add gathering routes — Tuesday mining cliffs from Mining, Wednesday hub pier fishing from Fishing — so town nights stay scheduled.
Co-op role sheet
Three-player online drop-in co-op benefits from written roles before session start:
| Player | Weapon | Job |
|---|---|---|
| Host | Sword and Shield | Anchor, navigation |
| Guest A | Magic Glove | Break shields, interrupt |
| Guest B | Bow | Status, elite snipe |
Note voiceless drop-in etiquette from Roles and Party Tips — e.g., guest joins mid-camp and follows host ping colors. Shared progression rules from Shared Progression belong in notes when your group agrees on communal ore deposit.
Map and session goals
Link notes to compass targets from Map Hub:
- This week: outer camps toward northeast Tower.
- Life Tree rescue before Tower interior.
- Stockpile ore for post-endboss Tier attempt in Hall of Heroes and Endgame.
Session goals prevent idle OpenZone wandering that burns Chef meals without vendor payoff.
Tier and endgame planning
After campaign boss, Tier difficulty remixed familiar geography — notes should track:
- Comfortable Tier ceiling before frustration.
- Meal buff required at Tier 2+.
- NG+ intentions if restarting narrative per Hall of Heroes and Endgame.
Patch days: append dated balance observations rather than overwriting — history helps when Refractive adjusts break bars.
Sharing notes outside the pad
Copy textarea content into Discord, Steam chat, or email for party sync — the wiki does not push notes to other users. Screenshots work for mobile players referencing desktop drafts. For launch prep tasks with checkboxes, use Launch Checklist instead of freeform notes.
Privacy and data hygiene
Notes may include friend Steam names or schedule info — treat saved browser data as local-only sensitive scratch space. Clear pad before selling hardware or sharing browser profiles. Wiki maintainers cannot read your stored notes.
Example note template
Primary: Bow — proficiency focus
Secondary: Magic Glove @ tier 2 mid-game
Vendor: Blacksmith +2 bow, Chef crit meal, Armorer chest
Co-op: I snipe elites; host tanks; guest strips shields
Next map goal: clear west camps → Life Tree → Tower scout
Tier cap goal: Tier 2 after campaign boss
Patch 2026-08-15: glove cooldown feels shorter — retest break phaseAdapt freely — the pad accepts any plain text structure.
When notes beat guides
Guides teach community consensus; notes capture your group’s agreements and your proficiency experiments. Update notes after demo sessions (Demo Review) and first Early Access weekend; revisit Early Access Roadmap when new weapons or map regions invalidate old routes.
Scroll below this article to use the build notes pad UI — save often before closing the tab.
Build notes pad
Draft weapon loadouts and town priorities — saved in this browser only.
Frequently Asked Questions
Quick answers to the most common Luminary questions.
Where is the build notes pad UI?
The notepad renders on this Build Notes page below the article — type, save locally, and clear when starting fresh.
Are build notes synced to the cloud?
No. Notes save in browser local storage on this device only. Copy text manually to share with friends.
What should I write in build notes?
Weapon focus, vendor spending order, co-op roles, map goals, and Tier targets — whatever your group needs to track.
How is this different from the launch checklist?
Checklist tracks fixed prep tasks with checkboxes. Build notes are freeform text for loadouts and session strategy.
Will notes survive browser updates?
Usually yes on the same browser profile until you clear site data or use clear on the pad.