Skip to main content

SDE Patched

npm PyPI CI

Discord

A patched EVE Online SDE to work better with EVEShipFit's dogma-engine.

The main goal is to produce a small data-file, with everything included for dogma-engine to calculate fit statistics.

Prerequisite

  • Go 1.27 or later
  • flatc

Usage

go run ./cmd/sde-patched download        # fetch the latest SDE into sde/
go run ./cmd/sde-patched build           # write dist/sde.dat, dist/names.dat and dist/texts.dat
go run ./cmd/sde-patched compare old/    # tell whether dist/ differs from old/, ignoring the SDE build
go run ./cmd/sde-patched patches         # list all patches
go run ./cmd/sde-patched ids             # give an ID to anything added without one
go run ./cmd/sde-patched explain alignTime
go run ./cmd/sde-patched explain --type "Rifter"
go run ./cmd/sde-patched serve           # edit the patches in a browser

build downloads the SDE when there is none yet, and uses the one on disk otherwise. Use --build <number> to pin a version.

Editing

The patches are best edited via the web-editor (via serve). It allows for full customization of all existing and new attributes.

This editor is fully vibe-coded, and it is very likely no human actually understands how it works. It is also not meant as "production-ready" software, but much more as "an easier way to digest patches".

Output

build writes three flatbuffers, described in specs/:

  • dist/sde.dat holds the types, dogma, groups, categories, buffs and mutaplasmids, with English names only. It is all a dogma-engine needs.
  • dist/names.dat maps a name in any of the eight languages EVE supports back to a type ID. Only an EFT-fit importer needs it, and only ever to search.
  • dist/texts.dat holds text only a user interface shows, like the tooltips of attributes, in English. A dogma-engine never needs it.

npm

npm install @eveshipfit/sde

@eveshipfit/sde ships all three files and the schemas, under dist/ and specs/.

Python

pip install eveshipfit-sde

eveshipfit-sde ships all three files and the schemas, and the paths to them.

from eveshipfit_sde import build_number, names_path, sde_path, specs_path, texts_path

dogma.load_sde_from_file(sde_path())

build_number() reads the SDE build straight off the version.

Releasing

Every day at 12:00 UTC, main is built against the latest SDE. When the result differs from the latest release, the SDE build number and release date aside, a new release is made and published on npm and PyPI. A change to the patches is released this way too.

Patches

The SDE describes what the EVE client needs, not what a fitting tool needs. Align time, for example, is not an attribute; the client works it out. Patches add the missing attributes and effects, so a dogma-engine can work them out instead.

License

All EVE Online data belongs to CCP, and is subject to their license agreement. Everything EVEShip.fit-specific is MIT.

Metadata

Release files for eveshipfit-sde 10.3561556.1

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for eveshipfit-sde 10.3561556.1
File Size Uploaded
eveshipfit_sde-10.3561556.1.tar.gz 5.7 MB Details

Built distribution (wheel)

Table of built distributions (wheels) for eveshipfit-sde 10.3561556.1
File Interpreter ABI Platform
eveshipfit_sde-10.3561556.1-py3-none-any.whl Python 3 none any Details

Total release size: 11.5 MB

Release files / eveshipfit_sde-10.3561556.1.tar.gz

Download URL eveshipfit_sde-10.3561556.1.tar.gz
Size 5.7 MB
Tags Source
SHA-256 checksum
How to use checksums
93b5acf921d3c86d2a9e5ab5c59a1a1e42de6c19a3c2069a2eb3bae0d1ee3fff
BLAKE2b-256 checksum
How to use checksums
e22691a15c4c22b896510989aa56859adc299f8ef2dfad661c19d0093a5a2323
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 6, 2026.

Transparency log

Release files / eveshipfit_sde-10.3561556.1-py3-none-any.whl

Download URL eveshipfit_sde-10.3561556.1-py3-none-any.whl
Size 5.8 MB
Tags Python 3
SHA-256 checksum
How to use checksums
b53cefecab057497dcfc7f70391b1bea9d875c58b869c4e0d2452a81d72a6945
BLAKE2b-256 checksum
How to use checksums
96bffb6549293bc77d6f3093a447abac19316634c61cb1eae8c9b46089131dd5
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 6, 2026.

Transparency log
Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page