ShinyAndroid Well-known member Featured Contributor Joined Oct 14, 2020 Messages 75 Reactions 394 Jan 28, 2025 #1 I'm kinda confused on this. I'm making an update to an old scene - which I've done before without issues. But this time, the update, V2, references V1 as a dependency. its not a huge deal I guess, but I'd prefer it didn't do that. Any idea why?
I'm kinda confused on this. I'm making an update to an old scene - which I've done before without issues. But this time, the update, V2, references V1 as a dependency. its not a huge deal I guess, but I'd prefer it didn't do that. Any idea why?
ShinyAndroid Well-known member Featured Contributor Joined Oct 14, 2020 Messages 75 Reactions 394 Jan 28, 2025 #2 Well. I'm not sure what happened but I went to package it again and it had a button to fix the reference. So it's all good now! lol
Well. I'm not sure what happened but I went to package it again and it had a button to fix the reference. So it's all good now! lol
SlimerJSpud Invaluable member Joined May 18, 2022 Messages 2,227 Solutions 44 Reactions 1,481 Jan 28, 2025 #3 Selecting fix references makes it package custom items with the new var, rather than linking to the old one, I believe.
Selecting fix references makes it package custom items with the new var, rather than linking to the old one, I believe.