cosmo/daggerheart
1
0
Fork 0
mirror of https://github.com/Foundryborne/daggerheart.git synced 2026-01-11 19:25:21 +01:00
Code Issues Projects Releases Packages Wiki Activity Actions
An unofficial Foundry VTT implementation of the Daggerheart system
24 commits 28 branches 28 tags 48 MiB
Find a file
WBHarry b24cdcc9ed
Adding Prettier 
* Added prettier with automatic useage on pre-commit to avoid style breakage
* Ran Prettier on the project
2025-05-23 18:57:50 +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 Compendium init (#20) 2025-05-23 16:49:49 +02:00
lang Adding Prettier 2025-05-23 18:57:50 +02:00
module Adding Prettier 2025-05-23 18:57:50 +02:00
src/packs Adding Prettier 2025-05-23 18:57:50 +02:00
styles Adding Prettier 2025-05-23 18:57:50 +02:00
templates feat(armorItem): add base thresholds to armor (#21) 2025-05-23 17:56:55 +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 Adding Prettier 2025-05-23 18:57:50 +02:00
.prettierrc Adding Prettier 2025-05-23 18:57:50 +02:00
daggerheart.mjs Adding Prettier 2025-05-23 18:57:50 +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 Adding Prettier 2025-05-23 18:57:50 +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 Adding Prettier 2025-05-23 18:57:50 +02:00
rollup.config.mjs Adding Prettier 2025-05-23 18:57:50 +02:00
system.json Adding Prettier 2025-05-23 18:57:50 +02:00
template.json Adding Prettier 2025-05-23 18:57:50 +02:00

README.md

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

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