Official Daggerheart Bug Report Thread

[superteddy57]

I think when you compare the DH ruleset to some of the more mature rulesets it feels automation light, but most of the best automation either started with of still resides in The Forge for things like 5e and Savage Worlds, so I would expect more automation in the future as more user generated content evolves. Also, putting extensions together to handle some automation on your own is not too difficult once you get the change of it and incorporate some AI to help you out. I was able to add a bunch of functionality to our game that my players really wanted.

I would also say most of the homebrew people do is for creating domains, classes, ancestry... That stuff needs flexibility. But the more automated the actual mechanics are the better iny opinion.

This might be better as it's own thread unless you are reporting an issue that needs to be addressed. I will address my opinion here. As for the automation, there is always a refinement to what is initially released, but our goal is not to make a video game. Some instances need a manual touch and not full automation or you will limit freedom and abstractness. We also don't want to lose that tabletop feel and aim for about 70% automation. Also some automation is not possible without hard coding the logic in and then no chance of homebrew within the program itself. But, this is a prime example of the use of extensions. Some want it automated all the way through and some want little to none. Extensions make that possible as the GM can decide how much automation they want in the game. Making extensions is also a way for features and automation to be introduced as we can gauge if it's an universal want versus only a few tables take advantage of it.

[Agamon]

It looks like Long Rest actions targeting others (Tend to All Wounds and Repair All Armor) have no effect. The same actions while targeting yourself work as intended.

You don't need to target others, you just tell the other player you are, for example, fixing their armor, and they do it themselves.

[Cyrian]

You don't need to target others, you just tell the other player you are, for example, fixing their armor, and they do it themselves.

It can of course be handled manually, but the functionality is there and it used to work, hence the bug report.

Superteddy - speaking of rest actions, is it possible to add a button for the rest menus instead of the players right clicking? My regular group is used to it now, but other players, even familiar with FG, are typically surprised by the random right click in empty space to bring this menu up.

[superteddy57]

It can of course be handled manually, but the functionality is there and it used to work, hence the bug report.

Superteddy - speaking of rest actions, is it possible to add a button for the rest menus instead of the players right clicking? My regular group is used to it now, but other players, even familiar with FG, are typically surprised by the random right click in empty space to bring this menu up.

That's using the CoreRPG design and similar to many other rulesets. Just conforming global design so others that want to try Daggerheart will feel comfortable and cut maintenance down.

Edit: I believe I already pushed a hotfix to address rest options

[Cyrian]

Ah yes, just checked and the targeted Long Rest functions are working. Thanks!