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

Set collision filters using a global string #487

Open
2 tasks done
WTI-RUslan opened this issue Feb 24, 2025 · 1 comment
Open
2 tasks done

Set collision filters using a global string #487

WTI-RUslan opened this issue Feb 24, 2025 · 1 comment

Comments

@WTI-RUslan
Copy link

Reviewed guidelines

  • I have read and understand the suggestion guidelines

Checked for duplicate suggestions

  • I checked for existing similar suggestions

Summary

I really love the collision filters feature on the Solid behavior. Like, a lot. But there are instances where I need to just "reset" the behavior to a specific set of tags every time.

Possible workarounds or alternatives

Currently, if a filter set ever changes, I have to go through my entire project and change it as well and missing it in even one place can result in some pretty catastrophic bugs. At the moment and I tried to use a global string, but the engine actively ignores it and treats it as if it's empty.

Proposed solution

It would be great if we could use a global string variable as a sort of "preset" for Solid filter tags or just create presets within the behavior if that's too complicated or won't work for some reason.

Why is this idea important?

It's very time consuming to set all of these filters in every individual instance they occur in games that use the solid tag filters frequently. Every time a state change occurs, we have to call the individual tags to include or exclude instead of being able to apply a group of them all at once.

For instance, if we have a power that makes you able to phase through objects A, B, C, and E, but not D, we have to call those individually and then when the power resets, we have to tell it to include "A, B, C, D, and E". It would be a lot easier to just have "A, B, C, D, and E" all in a single "preset" tag called "Default" or something so we could clearly see that we're setting all of those objects as such.

Additional remarks

No response

@XHXIAIEIN
Copy link

Just as an additional suggestions.
I think it would also help if solid tags got more ACEs like the new tags property on instance objects.

  1. Solid: Set tags action
    Action: Add / Remove / Set
    Tags: ""

Image

  1. Solid: Tags / TagAt / TagsCount expression
    Image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants