Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Arrival trigger missing value field #82

Closed
ual002 opened this issue May 22, 2023 · 2 comments
Closed

Arrival trigger missing value field #82

ual002 opened this issue May 22, 2023 · 2 comments
Labels
clarification Not a bug, but could use some tweaking

Comments

@ual002
Copy link

ual002 commented May 22, 2023

The value field presented in Yogme does not appear to be the one that determines region.

image

However in allied you can see the value is retained but it isnt the value field that allied thinks specifies the region.

image

@MikeG621
Copy link
Owner

MikeG621 commented Jun 4, 2023

The drop-down next to Target Type is the correct field, it has the names of the regions listed and will display the correct index. That extra parameter field is what's used for Regions and Proximity targets, not the normal Variable drop-down.

It's working the same as AlliED, so this is more of a GUI issue and I need to make it more intuitive.

MikeG621 added a commit that referenced this issue Jun 4, 2023
@ual002
Copy link
Author

ual002 commented Jun 6, 2023

Oh I see what you're saying. I kind of feel dumb that I missed that.

@MikeG621 MikeG621 added the clarification Not a bug, but could use some tweaking label Jun 11, 2023
@MikeG621 MikeG621 closed this as completed Aug 4, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
clarification Not a bug, but could use some tweaking
Projects
None yet
Development

No branches or pull requests

2 participants