Replies: 2 comments
-
I agree, I currently have to grab the asset using a GUID and then pass in the ID from that asset class. This is because while the methods take ID, I still prefer using GUID in the configuration because of the planned obsolescence of the legacy IDs. |
Beta Was this translation helpful? Give feedback.
0 replies
-
You're right that it would be a good and useful improvement. Would like to address as part of continuing guid support everywhere, unsure if next update. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Normal effects already support GUID and almost the majority of the game is already working with GUIDs so it will make sense to create new methods for sending UI's by GUID and mark ID's as obsolete.
The majority of plugins now days use UI's so getting an non used ID is a bit annoying, I usually kept track of my ids to avoid issues but it's hard to do the same for other UI's, so moving to GUIDs seems the most logical next step for this and due you're already on that way I'm creating this post to, with a bit of hope, have this added to the game for next update.
Beta Was this translation helpful? Give feedback.
All reactions