Astra

01 / CAPABILITIES

Everything runs while you don't.

Astra is three cooperating processes and a Discord bot, wired together with one INI file. No dashboard, no babysitting.

SCAN

Outbound trade scanning

Walks every open outbound trade, prices both sides against live data, and auto-declines anything below your tolerance. RAP, value, or both.

SYNC

Live value tracking

Polls Rolimons item data on a cooldown. The moment a value shifts, the values file is rewritten and dependent processes restart on the new numbers.

SUPERVISE

Process orchestration

Launches and supervises Olympian and the Outbound Checker. If values change or a process dies, Astra kills, relaunches, and keeps going.

LOCK

Hardware-locked licensing

Access is bound to a SHA-256 of your machine UUID plus buyer ID, verified against a hosted whitelist on every launch. One machine, rebindable every 5 days.

NOTIFY

Webhook trade reports

Every cancelled trade fires a Discord embed with your value, their value, and exactly how much RAP or value Astra just saved you.

CONFIG

One-file setup

All behavior lives in Astra_Settings.ini: cooldowns, loss tolerances, scan modes. Sane floors are enforced so you can't rate-limit yourself into a ban.

02 / PIPELINE

Purchase to whitelist, no humans involved.

The Discord bot bridges Shoppy.gg, the order database, and the whitelist server. From payment to a running, licensed copy of Astra is a two-command flow.

01 SHOPPY.GG GET /api/v1/orders?page=1 idle

02 DATABASE database.json :: DB_LOCK held idle

03 DISCORD DM @AstraBOT :: direct message idle

04 DEPLOY WhitelistsSerialNumbers.txt idle

05 CLIENT Astra 3.0.exe :: launch idle

> click any stage to replay from there. every hop logged to a private Discord channel. zero manual provisioning.

# whitelist management

Every claim, rebind, and cooldown denial streams into a private ops channel. This is the real log.

HWID rebinds allowed every 5 days, enforced automatically
old key and new key logged on every change
invalid order IDs and early rebind attempts flagged
whitelist file rebuilt and redeployed on each update

</> discord :: #astra-bot :: live whitelist log

Astra BOT whitelist management log in Discord, showing buyer role claims, whitelist changes, and cooldown denials

03 / CONFIG

$ cat Astra_Settings.ini

The whole machine is tuned from one file. This is a real excerpt.

Astra_Settings.ini

[ASTRA SETTINGS]
# issued by Astra BOT on $buyer
Buyer_ID = 42
# seconds between value scans (min 180)
Value_Check_Cooldown = 240

[OUTBOUND CHECKER SETTINGS]
Automatic_Outbound_Scan = true
# value, rap, or both
Outbound_Loss_Tolerance_Type = both
Outbound_Loss_Tolerance_Rap_Amount = 0
Outbound_Loss_Tolerance_Value_Percent = 0
Outbound_Cancel_Equals = true

04 / ASTRA BOT

@ AstraBOT, in your DMs

Onboarding happens entirely over Discord DM. Three commands, in order.

$help

Walks you through the whole flow, screenshots included.

$buyer <shoppy-order-id>

Verifies your purchase, grants the Astra role, and issues your buyer ID for the settings file.

$whitelist <machine-uuid>

Binds your license to this machine. Run Whitelist.exe to get the code. Rebind allowed every 5 days.