Documentation

Find the answer.
Get back to camp.

Clear guides for setup, reports, character storage, triggers, and troubleshooting.

01

Start here

Your first session

Shiba Max reads supported local files and keeps setup on your PC. It does not need your EverQuest password or a cloud account.

  1. 1
    Install Shiba Max

    The signed public installer will be linked from the home page after clean-machine testing is complete.

  2. 2
    Turn on EverQuest logging

    Shiba Max needs the native combat log for fights, casts, heals, rewards, zones, and trigger messages.

  3. 3
    Select a character

    The app pairs that character's log with saved hotbuttons, socials, window layout, and other supported configuration.

  4. 4
    Follow Guided setup

    Guided setup checks the app profile, local files, logging, abilities, layout, and live readings in order, then resumes from the first step that still needs attention.

  5. 5
    Watch the reading status

    Each reading shows where it came from, when it was updated, and whether a refresh is needed.

My Companion dashboard

Choose Companion guardian, Camp watch, Performance, or Minimal watch; pin and order up to twelve signals; choose Comfortable, Compact, or Glance density; and set text size, contrast, motion, and keyboard-focus preferences. Health, mana, and companion-health cards show a recent mini trend after three readings, while Chronicle goals add a progress bar. Preferences stay local to the selected character and server. They do not copy values, logs, chat, screenshots, coordinates, inventory, or sharing consent.

Client Spell Library and cross-character planner

Search the installed spell library, compare saved /outputfile spellbook and /outputfile missingspells files, and keep private Need spell or Have scroll plans across characters. Each source shows when it was captured. The client's MissingSpells file may vary by server era or data quality, so Shiba Max does not use it alone to decide eligibility or need.

Reviewed Camp Library and community catalog

Save reviewed camp drafts with revision history, sign packages you publish, and browse owner-approved community releases. Every downloaded package receives an integrity, publisher, version, privacy, compatibility, and replay check before it opens for local review. Saving or reviewing a camp does not activate it or send game input.

Need help?

Download a privacy-safe support report from Guided setup. It includes the app version, setup status, reading age, and readiness counts. It leaves out character, server, companion, and target names; paths; combat lines; screenshots; chat; coordinates; and inventory. Review the JSON before sharing it.

02

Data and privacy

What the app reads

Read

Combat log

Damage, healing, casts, failures, deaths, experience, currency, loot, zones, and supported chat-trigger lines.

Read

Character and UI INI

Saved hotbuttons, socials, window positions, layout names, UI skin, and other configuration—not live inventory contents.

Optional

Native output files

Point-in-time inventory, spellbook, real-estate, and guild exports created by EverQuest commands.

Not used

Packets and memory

The Legends build does not capture network packets or inspect client memory.

Source rule

A file that describes how a window looks is not proof of what the window currently contains. Shiba Max keeps those facts separate.

Optional community research

Sharing is off by default. If enabled in the Windows app, only future completed-encounter aggregates are sent: damage, healing, attack, defense, casting, effects, NPC targets, duration, and outcome. The consent screen previews the exact JSON. Raw log lines, chat, tells, account/character/companion/server identity, screenshots, coordinates, packets, memory, local paths, inventory, and UI files are excluded. Sharing can be stopped, and a local deletion credential can remove that installation's contributed rows.

03

Character Vault & Chronicle

Storage and progression, without guessing

EverQuest can write a tab-separated inventory snapshot containing Location, Name, ID, Count, and Slots.

Run in EverQuest/outputfile inventory
Where is my item?

The Windows Vault searches every verified character snapshot by item name or ID, character, storage group, and snapshot age. Each result shows the character, server, exact exported location, quantity, and age. Missing or rejected character exports remain visible as coverage gaps.

What was in the guild bank?

Run /outputfile guildbank from the guild hall. The Windows Guild-Bank Explorer accepts only an exact default character/server filename with the reviewed Location, Name, ID, Count, and Permission columns. Search by item, ID, location, exported permission label, character, or age. Permission text remains an uninterpreted label, character snapshots stay separate, and no combined live guild total is claimed.

What will each character do with this item?

Loot Filter Studio reads native userdata/LF_<character>_<server>.ini files and compares Auto loot, Auto merge, Auto store, and Auto sell choices. It highlights differences, duplicates, and conflicts across characters. Native Copy Planner previews items found only in the source, only in the destination, changed in both, matching, or ambiguous before the player uses the EverQuest client's own Merge or Replace control. Search results leave out installation paths and raw file lines. Editing remains disabled while backup, recovery, client-restart, and clean-install tests continue.

Which needed scrolls are already in reach?

The private Spell Acquisition Board matches a character's spell plan with spellbook, missing-spell, inventory, and guild-bank snapshots, then organizes reviewed merchant, quest, autogrant, research, and historical drop routes. Each item shows its source and capture date so the player can refresh old information before acting.

What is current for each character?

Source Center shows which logs, inventory exports, guild-bank snapshots, spellbooks, missing-spell files, and saved UI files are available for each character and when each was updated. Its copy-only refresh list contains /outputfile inventory, /outputfile guildbank, /outputfile spellbook, and /outputfile missingspells; Shiba Max never sends those commands to EverQuest.

What progression did the log record?

Character Chronicle turns recorded skill gains, faction changes, and level-ups into searchable history. Filter 30 days, 90 days, or all scanned history by category, zone, or search text; compare daily and subject graphs with exact tables; and keep up to 24 private milestones for each character and server. Recorded skill values are not live caps, and historical levels are not presented as the current level.

ViewSourceWhat Shiba Max can verify
Equipped gearInventory exportSlot, item name, item ID, quantity, container capacity, and augments represented as nested worn-slot rows.
Carried inventoryInventory exportGeneral bag and nested bag-slot locations.
Personal and shared bankInventory exportBank location, nested container location, item identity, and quantity.
Dragon's HoardConditional inventory exportEverQuest documents that the Hoard window must be open when the export is created.
Real estate/outputfile realestateSeparate source. It is never inferred from the inventory file.
Guild bank/outputfile guildbankImplemented separate guild-scoped snapshot: item, ID, location, count, exported permission label, source character, and age. It does not establish live contents or authority.
Loot filtersNative userdata/LF_<character>_<server>.iniSaved item ID, item name, icon ID, reviewed action, source character/server, file age, duplicates, cross-file variation, and same-file conflicts. It does not establish current loot-window state.
Export boundary

The inventory file is a point-in-time list of owned item rows. The account-wide index stays local, omits installation paths and raw export text, and is never uploaded automatically. Shiba Max reports only fields present in each export and does not infer additional live character information from it.

04

Combat analytics

Understand what happened and what changed

Start with the question you care about, then open calculation details when you want the exact method.

DPS

How quickly you dealt damage while combat was active. Metric details show the exact combat window.

Hit rate

How often resolved swings landed. The breakdown shows misses, dodges, parries, blocks, and ripostes.

Average

The arithmetic mean. Large critical hits can pull it upward.

Median

The middle result after sorting. It is less sensitive to a few extreme hits.

Quartiles

The 25th, 50th, and 75th percentiles, useful for seeing the spread of ordinary results.

Buff uptime

How consistently an effect stayed active during the part of the fight Shiba Max could track. Coverage details show any gaps.

Session recap

Start with the story before opening the detailed charts. The recap brings together fights, kills, damage, healing, experience, currency, items, strongest contributions, survival, effect upkeep, casting problems, and accuracy signals. When you have chosen a camp benchmark, the same recap tracks companion survival, kill pace, and damage output against that trusted run. Compact recent-run charts show whether those results held across several sessions at the same camp, and every plotted run opens its saved Session Journal recap. Each comparison appears as soon as both runs contain enough recorded activity for that result. The recap calls out low hit rate only after at least five resolved attempts and clearly marks a fight that is still active.

Ability performance history

Find every observed spell and attack across saved sessions. Compare total results, cast and attack outcomes, effect uptime, and five-number plots for per-session DPS or HPS. Calculation details explain how session-level quartiles differ from individual hits and heals.

Progression & Loot Journal

Filter 7 days, 30 days, or all saved sessions by zone, enemy, item handling, or search text. Review experience, corpse coin, observed sale proceeds, item quantity, daily graphs, and rewards by enemy. Source details show the number of observed kills behind each result and distinguish observed sale proceeds from vendor, auction, or market value.

Session Journal

Search saved sessions by camp, zone, enemy, outcome, performance, notes, or tags. Camp history at a glance shows which camps have a benchmark, which have enough repeat results for trends, and the newest kills, damage, and companion survival before you open a recap. Sort your completed camps by companion survival, experience per hour, coin per hour, kills per hour, damage per second, or healing per second to find the highest recorded results for what matters to you. Run count, observed time, fights, and kills stay beside every ranked camp, and each result opens the full camp report. Open a camp report to see the total time, fights, kills, experience, coin, items, damage, deaths, and survival across every completed saved run at that exact camp, along with your strongest and most recent results. Compare two saved camps side by side for survival, kill pace, experience, coin, damage, and healing. Run counts, observed time, fights, and kills remain beside each camp so you can judge the rates in context, and a result that was not recorded stays marked as unavailable. Save the reviewed camp comparison as privacy-safe JSON or Markdown with one-way camp references and no local session IDs, character identity, or private notes. Save the whole camp report as JSON or Markdown with one-way run references and no character identity, private notes, or local paths. Open any result to revisit what happened, what worked, and what deserves attention; the same recap is included in one-session JSON and Markdown reports. Camp history follows the saved run you opened—even when it is not your newest camp—and lets you move between plotted recaps without changing your search filters. Compare the selected run with another to see what improved, what regressed, and what changed. Choose one trusted run as your private camp benchmark and Shiba Max will offer it first in future comparisons for that camp. Without a benchmark, Shiba Max offers the closest saved run from the same camp first. You can replace or clear the benchmark at any time without changing session history. Save the reviewed comparison as JSON or Markdown, star important runs, and save useful views. Comparison reports leave out character and server identity, raw logs, paths, screenshots, coordinates, packets, private notes, and tags. A one-session report includes private notes only when you explicitly choose that option.

Camp Atlas

Turn your own /loc samples into a private camp map with separate markers for idle positions, combat positions, encounter starts, waypoints, notes, and recorded paths. Start path recording, then use your /loc hotkey at meaningful turns. Shiba Max watches the resulting log lines; it does not press the key or move the character.

Camp Strategy Intelligence

Compare enemy variants, clean wins, failures, control use, hostile healing, positioning problems, cast results, effect loss, and death sequences from saved encounters. Comparisons appear after each side has at least three similar encounters. They highlight patterns to review, not proof that one condition caused another.

05

Trigger alerts

Match, explain, then alert

Triggers turn reviewed combat-log text into overlays, countdowns, sounds, or optional spoken notices.

Log lineScoped ruleCaptured fieldsThrottle checkOutput
  • Use exact or contains matching for simple rules.
  • Keep regular expressions disabled until reviewed and tested with a time budget.
  • Use the debugger to inspect scope, captures, throttling, and planned outputs without firing the rule.
  • Imported packs begin disabled and remain data-only.
  • Authors can sign original, tested rules with a passphrase-protected local publisher identity; recipients review every rule and output before importing it.
06

Updates and recovery

Publisher first, update second

The Windows Release Center makes trust visible before it offers any update action.

  1. 1
    Verify this installation

    Shiba Max checks its own Authenticode publisher, thumbprint, and trusted timestamp locally. An unsigned, invalid, or untimestamped build cannot contact the release channel.

  2. 2
    Check the stable channel

    Checking is manual. Prereleases and downgrades are disabled, and the available version is shown before anything downloads.

  3. 3
    Approve download and installation separately

    Download requires a native confirmation. Restart and install requires another confirmation after the updater verifies the candidate publisher.

  4. 4
    Keep local work recoverable

    Profiles, settings, and retained analytics stay in the Windows application-data folder rather than the replaceable program directory. Release Center can open that folder directly.

How releases earn public-ready status

Seven append-only Windows trials cover clean install, first run, overlay, observer-profile onboarding, signed upgrade, uninstall, and failed-update rollback. Every pass is bound to one exact installer hash and required sub-results. Failed attempts remain in the ledger. Compatibility records use Windows build, architecture, account class, VM/physical class, and display categories—never usernames, computer names, hardware IDs, paths, or game data.

Version 1.1.0 signed candidate

The exact signed 1.1.0 installer remains available from the Download page as a testing candidate. It is not public-ready while the version-and-hash-bound clean-install, first-run, overlay, onboarding, upgrade, uninstall, and rollback trial ledger remains incomplete.

07

Troubleshooting

Common fixes

No character appears

Confirm native logging is enabled and that the app is pointed at the same EverQuest installation that owns the character's log.

The inventory is missing

Run /outputfile inventory on that character. The Character Vault only associates files whose name is linked to the discovered character.

The bank looks old

The inventory file is a snapshot. Run the command again, then check the freshness label in the vault.

A loot-filter file is rejected

Loot Filter Studio requires the exact native header and four caret-delimited fields. It reports rejected files and malformed rows without attempting to repair or rewrite them.

A trigger does not fire

Use the trigger debugger. Check rule enablement, character/server/zone scope, pattern result, captured fields, and throttle state in order.

I need to report a setup problem

Open Setup, follow the current Guided setup instruction, then download the privacy-safe support report. Its support code identifies that setup snapshot without attaching logs or screenshots.

08

Visual guides

Built for screenshots and short tours

These prepared slots will become annotated walkthroughs as the installer and interface reach public-preview quality.

Dashboard tourScreenshot set
What is happening now, what needs attention, and the next useful action.
Character VaultShort video
Locate gear, compare native sources, and audit saved loot choices across characters.
Combat reportAnnotated chart
Damage ranges, healing, hit rates, and the events behind each result.