Skip to content
This repository has been archived by the owner on Nov 13, 2024. It is now read-only.

Releases: p4535992/conditional-visibility

v0.4.24

13 Mar 22:59
Compare
Choose a tag to compare
  • (Again) Bug fix multiple AE for missed unsetflag when delete a AE
  • Removed refresh function seem not necessary anymore

v0.4.23

13 Mar 22:03
Compare
Choose a tag to compare
  • Buf fix multiple AE for missed unsetflag when delete a AE

v0.4.22

13 Mar 19:30
Compare
Choose a tag to compare
  • Some bug fix
  • Autostealth now it should work like expected?

v0.4.21

13 Mar 09:51
Compare
Choose a tag to compare
version 0.4.21

v0.4.20

13 Mar 08:57
Compare
Choose a tag to compare
version 0.4.20

v0.4.19

12 Mar 23:58
Compare
Choose a tag to compare
  • Add new active effect change ATCV.conditionDistance for a distance check to add to the active effect.

v0.4.18

12 Mar 21:57
Compare
Choose a tag to compare
version 0.4.18

v0.4.17

12 Mar 18:49
Compare
Choose a tag to compare
  • Complete rewrite of the code,api desgin pattern ecc.
  • For backward compatibility and integration with the Levels module, the new logic must remain bound to the flags already existing in the current module.
  • Sync the status with the flags on the token, the checking of the visibility, if I can or cannot see the certain thing is currently bound to the values of the flags, with the new version for a better management of the thing each flag is associated with an AE, so if a token a l'active effects "Truesight" can see tokens that have the "Invisibility" active effects and that they usually shouldn't see.
  • Integration with the DfFred Convenient Effects module with the will gonna be api
  • Possible integration with perfect vision.
  • Hope to have a multisystem integration, but for now PF2, DND5e are the first one requested.
  • Possible integration with the levels it's seem to be the right road to follow, we can use the method overrideVisibilityTest(sourceToken, token){} of levels for override the levels visibility test.

v0.4.16

12 Mar 18:43
Compare
Choose a tag to compare
  • Complete rewrite of the code,api desgin pattern ecc.
  • For backward compatibility and integration with the Levels module, the new logic must remain bound to the flags already existing in the current module.
  • Sync the status with the flags on the token, the checking of the visibility, if I can or cannot see the certain thing is currently bound to the values of the flags, with the new version for a better management of the thing each flag is associated with an AE, so if a token a l'active effects "Truesight" can see tokens that have the "Invisibility" active effects and that they usually shouldn't see.
  • Integration with the DfFred Convenient Effects module with the will gonna be api
  • Possible integration with perfect vision.
  • Hope to have a multisystem integration, but for now PF2, DND5e are the first one requested.
  • Possible integration with the levels it's seem to be the right road to follow, we can use the method overrideVisibilityTest(sourceToken, token){} of levels for override the levels visibility test.

v0.3.5

03 Feb 13:39
Compare
Choose a tag to compare