README

Capital ship management for SeAT, the EVE Online corporation manager. This is a SeAT 5 plugin: a Composer package that Laravel discovers automatically once it is installed into a SeAT instance.

It does three things:

• Applications. A member asks to build a capital hull for one of their characters and explains why.
• Review. Reviewers approve or deny pending applications, with an optional note to the applicant.
• Report. A table of every capital hull owned by the characters in scope, with the solar system each hull sits in, filterable by system and extendable to the owners' alts.

Every hull in the report comes from the character assets SeAT already syncs from ESI. Whether a hull went through an application makes no difference to the report.

Installation

1. Add the package to the SeAT instance:

   composer require temetvince/seat-capitals

2. Run the migrations and refresh the caches:

   php artisan migrate
   php artisan config:cache
   php artisan route:cache

3. Grant permissions to roles (see below). The Capitals group appears in the sidebar for every user holding at least one of them.

4. Optionally subscribe a notification group to the two Capitals alerts, and set the home systems under Capitals > Settings.

Permissions

The report permission lives in SeAT's character scope on purpose. Set the role's filter to your corporation and the report shows exactly the hulls of characters in that corporation. Without a filter the report shows every character SeAT knows. Admin users always see everything.

Screens

Report filters

• Systems. A multi-select backed by SeAT's system lookup. It starts with the configured home systems selected. Clear it to see hulls everywhere.
• Characters. Whose hulls to list. "In my scope, plus their alts" is the default: the characters the viewer's role filters allow, widened to every character registered under the same SeAT account, so a corp member's out-of-corp alts get listed. "In my scope" drops the alts. "Everyone in SeAT" ignores the role filters and covers every character SeAT knows, which is how a pilot who left the corporation but still has a token stays visible; it appears only for viewers holding capitals.report_all. The Main and Corporation columns show whose account a hull belongs to and where that character is now, so departed members and out-of-corp alts are easy to spot.

How a hull's system is found

ESI reports a location id and a location type per asset. The report resolves them in this order and takes the first hit: the asset's own system when it is in space, the station or structure it is docked in, the same two rules applied to the item that contains it, then the map id SeAT's location job derived from coordinates. A hull whose location cannot be resolved shows an unknown system and is excluded by any system filter.

Application lifecycle

Every other transition is refused. Rows are never deleted, so the history stays auditable.

Notifications

Two alerts are registered with eveseat/notifications. Subscribe a notification group to them and each of its Discord, Slack or mail integrations receives the message.

Notification text is English, as with SeAT's own notifications, because webhook and mail messages have no viewer locale.

Configuration

Publish the config file to change which SDE groups count as capital hulls:

php artisan vendor:publish --tag=seat-capitals

config/seat-capitals.php then holds capital_groups, a map of invGroups.groupID to a label. The default lists titans, dreadnoughts, lancer dreadnoughts, carriers, supercarriers, force auxiliaries, capital industrial ships, freighters and jump freighters. A group not listed can neither be applied for nor appears in the report.

Home systems are stored as a SeAT global setting, edited from the Settings screen.

Development

The plugin is developed against the upstream SeAT source for reference and tested in isolation with Orchestra Testbench on in-memory SQLite. It needs PHP 8.1 or newer and Composer.

Upstream's migrations target MySQL, so the tests create SQLite stand-ins for the upstream tables the plugin reads (tests/database/migrations). The plugin's own table comes from its real migration.

To try the plugin inside a running SeAT, add this directory to that instance's composer.json as a path repository, then require it:

{
  "repositories": [
    { "type": "path", "url": "../plugins/seat-capitals" }
  ]
}

composer require temetvince/seat-capitals:@dev

SeAT's settings page reports the plugin version as missing for a path install. That is expected: the version comes from Composer's installed-package metadata, which a path repository does not carry.

File map

License

Released into the public domain under the Unlicense.