Project Plateau
Project Plateau: four glass plates, one living valley, and the road back to camp.
翻訳待ち
No updates detected yet. GitHub releases will appear here.
Warhammer 40,000 11th edition army list builder powered by BSData
翻訳待ち
Loading the full README.
Read the full README ↗A Warhammer 40,000 11th edition army list builder that runs entirely in the browser. Unit stats, points, wargear options, leaders, detachments, enhancements and stratagems come straight from the community 40kdc-data dataset, so the builder stays current as the data is updated. The UI is built with Bootstrap 5; the rules engine is plain JavaScript (ES modules, no build step, no dependencies).
PawHammer originally read BSData/wh40k-11e, which has been taken offline. The app now translates 40kdc-data into the same model its engine uses (see Data below); BattleScribe JSON files can still be loaded from disk under Data Source.
npm start # serves the app at http://localhost:8080
Any static file server works; ES modules just need to be served over HTTP, not opened as a file:// URL.
.ros, which also opens in New Recruit), re-import them, and print them as datasheets.Yellowscribe's server doesn't send CORS headers, so a web page can only read the code it
returns through a CORS proxy. The proxy URL is set under Data Source and defaults to
Corsfix (https://proxy.corsfix.com/?{url}):
npm start): works as-is. Corsfix allows localhost without an account.frbfli.github.io). The free plan allows 60 requests per minute and 100 MB a month.Other proxies work too. {url} is replaced with the Yellowscribe address, and {encodedUrl}
with a URL-encoded one. For corsproxy.io, for example: https://corsproxy.io/?key=YOUR_KEY&url={encodedUrl}.
If the proxy is empty or fails, the dialog offers to download the .ros file and open
Yellowscribe, so you can upload the file there yourself.
js/
engine/
gamedata.js Indexes a game system + catalogues and resolves entry links into EntryDefs
roster.js Roster / Force / Selection model
engine.js RosterEngine: modifiers, conditions, repeats, constraints, costs,
validation, auto-selection, datasheet info, text/JSON export
data/
dc-repository.js 40kdc-data source: file listing, downloads, faction list
dc-translate.js 40kdc-data -> the engine's (BattleScribe-shaped) game data
repository.js BattleScribe JSON files (local), catalogue-link resolution
cache.js IndexedDB cache
ui/ Bootstrap views (home, editor, play), templating helpers, storage
main.js App controller and routing
dc-translate.js turns a 40kdc-data faction into the structures the engine reads:
This is the beginning of the README. Read the rest at the original. Read the full README ↗