Retrieve a random record from the Fallout 76 game files. https://fwdekker.com/tools/random-fo76/
Go to file
Florine W. Dekker 21974c0b22
Add version information
Fixes #2.
And fix a silly bug with preferences when the number of possible signatures is not a multiple of 8...
2020-10-01 19:33:30 +02:00
src/main Add version information 2020-10-01 19:33:30 +02:00
.editorconfig Add version number and best practices 2020-03-14 12:58:33 +01:00
.gitattributes Migrate to npm, use template package 2020-05-16 20:33:11 +02:00
.gitignore Migrate to npm, use template package 2020-05-16 20:33:11 +02:00
Gruntfile.js Migrate to npm, use template package 2020-05-16 20:33:11 +02:00
LICENSE Add LICENSE and semantic HTML 2019-06-10 14:32:55 +02:00
README.md Add version information 2020-10-01 19:33:30 +02:00
package-lock.json Display loading indicator 2020-10-01 18:42:34 +02:00
package.json Add version information 2020-10-01 19:33:30 +02:00

README.md

Random Fallout 76 records

Allows a user to retrieve a random record from the Fallout 76 game files. The user can filter records by data type to avoid receiving uninteresting data types.

The back end, api.php, communicates with an SQLite database, .fo76-dumps-ids.db, containing the IDS.csv dump from the Fallout 76 data dumps repository, with an additional index sk_signature on the signature column. The database also has a table meta with text columns key and value that contain version information. Additionally, the database has an index sk_signature on the signature column. The database is not included in this repository.

The front end, index.html, sends asynchronous queries to the back end based on the user's settings. Selected data types are stored in a cookie so the user doesn't have to redo their settings each time the page is refreshed.

Development

Requirements

  • npm
  • a local PHP 7 server
  • a local copy of .fo76-dumps-ids.db

Setting up

# Install dependencies (only needed once)
$> npm ci

Building

# Build the tool in `dist/` for development
$> npm run dev
# Same as above, but automatically rerun it whenever files are changed
$> npm run dev:server
# Build the tool in `dist/` for deployment
$> npm run deploy