README

A comprehensive mining management plugin for SeAT 5.x. Track mining operations, plan and manage moon extractions, and generate detailed reports for your corporation.

Maintained by Bahu90 as bahu90/mining-manager. Based on Mining Manager by Matt Falahe, released under the GPL-2.0. The PHP namespace, database tables, routes and permissions are unchanged, so an existing mattfalahe/mining-manager install can switch over and keep its data.

Standalone

Mining Manager works on its own. Install it, set your Moon Owner Corporation, and everything below runs on SeAT alone. It does not depend on any other plugin: no Manager Core, no Structure Manager.

Since 3.0.0 Mining Manager is a tracking plugin only. Mining tax, tax codes, invoices, payments, balances and theft detection have been removed; data recorded by earlier versions stays in the database but is no longer read.

Release history lives in the CHANGELOG.

Features

Moon / Anomalies / All -- One switch on My Mining, Mining Summary and each pilot's page picks what the figures count: Moon (moon ore: the refineries' own data, plus moon ore in pilots' logs that no refinery row covers yet; the default), Anomalies (ore, ice and gas from belts and anomalies) or All. When a pilot's log repeats what the refinery reported for the same day and ore, only the refinery row is counted. A bar shows the two side by side, and All adds Moon and Anomalies columns per pilot. The pick is remembered while you move between pages. The Dashboard counts moon mining only and names the anomaly total beside it.
Mining Ledger -- Automated processing of character and corporation mining data with daily summary aggregation. Personal mining is imported as whole days: SeAT keeps a day mined in several sittings as several rows, and the import adds them up. The scheduled import reads the last two days by mining date, so mining SeAT saves later than that is left out and days already summarised do not change.
Moon Mining -- Extraction tracking, ore composition, value estimation, jackpot detection (automatic + manual reporting), chunk arrival alerts. A chunk's ore follows the newest of the game's own notices, a moon with no scan in SeAT is valued from them too, and a chunk is priced for the last time when it fractures, so a finished chunk keeps the value it had. The Extraction Calendar shows three months at once as stacked per-month grids (week and list views a click away), each chunk badged with the tier of its moon worked out from that extraction's own ore, on EVE time. Past Extractions table with sortable/filterable DataTables view, structure column, status filter (expired/fractured/cancelled), and search — scoped to Moon Owner Corporation only
Moon Extraction Planner (Moon Manager / Director) -- A corp-internal coordination calendar at Moon Planner for staggering refinery pulls so a small crew isn't drowned by chunks landing together (chunks not mined promptly are wasted). SeAT can only read in-game extractions, so the planner is intent/coordination only — it never controls the structure. Gated by the standalone mining-manager.moon_manager ability (directors/admins included), which also opens Moon Analytics.
- Three months at once — the anchor month plus the next two as stacked grids, paged by prev/today/next, so a quarter (or a year, by paging) is visible in one place.
- Everything in EVE time (UTC) — the clock EVE's in-game structure scheduler uses. The add/edit form takes EVE time and shows a live "that's [time] your local time" confirmation; locked entries show both.
- Auto-fill from history — walks each refinery's cadence across the whole visible window (needs ≥2 past arrivals; median interval at ≥3) and places every occurrence not already covered by a real pull, an archived pull, or an existing plan, and never one closer than the refinery spacing to another pull on the same refinery. Refineries with too little history of their own fall back to the corp-median cadence (flagged as estimated). Spreads placements to honour the minimum gap.
- Re-anchor a recurring day — move a Monday moon onto Tuesday and it sticks; future projections chain off the moved slot.
- Minimum-gap guard — placing/moving a pull within the configurable gap (default 24h) of another moon's arrival raises a confirmation listing the clashing moons, enforced client- and server-side.
- Time between pulls on one refinery: two pulls on the same refinery closer than the refinery spacing (7 days by default, a setting kept in hours and shown in days) get a warning when one is placed or moved, in the blueprint preview, and in a Pulls too close together banner with a mark on each planned pull. An extraction takes at least 6 days and the next one can only start once the chunk is in. A warning, not a block.
- Locked in-game pulls — live/completed extractions and plans reconciled to a real extraction are marked with a lock and can't be edited; clicking one explains why. Archived pulls stay visible so a refinery whose chunk already arrived doesn't vanish.
- 30-minute dedup + off-plan detection — a plan and the real pull within 30 min are the same pull (plan hidden, no double render). Further apart but same cycle means the in-game timer diverged: the pull is flagged red, listed in a Scheduling mismatches banner, and a schedule_mismatch notification fires. Realign moves the plan to the time the drill was actually set for in game; Ignore keeps the plan's time and records that the pull went ahead off-plan. Both ask for a reason, both are saved to the change history with who did it, and neither moves later plans for that refinery.
- Refinery panel — every refinery with its cadence, last arrival, projected next pull, a coverage badge (Planned 2× / amber Not planned = skipped moon, counted across the whole horizon), and a highest-ore-tier badge (R4–R64). Uncovered refineries sort to the top.
- Blueprints — a repeating pattern of pulls (which refinery, which weekday, what EVE time) over one to eight weeks, laid onto the planner from any start date for as many cycles as you ask for. Editing a blueprint carries the change to the pulls it already wrote, leaving anything already pulling or already past exactly as it was. Applying can instead take over the weeks it covers, clearing everything else planned in them first, including days the pattern does not use, with the full list of what goes shown before you confirm. A refinery goes into a blueprint once, the picker is labelled by moon tier, and refineries that have been unanchored or destroyed are flagged and cleared out by one button. A refinery being unanchored, or with its moon drill unfitted, keeps its slots and pulls under a yellow warning mark, since both can change back. A refinery the corporation no longer owns has its planned pulls taken off the calendar by themselves once it has been missing on three sightings at least twelve hours apart, with a Refinery Gone notification for each.
- Final pulls: when a refinery is going to be relocated or unanchored, mark its last pull as final, either a planned pull or the extraction already set in game. Pulls planned after it are listed and removed once you confirm, nothing more can be planned after it, and Moons Need Planning and Moon Not Rescheduled leave the refinery out. When its last chunk arrives, Next Extraction Planned says that was the last pull. If somebody starts an extraction there anyway, the planner's webhooks are told. Resume normal operations on the refinery's card clears the mark. Only the planner shows any of this: the extraction pages members see are unchanged.
- Pulls more than 56 days ahead: the planner takes a pull any distance ahead. One further off than an extraction can run cannot be set up in game yet, so when the chunk before it arrives, Next Extraction Planned says when it can be started and posts again at that time (Next Pull Can Be Started), and Moon Not Rescheduled waits until then.
- Resend Next-Pull Notices: one button sends Next Extraction Planned again for every refinery whose chunk has arrived and whose next extraction has not been started, after listing them. Far pulls say from when they can be started; refineries it has nothing to send for are listed with the reason and left out.
- Moon tier on every pull — the calendar carries the same R4–R64 badge as the refinery cards, with the full refinery name and moon on hover. Today is picked out in amber.
- Change history — every create / move / delete / realign / ignore records who did it and the before→after times; auto-fill logs an aggregate entry. A History button shows the last 100 changes.
Extraction Simulator and Find Moons (Director / Admin / Moon Manager / Moon Finder, in the Moon Planner section) -- Simulate any scanned moon over 6 to 56 days with ore value, refined value, class and a quality rating against the scanned moons of its class, all priced from the price cache. Directors and admins also see what a Metenox Moon Drill on the moon would collect (the moon materials only, at 40%), before fuel. Find Moons searches every scanned moon by region, constellation, system, security band, class, moon ore share (the moon ores in the scan added together, not the whole scan), required ores, composition rules (R16 at least 20%), value range and quality, finds a single moon by name, marks the moons one of your refineries still sits on, the ones held by another corporation and the ones on your shared watchlist (any of which can be hidden), suggests better moons of the same class nearby, and exports the results to CSV.
Moon drilling rigs -- A Moon Drilling Stability rig on an Athanor, or a Proficiency rig on a Tatara, stretches a chunk's mining window from 48 hours to 72 (Tech I) or 96 (Tech II), and Mining Manager follows it everywhere it times a chunk; the 2 hour unstable tail after it stays. Which rig a chunk had is read from the auto-fracture time EVE gave it, so it works for any refinery and a later rig swap never changes a chunk already pulled. Each extraction keeps the rigs seen in its refinery's rig slots, the extraction page shows them with roughly how much ore a yield rig (Efficiency or Proficiency) added, a chunk's ore figures follow the newest of the four game notices that report them, and the simulator lets you try any fit, starting from what is fitted.
Metenox Cargo Readout (v2.0.1, director-only) -- New sidebar page showing what's currently in every Metenox Moon Drill's MoonMaterialBay owned by your Moon Owner Corporation (matches the Past Extractions table scope and the related notification). Per-drill cards with ore composition, quantity, m³ volume, percent-of-cargo bars, ISK valuation (the configured price provider and its fallback), structure state, solar-system name (joined from solar_systems.name with id-only fallback), and last-polled timestamp (yellow if stale > 2h). Per-drill bay fill indicator with color-graded progress bar (500,000 m³ Metenox MoonMaterialBay capacity, verified against SDE attribute 5693 and EVE Ref). Admin scope picker -- operators with mining-manager.admin get a dropdown above the chips listing every corp with at least one Metenox + an "All corps" aggregate option, defaulting to the same Moon Owner Corp view directors see (one-click "Back to Moon Owner" shortcut whenever off the default). Notifications still scope to Moon Owner Corp only, so admin's expanded read visibility doesn't generate extra alert traffic. Cargo Bay Full notification fires when a drill crosses the configurable fill threshold (default 85%, configurable 50-99%) — yield-stopping warning, dedup-latched against repeats while still over threshold, resets when cargo is pulled. Cron mining-manager:scan-metenox-cargo-fill every 5 min. Cross-plugin contract: PluginBridge capability mining.metenox.cargoSnapshot($structureId) lets Structure Manager render the bay on its structure detail page.
Ore classification -- TypeIdRegistry covers more than 540 type IDs, including the IV-Grade tier of all fifteen classic ores, the Exordium 0-Grade variants, the X-Grade families, Prismaticite, and the full gas colour sets. Event and quest ore (Tyranite, Nephrite, Volatile Ice and the rest of the limited-time and mission ore), all six Mutanite types and Zuthrine are not imported, valued or charted. Mutanite comes from permanent Homefront Operations content, but it cannot be reprocessed and often has no price, so counted it only sat in the ledger as regular ore worth nothing. Zuthrine can be neither sold nor refined. See How Ore Classification Works.
Mining Events -- Create events to track participation. Dedicated event_mining_records table materialises the exact mining activity qualifying for each event, with all four scope filters (corporation, location, time, ore category) applied at populate time, so only mining that actually overlaps the event window counts, not the whole day. Historical pricing preserved via proportional allocation from the mining ledger. Event create/edit forms have an EVE/UTC vs My local time input toggle with live confirmation box; server still always stores UTC.
Local time + live countdowns (v2.0.1) -- Every server-rendered EVE timestamp gets a hover tooltip with full local time formatted in your browser's timezone (same mechanism Discord / Google Calendar / GitHub use; DST handled automatically). High-priority surfaces (active extractions, upcoming events, calendar, my-events) opt into an inline " · HH:MM local" pill for at-a-glance reading. Carbon::diffForHumans() text replaced with 1-second-tick countdowns color-graded from green (>1d) to red+bold (<1h) on the relevant pages. Browser-TZ readout in Help & Documentation lets operators sanity-check what their browser reports.
Reports -- Daily/weekly/monthly reports with PDF/CSV/JSON export and scheduled Discord/Slack delivery
Moon Mining (second in the menu, after Dashboard) -- The month's moon mining at your refineries, laid out like the corporation website: ISK, volume, active pilots, the refineries mined at, and a pilot leaderboard, with belt and anomaly mining named beside it. Dashboard, first in the menu, has the all-ore dashboard with 12-month charts, leaderboards and statistics.
Analytics (Director; Moon Analytics also for Moon Managers) -- Opens on your own corporation, with All Corporations as a deliberate second choice. Performance Charts filter by source (all mining, my moons only, all moon ore, other moons only), ore category and player (picked by main, counted across every character that player mines on), and exports carry the same filters. Moon Analytics covers utilization, pool vs mined, per-extraction detail and ore popularity. Allow Data Export (Settings > Features) switches every export and download off for everyone, directors and admins included; the settings backup stays available.
Notifications -- 18 notification types via Discord, Slack or custom JSON webhooks, with per-webhook event toggles. Three moon-lifecycle notifications: Extraction Started (a refinery lit its drill, naming the pilot who started it and their main, read from the in-game MoonminingExtractionStarted director notification), Next Extraction Planned (fires after a chunk is ready, announcing the refinery's next planned pull from the planner so a director re-fires on schedule), and Moon Scheduled Off-Plan (the in-game timer diverged from the plan by more than the 30-minute tolerance — one ping per plan). Four more planner notifications: Refinery Gone (pulls taken off a refinery the corporation no longer owns, one message per refinery), Moon Extraction Cancelled (stopped in game before the chunk arrived, naming who), Moon Not Rescheduled (a drill left idle after its chunk arrived, repeating until an extraction starts) and Moons Need Planning (one list of refineries short of planned pulls, cut at 25 with the total). Only refineries with a moon drill fitted count, and both reminders leave out one that is gone, reported destroyed, or unanchoring with no extraction running. Extraction Started waits for the in-game notification to reach SeAT so it can name the pilot, and goes out without the name if six hours pass first. Directors can bind Price Provider Trouble, which says so once when price refreshes stop getting through and once when they work again. Moon Scan Missing lists the moons your refineries drill that have no scan in SeAT, which Mining Manager values from the game's notices until somebody scans them. The two sit in their own Plugin Health group, each with its own switch. (v2.0.1) Inline Discord role picker on every per-type role-id input (one-click pick from your installed Discord role source — SeAT Broadcast / SeAT Connector / legacy warlof tables). Notification Routing Map read-only Settings tab shows what fires where and who gets pinged at a glance, with "enabled but firing nowhere" warnings.
Character lookups -- Names and corporations for characters SeAT does not know, such as visiting miners, are looked up in the background by mining-manager:resolve-characters (ESI first, then EVEWho and zKillboard when ESI is down) and kept by the plugin. Every page reads them from there, so no page waits on ESI, and a visiting miner is named on every page and counted as a guest rather than shown as Unknown.
Diagnostics -- Multi-tab diagnostic suite. (v2.0.1) Default tab is now Health Checks (renamed from "System Status", reordered so the universal tabs come first). Tier 1 tabs each open with a "What this tab does / When to use / Heads up" intro box. Tabs: Health Checks, Master Test (one-click read-only smoke chain, including the personal mining import, moon notifications reaching SeAT, ignored ore reaching the ledger and mined ore the registry does not recognise), System Validation, Settings Health, Data Integrity, Notification Testing, plus plugin-specific traces and a DEV-only Test Data tab.

Requirements

SeAT 5.x
PHP 8.1+
MariaDB / MySQL

Installation

composer require bahu90/mining-manager
php artisan migrate
php artisan db:seed --class=MiningManager\\Database\\Seeders\\ScheduleSeeder

After installation:

Open SeAT and navigate to Mining Manager > Settings > General
Set your Moon Owner Corporation
Run the setup wizard to populate your data:

php artisan mining-manager:initialize

The wizard verifies your settings, populates current month data (prices, mining entries, summaries, extractions), and optionally backfills historical data for reports and analytics.

Switching from `mattfalahe/mining-manager`

Nothing in the database changes, so take a backup and swap the package. On SeAT Docker:

docker compose exec mariadb mysqldump -u seat -p seat > ~/seat-before-mining-switch.sql
# .env, SEAT_PLUGINS: replace mattfalahe/mining-manager with bahu90/mining-manager
docker compose up -d
docker compose exec front composer show | grep -i mining-manager   # only bahu90 should be listed
docker compose exec front php artisan migrate --force
docker compose exec front php artisan vendor:publish --tag=seat --force
docker compose exec front php artisan optimize:clear

If mattfalahe/mining-manager is still listed, remove it with docker compose exec front composer remove mattfalahe/mining-manager. No setup wizard is needed: settings and mining history carry over.

Configuration

Key Settings

Setting	Location	Description
Moon Owner Corporation	Settings > General	Which corporation owns the moon structures -- determines observer data scope
Price Provider	Settings > Pricing	Market data source (SeAT, Fuzzwork or Janice)
Fallback Price Provider	Settings > Pricing	Prices instead when the provider fails outright, for the same market and price type: Fuzzwork by default, Janice or none. Cached prices are kept when the fallback cannot help either

Moon Arrival Notification Architecture

Moon arrival notifications use two decoupled systems:

┌──────────────────────────────────────────────────────────────────┐
│  STATE SYSTEM (ESI-driven)                                       │
│  - update-extractions every 2h                                   │
│  - Pulls ESI and writes chunk_arrival_time, natural_decay_time,  │
│    fractured_at, status                                          │
│  - Answers: "what does EVE say is happening?"                    │
└──────────────────────────────────────────────────────────────────┘

┌──────────────────────────────────────────────────────────────────┐
│  NOTIFICATION SYSTEM (time-driven)                               │
│  - check-extraction-arrivals every 1 min                         │
│  - Reads stored chunk_arrival_time, compares to now()            │
│  - Answers: "has arrival time passed + unnotified?"              │
│  - Idempotent via notification_sent flag                         │
└──────────────────────────────────────────────────────────────────┘

ESI tells us WHAT is happening. The clock tells us WHEN to notify.

This decoupling means arrivals notify within ~60 seconds of the actual chunk arrival time regardless of ESI refresh timing or outages. The chunk_arrival_time is known the moment an extraction is first imported (days or weeks before arrival); the notification watchdog just compares it to the current time.

Cancellation handling: If a director cancels an extraction in-game before chunk arrival, EVE sends a MoonminingExtractionCancelled character notification. The state system detects this during its next ESI poll and marks the extraction as cancelled. The notification watchdog then skips it — no false "Moon Chunk Ready" alert fires at the originally scheduled arrival time. Moon Extraction Cancelled says who cancelled it on the webhooks that have it ticked, and a cancelled extraction stays cancelled and is left off both calendars.

Extraction Started: the pass in check-extraction-arrivals picks a new extraction up from the stored extraction_start_time, then holds the alert until the in-game MoonminingExtractionStarted director notification reaches SeAT, so it can name the pilot who started it, with their main when they are on SeAT. It looks again every 10 minutes, and if the notification still has not arrived six hours after the extraction started, the alert goes out without the name: a slow notification can delay the alert but never lose it.

How Ore Classification Works

Every row in the mining ledger carries an ore category, and the category decides where it is counted on the dashboards, analytics and reports. It is decided once, when mining is imported, the same way for character mining and for moon observer data.

flowchart TD
    ESI["EVE ESI"] --> SEAT["SeAT<br/>character mining and moon observer data<br/>stored exactly as received"]
    SEAT --> IMPORT["Mining Manager import<br/>character mining and observer mining"]
    IMPORT --> CLASSIFIER{"OreClassifier<br/>one policy point"}
    REGISTRY[("TypeIdRegistry<br/>single source of truth<br/>for mining type IDs")] --> CLASSIFIER
    SDE[("SeAT SDE<br/>invTypes, invTypeMaterials")] -.->|"verifies every ID exists"| REGISTRY
    CLASSIFIER -->|"event or quest ore, Mutanite, Zuthrine"| SKIP["Skipped<br/>never reaches the ledger"]
    CLASSIFIER -->|"moon R4 to R64, ice, gas,<br/>abyssal, triglavian, regular ore"| LEDGER["mining_ledger"]
    CLASSIFIER -.->|"type ID not in the registry"| UNKNOWN["Imported as regular ore<br/>and listed by the Master Test"]
    UNKNOWN -.-> LEDGER
    REGISTRY -->|"which type IDs get prices"| PRICES["Price provider<br/>SeAT, Fuzzwork or Janice"]
    PRICES --> VALUES["Ore values"]
    SDE -.->|"reprocessing yields"| VALUES
    VALUES --> LEDGER
    LEDGER --> SUMMARIES["Daily summaries"] --> CHARTS
    LEDGER --> CHARTS["Dashboard, analytics and reports"]
    SDE -.->|"type names"| CHARTS

Part	Role
`TypeIdRegistry`	The single source of truth: every type ID the plugin knows, grouped by family (moon ore by rarity, ice, gas, abyssal, triglavian, regular ore, the compressed forms, event and quest ore, Mutanite). Data only, no rules, and the one place to update when CCP releases new ore.
`OreClassifier`	The one policy point: whether a type is skipped, and which ledger category it gets. Both importers, the mining event tally, daily summaries, the dashboard and analytics all ask it, so they cannot disagree.
SeAT's SDE	Support only: type names, reprocessing yields for refined ore values and the reprocessing calculator, and `mining-manager:diagnose-type-ids --verify-db` to check every registry ID exists. It never decides a category, because moon rarity tiers and ledger categories are Mining Manager ideas and CCP's own groups do not line up with them.

Ledger category	Covers
`moon_r4` to `moon_r64`	Moon ore, by rarity
`ice`	Ice and compressed ice
`gas`	Harvested gas, fullerites included
`abyssal`	Bezdnacine, Rakovene and Talassonite
`triglavian`	The registry's Triglavian ore list
`ore`	Every other registered ore, including the Deep Space Survey and Ore Prospecting Array families

Left out entirely: event and quest ore (Tyranite, Nephrite, Dense Moissanite, Amethystic Crystallite, Hiemal Tricarboxyl Condensate, Volatile Ice, Veldspar Isotope), all six Mutanite types (77118, 77418 to 77421, 77524) and Zuthrine (28626), which has no market group and no reprocessing output. They are skipped at import and count towards no mining event.

Types the registry does not know are imported as regular ore rather than skipped. The imports only read recent days, so mining skipped while the registry was behind could never be brought back. The Master Test's Unrecognised ore types check lists any such type mined in the last 30 days, with its name from the SDE, so it can be added.

Older rows keep the category they were imported with until mining-manager:backfill-ore-types re-stamps them.

Permissions

4-tier permission model -- higher tiers inherit all lower tier access. Plus three standalone capabilities: view_all lets pilots read what directors read without changing anything; moon_manager grants the planner, Moon Analytics and Find Moons without requiring full director, and moon_finder grants Find Moons on its own.

Permission	Tier	Description
`mining-manager.view`	Base	Help page access
`mining-manager.member`	Member	View own mining data, join events, view moon schedules, report jackpots
`mining-manager.director`	Director	View all corp data, manage operations, analytics, reports
`mining-manager.admin`	Admin	Full control: settings, delete actions, API, diagnostics
`mining-manager.view_all`	Capability (standalone)	See all data, read-only: the corporation and guest miners on the Dashboard, every pilot on Mining Summary and Moon Mining, Analytics, the Moon Planner and blueprints (view only) and Metenox Cargo. Give it with Member. Reports and settings stay with directors and admins
`mining-manager.moon_manager`	Capability (standalone)	Access the Moon Extraction Planner (assign / move / auto-fill planned moon pulls, realign or ignore an off-plan pull), Moon Analytics, and the Extraction Simulator with Find Moons. Directors and admins also have this access.
`mining-manager.moon_finder`	Capability (standalone)	The Extraction Simulator and Find Moons on it: search every scanned moon by location, composition, value and quality. Directors, admins and moon managers also have this access. Moon Planner in the sidebar opens straight onto the simulator for them.

Artisan Commands

32 commands available, 18 schedules in SeAT's scheduler. The three every-minute jobs run together in one process through mining-manager:every-minute.

Operational Commands

Command	Schedule	Description
`mining-manager:every-minute`	Every minute	Runs check-extraction-arrivals, update-events and resolve-characters --requested in one process, so SeAT boots one PHP process a minute for them instead of three
`mining-manager:resolve-characters`	Every minute (`--requested`, inside every-minute) + every 10min	Look up names and corporations for characters SeAT does not know. Every minute it takes the ones pages have asked for, every 10 minutes the miners SeAT has no affiliation for. ESI first, then EVEWho and zKillboard, and it backs off while the error budget it shares with SeAT is low. `--stats` shows what the table holds
`mining-manager:process-ledger`	Every 30min (:15, :45)	Process corporation observer mining data
`mining-manager:import-character-mining`	Every 30min (:20, :50)	Import character mining from SeAT's ESI data, adding up the rows SeAT keeps for each day. Scheduled with `--days=2` by mining date, so mining SeAT saves later is left out. `--dry-run` shows what it would add or change without writing anything
`mining-manager:update-extractions`	Every 2h	Refresh moon extraction data from ESI (state system: what EVE says is happening). The same run sends Moon Extraction Cancelled, the Moon Not Rescheduled and Moons Need Planning reminders, Next Pull Can Be Started, Moon Scan Missing, and takes pulls off refineries confirmed gone (Refinery Gone)
`mining-manager:check-extraction-arrivals`	Every minute (inside every-minute)	Send Moon Chunk Ready once a chunk's stored arrival time passes, Moon Chunk Unstable before a chunk goes unstable, and Extraction Started. Each goes out once per extraction
`mining-manager:update-events`	Every minute (inside every-minute)	Auto-transition event status (planned→active→completed) with notifications, update participant data
`mining-manager:scan-metenox-cargo-fill`	Every 5min	Send Metenox Cargo Bay Full when a drill's bay crosses the threshold set under Settings, Notifications
`mining-manager:cache-prices`	Every 4h (:30)	Cache market prices from configured provider
`mining-manager:update-ledger-prices`	Daily 1:00 AM	Lock in daily session prices for mining entries
`mining-manager:update-daily-summaries`	Daily 1:30 AM	Safety net for non-observer mining data. Also removes personal mining rows from the last four days that your own observer already recorded, the same as `reconcile-personal-mining`
`mining-manager:generate-reports`	Day 9 of month 4:05 AM + hourly (scheduled)	Generate monthly report and process user-defined scheduled reports. Dedup guard skips if same period+type exists (use `--force` to override)
`mining-manager:recalculate-extraction-values`	Twice daily (6AM/6PM)	Update moon extraction values with current prices
`mining-manager:archive-extractions`	Daily 5:05 AM	Archive completed extractions older than 7 days
`mining-manager:detect-jackpots`	Daily 6:05 AM	Detect jackpot extractions + verify manual reports
`mining-manager:validate-lifecycle-integrity`	Daily 3:00 AM	Warns when a stored extraction status has drifted from what the lifecycle helpers compute; `--fix` corrects it
`mining-manager:finalize-month`	2nd of month 2:00 AM	Pre-calculate summaries for closed month
`mining-manager:calculate-monthly-stats`	2nd of month 3:00 AM + every 30min at :25/:55 (current month)	Dashboard statistics

Utility Commands

Command	Description
`mining-manager:initialize`	Guided first-time setup wizard -- verifies settings, populates current month, optional historical backfill
`mining-manager:backfill-ore-types`	Re-stamp ore classification flags on existing ledger rows. `--dry-run` reports every category movement first
`mining-manager:backfill-extraction-notifications`	Backfill ore composition from the Extraction Started notices for existing extractions, and price them again. A chunk already priced at its fracture is left as it is
`mining-manager:backfill-extraction-history`	Reconstruct moon_extraction_history from `MoonminingExtractionStarted` notifications. Recovers past cycles for structures that pre-date plugin install. Progress bars for both dedup and processing passes. Use `--dry-run` to preview, `--structure=ID` to scope to one structure. Automatically invoked during `mining-manager:initialize` (Phase 3 historical backfill)
`mining-manager:backfill-event-records`	One-off population of `event_mining_records` for events that pre-date the table
`mining-manager:reconcile-personal-mining`	Remove personal mining rows that your Moon Owner Corporation's observer already recorded in full, only where the quantity matches exactly. The nightly summaries run does the last four days; `--days` reaches further back and `--dry-run` reports without writing
`mining-manager:generate-test-data`	Generate test data for development/testing
`mining-manager:backup-data`	Export Mining Manager data for backup or migration
`mining-manager:restore-data`	Import Mining Manager data from a backup
`mining-manager:diagnose-prices`	Diagnose price cache health and market data
`mining-manager:diagnose-affiliation`	Debug character corporation affiliations
`mining-manager:diagnose-character`	Debug character mining data and imports
`mining-manager:diagnose-extractions`	Debug moon extraction data and notifications
`mining-manager:diagnose-type-ids`	Debug ore type ID classification

Webhook Notifications

17 notification types across 4 categories (plus Metenox Cargo Bay Full, documented elsewhere). Each webhook can independently toggle which events it receives.

Supported channels: Discord, Slack and custom JSON webhooks, plus a single Slack channel under Settings, Notifications. EVE Mail is not available as a channel.

Category	Events	Description
Moon	arrival, jackpot, chunk-unstable, extraction-started, next-planned, schedule-mismatch, refinery-gone, extraction-cancelled, not-rescheduled, needs-planning	Chunk ready, jackpot detection, capital safety warnings (~2h before chunk goes unstable), drill lit (Extraction Started, naming who started it), the planner's next-pull nudge (Next Extraction Planned, which also says when a pull planned more than 56 days ahead can be started), off-plan scheduling alerts (Moon Scheduled Off-Plan), pulls removed from a refinery that is gone (Refinery Gone), extractions stopped in game (Moon Extraction Cancelled), idle drills (Moon Not Rescheduled) and refineries short of planned pulls (Moons Need Planning)
Events	created, started, completed	Mining event lifecycle
Reports	generated	Scheduled report delivery
Plugin Health	price-provider, moon-scan-missing	Price refreshes failing or working again (Price Provider Trouble), and moons your refineries drill with no scan in SeAT, valued from the game's notices until they are scanned (Moon Scan Missing)

All dispatch goes through a single NotificationService (consolidated from the previous two-dispatcher design) with 5xx/429 retry, per-type master toggles, per-channel filters, and per-webhook subscription gating. Webhooks are routable to a corporation (moon/events) or global (events/reports).

Diagnostic Testing

Mining Manager → Diagnostic → Notification Testing provides three test modes for verifying webhook configuration:

Mode	Scope	Purpose
Preview Test	One webhook (selected or custom URL)	Check embed layout + single-webhook wiring — renders without writing to audit log
Fire Live Notification	Full pipeline, one type, all subscribed webhooks	End-to-end verification for one specific surface. Respects corp scoping + all gates. Writes audit log.
Fire ALL (Chain)	Full pipeline, every fire-able type sequentially	Post-deploy smoke test — every subscribed webhook receives every type in well under a minute

Settings → Webhooks → Test button sends a minimal "✅ Webhook Active" ping for wiring verification.

Support

Issues: GitHub Issues
Wiki: Documentation & Screenshots
In-App Help: Full documentation under Help & Documentation in the plugin's sidebar

License

GNU General Public License v2.0 -- see LICENSE for details.

EVE Online and the EVE logo are the registered trademarks of CCP hf. All rights are reserved worldwide.

Development

composer update
vendor/bin/phpunit

GitHub Actions lints every PHP file and runs the test suite on PHP 8.1 to 8.4 for every push.

bahu90 / mining-manager

Package info

Security

Statistics

README

Standalone

Features

Requirements

Installation

Switching from `mattfalahe/mining-manager`

Configuration

Key Settings

Moon Arrival Notification Architecture

How Ore Classification Works

Permissions

Artisan Commands

Operational Commands

Utility Commands

Webhook Notifications

Diagnostic Testing

Support

License

Development

bahu90 / mining-manager

Package info

Security

Statistics

README

Standalone

Features

Requirements

Installation

Switching from mattfalahe/mining-manager

Configuration

Key Settings

Moon Arrival Notification Architecture

How Ore Classification Works

Permissions

Artisan Commands

Operational Commands

Utility Commands

Webhook Notifications

Diagnostic Testing

Support

License

Development

Switching from `mattfalahe/mining-manager`