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

No .max property for Wounds and Vigor in 3.5e #740

Open
Belgaron opened this issue Mar 17, 2023 · 4 comments
Open

No .max property for Wounds and Vigor in 3.5e #740

Belgaron opened this issue Mar 17, 2023 · 4 comments
Assignees
Labels
bug Something isn't working 🔫t Triggler unverified Bug not yet validated

Comments

@Belgaron
Copy link

Describe the bug
The drop-down menu for triggers isn't giving me the .max option for wounds or vigor. Making it unusable as I can't find a single document or video explaining how to use the advanced triggers.

To Reproduce
1 try to use the drop-down menu for either property to give max option while using wounds or vigor category

Expected behavior
max wounds and max vigor should be options in the property drop-downs

Screenshots
image
image

Environment Info (please complete the following information):

  • Foundry Version: 10, build 291
  • Game System / Version: [3.5E]
  • CUB Version [image]
  • Browser [chrome]
  • OS [Windows 10]

Additional context
Id take a fix or explanation on how to use the advanced triggers to point to wounds.max and so on. I've tried dozens of combinations and I'm not a coder. I've tried attributes, data, data.data, data.attributes, actor.attributes, data.actor, and a couple others. Nothing seems to work and I can't find any documentation to even start me in the right direction. They all use the simple trigger... and that thing is broken (for my purposes)

@Belgaron Belgaron added bug Something isn't working unverified Bug not yet validated labels Mar 17, 2023
@eclarke12
Copy link
Member

You can try system.attributes.wounds.max in an advanced trigger, but if it's not showing it in the dropdown, it might not be something Triggler is able to work with.

@eclarke12 eclarke12 added the 🔫t Triggler label Mar 17, 2023
@Belgaron
Copy link
Author

I tried that, it seems it auto defaults the first "data" to system after you close and reopen the trigger menu.

I actually got it working on the "actor" level, but still no dice on the token level. It's not working on npc or summons right now. But with hours and hours of trial and error... some progress is better than none, I suppose.

@eclarke12
Copy link
Member

.max is a calculated/derived property on the Actor data not included in the system template so Triggler simple triggers don't detect it.

An advanced trigger like this should work:
image

Example macro using the trigger:
image
image

@Belgaron
Copy link
Author

OK, I will give that a shot. I got the actor working but not the token. That might be different from the paths I've tried so far. Thanks.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Something isn't working 🔫t Triggler unverified Bug not yet validated
Projects
None yet
Development

No branches or pull requests

2 participants