Just wanted to report an issue we noticed in case it’s a bug. If you decorate a generic task with the Name attribute to provide a custom name, you’re no longer able to select the generic type. Instead it chooses one type and forces you to use that. We were using a constraint on the generic so I’m not sure if that was affecting it. Once the Name attribute is removed it works as expected.
Hello,
Thank you for the report.
This was a known bug indeed, and which has now been fixed in the latest version that has recently gone live on the asset store! 🙂
If you encounter anything else, please let me know.
Thanks.
Join us on Discord: https://discord.gg/97q2Rjh
Author
Posts
Viewing 2 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic.
Login
Register
By registering on this website you agree to our Privacy Policy.