Skip to content

v1.6.0 - Active Impact Conditions

Compare
Choose a tag to compare
@eclarke12 eclarke12 released this 17 Jun 14:56
· 330 commits to master since this release
d074440

While this update started out as a small patch for CUB v1.5.0, it grew into something much more! Continue reading for more details, or jump to the 📜notes!

First and foremost is a fix allowing the Condition Lab Active Effects (Enhanced Effects) config to be opened again. This was an unfortunate miss on my part during the testing of v1.5.0--not realising that Foundry VTT v0.8.x had broken the ability to open config. I made the necessary changes and also some QOL fixes to the way the config behaves. It should correctly save changes to the attached condition when the config form is Submitted.

Additionally Active Effects are now able to be exported/imported in the Condition Lab.

This release also adds support for the Ironclaw Second Edition game system. Thanks to @Hertzila!

On the i18n front @WallaceMcGregor provided a revised translation for Español. Previously the translation provided was labelled as Castellano which was an unnecessary differentiation (or so I'm told!). If you have concerns about this change please contact me.

Finally, while working on the Condition Lab I started thinking about some of the principles I had applied while designing the Lab, and whether they still made sense today. The Foundry API has moved substantially since the first release of the Condition Lab back in 2019(?) and I realised that there were some things that could be done better:

  • Reference Entries were a great idea, but poorly implemented. In the previous incarnation you would select the type of entry (eg. Item from a Compendium or Journal Entry from your world) and then the list of available of entries of that type would show up. The problem here is that the Condition Lab was preparing ALL the entries for EVERY type on EVERY 👏 SINGLE 👏 LOAD👏. In some worlds this wasn't a problem (ie. if you didn't have a lot of compendia or JournalEntries/Items in your world), however in an "average" world this could cause the Condition Lab to take seconds or even minutes to load. Given that support for dragging and dropping entities into text fields is pretty solid, I realised it made more sense to provide this workflow instead.

jJrcYi4wkE

It's faster to load the lab, and more intuitive to drop the desired reference into the field-well rather than search through a dropdown of 700 entries.

  • Drag and Drop reordering sounded really good on paper, but it was a nightmare to implement. The first iteration used native Foundry drag 'n drop functionality which worked "OK" but didn't look great. Then the amazing @Moerill came in with an implementation based on the Greensock library that looked a lot better, but it was glitchy (my fault not theirs!). So I've scrapped the notion of being able to drag and drop Condition Lab mapping rows for now. Instead you can use tried and tested buttons to move an entry up or down on the list.

These are just two areas I wanted to highlight where the experience in the Condition Lab could be/has been improved. The entire Lab is due for an overhaul to improve its user interface and functionality, so look forward to a future release addressing that.

Support My Work

Hopefully you enjoy CUB as much as I do! While CUB is a labour of love for me, the more support I receive, the more time I can dedicate to making it as awesome ✨ as possible!

If you're already a Patron: thank you from the bottom of my heart 💖!
If not, please consider supporting my work via Patreon.

♥ e

Release Notes

[1.6.0] - 2021-06-15

Enhanced Conditions

  • Active Effects Config can be opened from the Condition Lab again!
  • Changes made in the Active Effects Config are shown without closing and reopening the form, and are saved to the attached Condition on Submit.
  • Active Effects attached to Conditions can now be Exported and Imported in the Condition Lab
  • Condition Lab reference entries for Conditions are now a text-input (Id) field linking to any entity in your Foundry instance (eg. Actor, Item, JournalEntry, Compendium JournalEntry etc). The field is in the format of @EntityType[entityId]{DisplayName} This field now accepts drag-drop similar to dropping an entity into a Journal Entry (or other enriched text entry). If the dropped Id resolves correctly, a link to the entity will show up next to the Id. You can also put good ol' plain text in this field if you want.

Note: the reference entry's DisplayName or text will override the Condition Name.

  • The drag handles in the Condition Lab have been removed in favour of simpler up/down arrows ("chevrons" if we're being pedantic). A future update may add drag handles or more advanced order-sorting to the Lab
  • Added support for the Ironclaw 2e system. Thanks to @Hertzila! 🎉
  • Conditions are no longer output to chat if the Output to Chat setting is disabled in CUBputer. Additionally, When this setting is disabled the related checkboxes in the Condition Lab cannot be changed.

Triggler

  • When Triggler executes a macro it now passes the triggering token/actor to the macro for downstream usage.
  • Fixed logic in Triggler related to checking the ownership of the triggering actor/token.

Temporary Combatants

  • Temporary Combatants now work with Foundry VTT v0.8.x

Hide Names

  • Hide Names Actor button no longer disappears (🐱‍👤 ninja-style) after saving the form.

Translations

  • Updated 한국어 (Korean) translation (thanks @drdwing! 🎉)
  • Replaced Castellano (es-ES) translation with Español (es) (thanks @WallaceMcGregor! 🎉)