An unofficial Foundry VTT implementation of the Daggerheart system
Find a file
2025-05-24 22:25:54 +02:00
.github/workflows Initial commit 2025-05-22 16:53:39 +02:00
.husky Adding Prettier 2025-05-23 18:57:50 +02:00
assets added T4 equipment and class features (#39) 2025-05-24 10:27:45 +02:00
lang Fixed Check Rolls, Attack Rolls and Damage Rolls for PCs 2025-05-24 16:56:01 +02:00
module PR-Fixes 2025-05-24 22:25:54 +02:00
src/packs Merged with main 2025-05-24 10:36:36 +02:00
styles Fixed Check Rolls, Attack Rolls and Damage Rolls for PCs 2025-05-24 16:56:01 +02:00
templates PR-Fixes 2025-05-24 22:25:54 +02:00
tools Adding Prettier 2025-05-23 18:57:50 +02:00
.gitignore Initial commit 2025-05-22 16:53:39 +02:00
.prettierignore PR-Fixes 2025-05-24 22:25:54 +02:00
.prettierrc Adding Prettier 2025-05-23 18:57:50 +02:00
daggerheart.mjs Merged with main 2025-05-24 10:36:36 +02:00
gulpfile.js Adding Prettier 2025-05-23 18:57:50 +02:00
LICENSE Initial commit 2025-05-22 16:53:39 +02:00
package-lock.json feat(equipmentFeatures): update itemConfig (#26) 2025-05-23 21:45:25 +02:00
package.json Adding Prettier 2025-05-23 18:57:50 +02:00
postcss.config.js Adding Prettier 2025-05-23 18:57:50 +02:00
README.md Updated Readme with style code 2025-05-23 19:05:02 +02:00
rollup.config.mjs Adding Prettier 2025-05-23 18:57:50 +02:00
system.json Replaced MappingField with FoundryCore TypedObjectField. Raised system foundry version to 13.344. Added styles/daggerheart.css to .prettierignore (#45) 2025-05-24 21:09:39 +02:00
template.json Updated attack rolls and damage rolls for adversaries 2025-05-24 10:25:40 +02:00

Daggerheart

For Foundry VTT

This is a repo for a Foundry VTT implementation of daggerheart. It is not associated with critical role or darrington press.

Table Of Contents

Overview

Developer Guide

Coding Practises

Style Code

The project is set up for Prettify. Make sure you've run npm install since it was added. There is a pre-commit hook that will automatically run prettify on the files you've changed whenever you do a commit to maintain the formating.

Branches And Pull Requests

During pre-release development, we are making use of main as the development branch. Once release is getting closer we will instead be making a dev branch to base development from to make main more stable.

When you work on an issue or feature, start from main and make a new branch. Branches should be topically named and with the associated Issue number if it relates to an Issue. EX: #6/Level-Up-Bugginess.


Once you're finished with an issue or feature, open a Pull Request on Github for that branch.

The Reviewers Team will be approving submissions. This is mainly since we have a wide spread of experience with system building and the system itself, and we do want the system to become something great. As time goes on, more collaborators are likely to be added as reviewers.

Setup

  • Open a terminal in the directory with the repo cd <path>/<to>/<repo>
  • NOTE: The repo should be placed in the system files are or somewhere else and a link (if on linux) is placed in the system directory
  • NOTE: Linux link can be made using ln -snf <path to development folder> daggerheart inside the system folder
  • Install npm npm install
  • Update package.json to match your profile
"start": "concurrently \"rollup -c --watch\" \"node C:/FoundryDev/resources/app/main.js --dataPath=C:/FoundryDevFiles  --noupnp\"  \"gulp\"",
"start-test": "node C:/FoundryDev/resources/app/main.js --dataPath=C:/FoundryDevFiles && rollup -c --watch && gulp",

  • Replace C:/FoundryDev/resources/app/main.js with <your>/<path>/<to>/<foundry>/<main.js>
  • The main is likely in <Foundry Install Location>/resouces/app/main.js
  • Replace --dataPath=C:/FoundryDevFiles with <your>/<path>/<to>/<foundry>/<data>

Now you should be able to build the app using npm start Foundry VTT Website