Skip to content

Getting Started

Requirements

  • Windows 10 or 11.
  • An EVE Online account (you'll authorize characters via EVE's official Single Sign-On).

Linux builds are planned for the 1.0 release. Today the app is built and tested on Windows (net9.0-windows).

Download & install

Grab the latest build from the project's Releases page. The links below always point at the newest release, so they don't go stale:

Both are the same app and both keep themselves up to date automatically (see below), so which you choose is a matter of preference — the installer if you'd like it integrated into Windows, the portable ZIP if you'd rather keep everything in a single folder you can move or delete.

Your data is stored locally at %LOCALAPPDATA%\EveConsole\EveConsole.db. Nothing is uploaded anywhere — the app talks only to CCP's ESI API to refresh your data.

Staying up to date

You normally won't need to download the app again. Whether you installed it or run the portable build, EVE Console checks for updates on startup and once an hour, and when a new version is available it prompts you inside the app — accepting downloads the update and restarts to apply it. Declining won't nag you again until the next version.

You can manage this under Settings (the ⚙ gear button, top-right) → Updates:

  • Automatically check for updates — on by default; untick to only check manually.
  • Current version / Latest version — what you're running vs. what's available.
  • Check Now — check on demand.
  • Update Now — appears when an update is available; downloads and restarts.

Note

Automatic updates apply to the released builds (installer and portable ZIP). Only a build you run from source can't self-update — the Updates tab shows "n/a — not an installed build," and you update it by pulling and rebuilding.

Building from source

If you'd rather build it yourself (or want to contribute), you'll also need the .NET 9 SDK:

git clone https://github.com/kernoeve/EveConsole.git
cd EveConsole
dotnet restore
dotnet run

A dotnet run build doesn't self-update — git pull and rebuild to get newer changes.

Building a self-updating package

If you want a packaged, self-updating build from your own checkout — the same kind of installer/portable the downloads produce — run the packager the release pipeline uses (Velopack) yourself:

  1. Install the Velopack CLI (pinned to the version CI uses):

    dotnet tool install -g vpk --version 1.2.0

  2. Publish a self-contained Windows build. Use a version number — matching the latest release (or the VERSION file) is a good default:

    dotnet publish EveConsole.csproj -c Release -r win-x64 --self-contained true -p:Version=0.9.5 -o publish

  3. Pack it with Velopack. Keep --packId EveConsole so the updater recognizes the project's official releases:

    vpk pack --packId EveConsole --packTitle "EVE Console" --packVersion 0.9.5 --packDir publish --mainExe EveConsole.exe

The installer (EveConsole-win-Setup.exe) and portable ZIP appear in the Releases folder. Run either and you have a Velopack-managed build that self-updates exactly like an official download.

A self-updating source build tracks the official releases

Because it checks the project's GitHub releases, a locally-packed build will update itself to the next official release, replacing your custom build. That's fine if you just want the latest source as a self-updating app, but your local changes get overwritten when a new release ships. For ongoing development, stick with dotnet run and git pull.

First launch

The first time you launch EVE Console, it starts downloading the EVE game data it needs (the Static Data Export and Hoboleaks data) in the background. A short Welcome dialog explains this — item lookups, market pricing, and industry tools fill in over a few minutes as the download completes, and you can watch progress on the SDE tab in Settings.

Click Get Started on that dialog and the Settings window opens automatically on the ESI Tokens tab. That's where you authorize your characters and corporations — click Add Character to log in your first character through EVE's Single Sign-On, as described next.

You can reopen ESI Tokens any time from Settings (the ⚙ gear button, top-right); it's the first tab.

Managing ESI tokens (characters & corporations)

Everything the app knows comes from ESI tokens you authorize. Manage them under Settings ▸ ESI Tokens, which has a Characters list and a Corporations list, each with Add, Update, and Remove buttons.

Adding a character

  1. Under Characters, click Add.
  2. Pick which scopes (permissions) to grant — they're grouped by category. Only the data you grant can be pulled.
  3. Continue to EVE's SSO page in your browser and authorize the character.
  4. The character appears in the list with its status and granted scopes. Selecting it shows when it was last authenticated and exactly which scopes it has.

Update re-runs the SSO flow for the selected character — use it to add or change scopes, or to refresh an expired token. Remove deletes that character's token and data.

Adding a corporation

  1. Under Corporations, click Add.
  2. Pick the corporation scopes to grant.
  3. In the browser, log in as a character who holds the required corporation roles (Director / Accountant) — corporation ESI data isn't available without them. The app uses that character only to resolve and authorize the corp; the corp's token is stored on the corporation itself.
  4. The corporation appears in the list (ticker, name, status).

Personal corporations

A corporation you own is a personal corporation — its activity and assets should count as yours. Select a corp and tick Personal Corporation to mark it (a gold dot flags personal corps in the list).

What 'personal' changes

Personal corps count toward your individual net worth, and their activity and assets are treated as part of your own. Alliance or employer corporations — ones you've added for visibility but don't own — are treated as separate entities and are kept out of your personal totals.

How data stays fresh

While EVE Console is running it performs background ESI pulls on a schedule. Most screens update automatically as new data arrives, so you can leave it open in the background. Some data (like market price history) is cached and refreshed on longer intervals to respect ESI limits.

Most tools depend on a little configuration first:

  1. Configure a market so the app knows where prices come from.
  2. Set up an industry park so build costs and the Production Calculator are accurate.
  3. Optionally, set up the AI agent.