@eveshipfit/sde 7.3542233.0 → 8.3542233.0

package/README.md

@@ -19,7 +19,7 @@ The main goal is to produce a small data-file, with everything included for dogm
 
 ```bash
 go run ./cmd/sde-patched download        # fetch the latest SDE into sde/
-go run ./cmd/sde-patched build           # write dist/sde.dat and dist/names.dat
+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
@@ -41,11 +41,13 @@ It is also not meant as "production-ready" software, but much more as "an easier
 
 ## Output
 
-`build` writes two flatbuffers, described in [specs/](https://github.com/EVEShipFit/sde-patched/tree/main/specs):
+`build` writes three flatbuffers, described in [specs/](https://github.com/EVEShipFit/sde-patched/tree/main/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
 
@@ -53,7 +55,7 @@ a type ID. Only an EFT-fit importer needs it, and only ever to search.
 npm install @eveshipfit/sde
 ```
 
-[`@eveshipfit/sde`](https://www.npmjs.com/package/@eveshipfit/sde) ships both files and the schemas, under `dist/` and `specs/`.
+[`@eveshipfit/sde`](https://www.npmjs.com/package/@eveshipfit/sde) ships all three files and the schemas, under `dist/` and `specs/`.
 
 ## Python
 
@@ -61,10 +63,10 @@ npm install @eveshipfit/sde
 pip install eveshipfit-sde
 ```
 
-[`eveshipfit-sde`](https://pypi.org/project/eveshipfit-sde/) ships both files and the schemas, and the paths to them.
+[`eveshipfit-sde`](https://pypi.org/project/eveshipfit-sde/) ships all three files and the schemas, and the paths to them.
 
 ```python
-from eveshipfit_sde import build_number, names_path, sde_path, specs_path
+from eveshipfit_sde import build_number, names_path, sde_path, specs_path, texts_path
 
 dogma.load_sde_from_file(sde_path())
 ```

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@eveshipfit/sde",
-  "version": "7.3542233.0",
+  "version": "8.3542233.0",
   "description": "A patched EVE Online SDE, as flatbuffers, for EVEShipFit's dogma-engine",
   "repository": {
     "type": "git",
@@ -11,8 +11,10 @@
   "files": [
     "dist/sde.dat",
     "dist/names.dat",
+    "dist/texts.dat",
     "specs/eve.fbs",
     "specs/names.fbs",
+    "specs/texts.fbs",
     "LICENSE.EVE"
   ],
   "publishConfig": {

package/specs/names.fbs

@@ -1,15 +1,8 @@
 namespace eve;
 
-/// Name lookup, in a file of its own.
-///
-/// An EFT-fit can be written in any of the eight languages EVE supports, so a
-/// name has to be matchable back to a type.
 table Names {
     build_number: int32;
-
-    /// Every name of every type, in every language, lowercased and sorted by
-    /// UTF-8 bytes. Lowercasing is per code point and locale-independent, so
-    /// that a fit does not have to match the case.
+    /// Lowercased per code point, locale-independent; sorted by UTF-8 bytes.
     names: [string] (required);
     type_ids: [int32] (required);
 }

package/specs/texts.fbs

@@ -0,0 +1,15 @@
+namespace eve;
+
+table DogmaAttributeText {
+    id: int32 (key);
+    tooltip_title: string;
+    tooltip_description: string;
+}
+
+table Texts {
+    build_number: int32;
+    dogma_attributes: [DogmaAttributeText] (required);
+}
+
+root_type Texts;
+file_identifier "ESFT";