Architect runs: a generated run every week
scripts/weekly-architect.js picks an HQ in a region the last weeks did not have and designs each brief against the network a reference architect has built so far, so every brief asks for something new; the game's own checklist and chaos monkey review judge it, and the whole run is replayed from the file for three stars. The game fetches architect/weekly/<key>.json when Puzzles opens, checks it field by field and writes the briefs' text itself. The Sunday job and the release deploy carry it like the weekly puzzles and scenarios. Later briefs' cities no longer show early.
This commit is contained in:
parent
601f7028bd
commit
4e6e8294d2
21 changed files with 461 additions and 17 deletions
|
|
@ -39,7 +39,7 @@ test('architect runs: the chaos monkey finds a shared trench, edits clear the cu
|
|||
const { ev, errors } = load();
|
||||
ev("ACT.pzArStart({id:'euro'})");
|
||||
assert.equal(ev("arHide('lis')&&arHide('bru')"), true, 'cities outside the run are hidden');
|
||||
assert.equal(ev("arHide('dus')"), false);
|
||||
assert.equal(ev("arHide('dus')"), true, 'a city a later brief adds stays hidden until then');
|
||||
// Later briefs stay a surprise: nothing on the map or a city card says where the run goes next.
|
||||
assert.equal(ev("typeof arTags"), 'undefined');
|
||||
ev("UI.sel={type:'city',id:'fra'};renderPanel()");
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue