Site Admin · BGS Command Deck
Wolf BGS Control
Private strategy, automation parameters, system status overrides, tick schedules, and order-generation controls for the Regiment of Imperial Mongrels.
Wolf Only
Checking Secure Access
Confirming the current site-admin session and loading Wolf BGS Control.
MONITORED CHANGES
Faction Alerts
New major Mongrel state changes light the master alert. ACKNOWLEDGE extinguishes the warning light without removing any alert. VIEW opens the broader board-level picture; REMOVE dismisses only that alert row.
0listed
Loading faction alerts…
Discord IntegrationMulti-channel Discord · Mission Control + Colonization Jobs + Faction Alerts + Scout Network + Squad Payouts + Archive + System Testing+
Mission Control → Discord
Discord Channel Routing
Daily Orders use the dedicated Mission Control channel. Colonization Jobs keeps a persistent live summary plus active-job cards in its dedicated channel. Scout Network keeps one persistent summary with every priority Scout Job plus the 15 ordinary systems needing scouting that are closest to Diaba in its dedicated channel. Faction Alerts keeps Retreat/conflict cards plus one silent opportunities summary for interesting trade/combat states in its dedicated channel. Squad Payouts uses one persistent squad-funded balance summary and individual cards only when a member requests payout in its dedicated channel. Completed Colonization Jobs write permanent records to the separate Colonization Archive channel. The original webhook is reserved for System Testing only.
LOW-NOISE MODEAll webhook URLs stay server-side in Cloudflare. Mission Control Daily Orders reuse one tracked message. Colonization Jobs keeps active work only in its dedicated channel. Scout Network shows all current priority jobs plus only the 15 nearest ordinary needs-scouting systems from Diaba; ordinary jobs never create individual Discord cards. The authenticated 30-minute operations check refreshes Scout cycle rollovers and BGS Discord state without waiting for another CMDR action. Faction opportunity states update the persistent summary only; Retreat/conflict cards are reserved for operational alerts. Verified squad rewards update the Squad Payouts summary silently; only explicit payout requests get individual cards. Rewards remain event-driven rather than adding ledger reads to the 30-minute timer. Completed Colonization Jobs are written once to the separate archive webhook and are deduplicated by Job ID. Mission Control, Colonization Jobs, Faction Alerts, Scout Network, and Squad Payouts each use their own production webhooks. System Testing is isolated from production routing. Live Scout is required for Scout attribution and rewards. Mentions remain disabled.
Scout NetworkDirect EDMC BGS uplink · individually revocable CMDR tokens+
Mongrel Scout Uplink
Fly it. Update it.
A scout only needs EDMC and the one-file Mongrel Scout plugin. Scout is event-driven: it uploads when Elite writes a full faction board on FSDJump, Location, or CarrierJump. Simply remaining in a system does not generate new influence data.
0issued tokens
1
Install EDMCUse the current Elite Dangerous Market Connector.
2
Install Mongrel ScoutUnzip MongrelScout.zip and copy the ready-made MongrelScout folder into EDMC's plugins folder.
3
Download Mongrel Scout (.zip)
Install guide
Paste scout tokenOne token per trusted CMDR. Then they just fly.
ONE-TIME TOKEN · COPY NOW
Loading Scout Network…
Privacy boundaryThe plugin does not send CMDR name, cargo, credits, ship/loadout, materials, missions, or general route history. Non-Mongrel systems are discarded locally and never uploaded.
Scout JobsTick-aware paid scouting · optional 60-minute reservations · priority bonuses+
Scout Reward Control
Cycle Scouting Rewards
Every active Mongrel system can offer one Scout reward per configured BGS cycle. The cycle uses the same per-system tick schedule and transition offset as Daily Orders. Claims are optional and only reserve reward priority for 60 minutes.
Priority bonus: set an extra amount and reason on any system. By default the bonus is one-shot and clears after that system's next rewarded Scout completion; you can make it persistent instead.
Loading active systems…
Page 1 of 1
Colony Architect RegistryManual system ↔ CMDR pairing · Frontier claim evidence · informational only+
Track who owns the architect role for colony systems without using it as an access gate. Future Frontier system claims are captured as evidence; older systems can be paired manually and corrected at any time.
NO JOB RESTRICTION
This registry is informational. Colonization Job creation is not restricted by architect identity. Captured claim events never overwrite a manual pairing unless you explicitly confirm the claimant.
Paired Systems0
Active Claims Seen0
Unpaired Claims0
Claim Conflicts0
Architect Pairings
Manual records are the registry of record. Frontier claim evidence is shown beside them when available.
Loading pairings…
Captured System Claims
Claim and release events are attributed to the Frontier-connected CMDR who synced them. Use Claimant loads that evidence into the pairing form for explicit confirmation.
Loading claim evidence…
Colonization Jobs · Test ConsoleSystem or build-specific cargo jobs · Frontier verification · reward preview only+
Define squad hauling jobs independently from Daily Orders. Frontier construction-depot events discover the build automatically, while ColonisationContribution verifies exact delivered tonnage. This console does not create reward debt.
ARBITRATION ACTIVE · PAYOUTS OFF
Each contribution can feed only one payable job. Specific-build jobs outrank system-wide jobs; commodity-specific jobs then outrank unrestricted jobs. Equal-specificity overlaps are blocked instead of guessed.
Active Jobs0
Observed Sites0
Payable Cargo0 t
Frontier CMDRs0
Loading jobs…
Observed Construction Sites
Dock at a construction depot and Sync Activity to discover it. The internal site ID stays hidden; choose the construction site by name and progress here.
No construction sites loaded yet.
Colonization Job HistoryDurable job revisions · site binding · reward rules · payout provenance+
Read-only archive for Colonization Jobs. Existing jobs receive a one-time baseline snapshot, then every create, edit, site binding, status change, and removal writes the complete BEFORE/AFTER job state before the live definition changes.
COLONIZATION PROVENANCE · PAYOUTS OFF
Each revision freezes the system/build binding, commodity restriction, target, reward block, payout rate, personal cap, status, and effective window. This archive creates no reward debt; it gives the future Reward Engine an exact rule snapshot to point back to.
History Records0
Applied0
Jobs Revised0
Jobs Removed0
Loading archive…
Daily Order HistoryDurable publication snapshots · revisions · removals · payout provenance+
Read-only publication archive for Daily Orders. Every future publish, reconcile, or removal writes the complete before/after order state before Mission Control changes, then marks that record applied after the change succeeds.
PROVENANCE FOUNDATION
The archive is not a payout engine. It preserves which logical orders existed, which revision was published, what was removed, who published it, and the exact resulting order snapshot so future reward entries can point back to durable evidence.
History Records0
Applied0
Orders Removed0
Orders Revised0
Loading archive…
Reward AdministrationPer-order member payout defaults · manual adjustments will post to the audited reward ledger+
Verification ReviewScout vs manual reports · reward dry run · ambiguity audit+
Read-only pre-payout audit. This compares Frontier Scout verification with members' manual Daily Order reports. Nothing in this panel creates, edits, or pays reward debt.
0 MATCHED
0 MISMATCH
0 SCOUT ONLY
0 MANUAL ONLY
0Frontier-connected CMDRs
0Verified member/order matches
0Ambiguous verification components
0Unmatched verification components
How to read this
Verified comes from Frontier journal evidence. Reported comes from the member's existing Mission Control submissions. Differences are expected while we test; they are review signals, not automatic corrections.
Loading verification review…
Site Admin Diagnostics
Stored Frontier Activity
Inspect what Mongrel Scout actually stored for a connected CMDR. This is independent of whether the activity matched a Daily Order or generated a reward.
Last Sync—
Latest Journal Event—
Last Known System—
Stored Events0
Raw Journal Trace0
What this proves
Parsed activity shows evidence retained for BGS/rewards. Raw journal trace shows the sanitized surrounding Frontier events captured during a Site Admin sync, including useful troubleshooting events that do not become rewards.
Select a CMDR to inspect stored Frontier events.
Reward Engine · AUTOMATICVerified rewards auto-create OWED debt · blocked items remain audit-only+
The engine computes exact verified Daily Order, Colonization Job, and Live Scout Job reward obligations. Valid READY rewards now create OWED ledger entries automatically. Blocked, ambiguous, stale, or duplicate work is never auto-issued, and payment is still confirmed manually after credits are transferred.
AUTOMATIC VERIFIED
Not checked yet
Pending Auto-Owed0 Cr
Ready Obligations0
Blocked0
Duplicate Suppressed0
Total Entitlement0 Cr
LIVE GATE
A verified reward becomes OWED automatically only when its source has durable provenance or direct Scout evidence, unambiguous member attribution, and no already-issued excess. The same deterministic ledger key suppresses duplicate issuance. Blocked rows stay in this audit for review and never create debt automatically.
Loading dry-run obligations…
Actual Reward Ledger · Payment Console
Rewards are grouped by CMDR. Expand one CMDR, select one or more outstanding entries, use the selected total as your in-game payment reference, then confirm only after the credits have actually been transferred. Selection is limited to one CMDR at a time.
0 CrTotal currently owed
0 CrTotal settled historically
0Members with ledger activity
Loading actual reward ledger…
Global Automation DefaultsCycle timing, freshness, reporting, and order-queue limits+
All Mongrel Systems
System Control Deck
Expand only the system you need. Manual status and system settings are saved independently so unfinished configuration edits never change a status submission.
FILTERED VIEW
Loading Wolf BGS Control…
System DefaultsInherited strategy and automation behavior for systems without a custom override+
Isolated Sandbox · Never Published
BGS Lab — Mandalore
Use Mandalore to create artificial faction boards, slider goals, target bands, balancing calibration, and conflict combinations. Lab changes stay in this browser and are never added to the live Mongrel footprint or Daily Orders.
Mandalore
Test system · synthetic board · local-only stateLABNO DAILY ORDERS
Strategy
System-level inputs used by the same Order Preview logic as live cards.
System Status & Faction Board
Set influence and active/pending/recovering states. Influence does not need to sum to 100 while you are intentionally testing malformed or transitional conditions.
| Faction | Influence % | Active state | Pending | Recovering |
|---|---|---|---|---|
Faction Strategy, Economy/Security Objectives, Conflict Configuration, calibration, and Order Preview are added below by the same control modules used on live system cards. Lab saves are intercepted and kept local.