@sakura2333/kancolle-data

@sakura2333/kancolle-data

Versioned data projections generated by kancolle-item-improvement-spider. The package exposes file paths and does not eagerly load large JSON/NeDB files.

const data = require('@sakura2333/kancolle-data')

console.log(data.improvement.listPath)
console.log(data.schemas.improvementDetailPath)
console.log(data.equipment.dropFromPath)
console.log(data.equipment.sourcesPath)
console.log(data.equipment.specialBonusesPath)
console.log(data.assets.useitemPath(71))
console.log(data.assets.equipmentPath(61))

Datasets:

• improvement/list.json: compact all + weekday list projection.
• improvement/detail.nedb: full routes plus ★0..★MAX effect expectations and 11 explicit per-route actions (including optional MAX conversion).
• schemas/improvement-detail.schema.json: JSON Schema for each schema-4 NeDB record.
• equipment/drop-from.nedb: detailed ship initial/remodel loadout evidence.
• equipment/sources.nedb: one unified record per equipment with required shipIds, upgradeFromItemIds, numeric questKey arrays, and a non-null boolean developmentAvailable flag.
• schemas/equipment-sources.schema.json: JSON Schema for unified source records.
• equipment/special-bonuses.nedb: bonus rules targeting either concrete equipment IDs or equipment-type IDs.
• assets/useitem/*.webp: official use-item cards encoded as WebP quality 93 for canonical consumers.
• assets/equip/*.webp: official KanColle slot/card equipment images encoded as WebP quality 93.

Special-bonus targets are discriminated by target.kind:

{"target":{"kind":"equipment","equipmentIds":[315]}}
{"target":{"kind":"equipment-type","equipmentTypeIds":[9]}}

Use manifest.json to verify schema versions, source freshness, icon-reference integrity and file hashes. RELEASES.json contains machine-readable release metrics.

Strict releases require same-run network validation for the canonical Akashi improvement source and the KcWiki/KC3 supplemental datasets. A cached projection cannot be promoted as a fresh release.

Legacy poi-plugin-item-improvement2 distribution

The Stable main release builds two immutable npm versions from the same canonical candidate:

@sakura2333/kancolle-data@latest
  normal paths -> canonical improvement detail schema 4

@sakura2333/kancolle-data@improvement2
  normal paths -> frozen improvement detail schema 3
  assets/useitem/{id}.png -> legacy official PNGs
  equipment datasets/images -> intentionally absent

The compatibility version is not a second crawler or a copied parser. The release tool builds a minimal package from the explicit schema-3 VO projection and the official useitem PNGs retained for the legacy plugin. It excludes all equipment datasets and equipment images, assigns a unique *-improvement2 npm version, and binds that version to the improvement2 dist-tag.

Legacy consumers keep their existing code and install the tag:

npm install @sakura2333/kancolle-data@improvement2

Future canonical fields do not require changes to the compatibility projection. Only changes needed to preserve an original schema-3 field or meaning may modify the frozen VO.