Skip to content

release-3.3.0

Latest
Compare
Choose a tag to compare
@MangoFVTT MangoFVTT released this 21 Oct 17:10

Ready Set Roll v3.3.0

A feature release of Ready Set Roll, that brings compatibility with dnd5e 4.0.x versions, and overall sweeping changes to RSR to work correctly with activities.

COMPATIBILITY WARNING: This module version ONLY SUPPORTS dnd5e 4.0.4 (release) and greater. To use this module version you must also use the dnd5e 4.0 system. If you do not wish to update your game system, please continue using previous versions of Ready Set Roll.

COMPATIBILITY WARNING: This module version ONLY SUPPORTS Foundry VTT version 12 (release) and greater. To use this module version you must also use Foundry VTT version 12. If you do not wish to update your core software, please continue using previous versions of Ready Set Roll.

For manual installation, use the following manifest URL: https://github.com/MangoFVTT/fvtt-ready-set-roll-5e/releases/download/release-3.3.0/module.json

Patch Notes

dnd5e 4.0 Compatiblity

  • Replaces Item quick rolling entirely with Activity quick rolling, and ensures that all types of activities can quick roll. Due to certain behaviours of activities, there will inevitably be more pop-up dialogs that come up when using activities vs using items. For example, usage configuration can no longer be skipped. This is an issue that should be brought up with the core system if desired.
  • As a result of this overhaul, Alternate item rolls have been removed, since activities replace their use case entirely. Similarly, Quick Roll configuration is also gone, since activities can be set up with near full customisation. Any missing customisation options should be brought up as core system feature requests.
  • Damage context fields no longer exist either, because activities can have their own individual flavour. I may re-add context later, but it will have to be a brand new feature since the old methods are 100% obsolete.

Split Same Type Damage

  • A long-requested feature has finally been enabled in the core system in 4.0+, allowing damage fields of the same type to remain separate damage fields when rolled. At the moment, this is hardcoded to true. I will later add a setting to disable/enable separation of damage rolls of the same type.

image

Change Log

Features