You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
IMO it's more convenient to add a plugin in order to add addational functionality to an Unreal project than to copy another project's content folder into the content folder of one's own project and It's also less error prone: The first time I copied your content folder into a subdirectory of my content folder, which broke your assets' dependencies and nothing worked anymore. Copying your content folder again into the root directory of my content folder worked, but if I wouldn't have read a comment on the unreal stating that this is still UE5 compatible I would've just assumed your work has been deprecated. If this were a plugin, I couldn't have even made this mistake.
The text was updated successfully, but these errors were encountered:
Yes this repo is kinda deprecated, as the last time it has been updated was 4 years ago.
I left it up and running as I think some people still find it useful, but I don't have any plans on updating it atm.
I'm not super well versed in UE programming and have never written a plugin before, but if anybody would like to do, forks/PRs are appreciated :)
Haha, it really isn't that hard to make a plugin 😄 Just open the project in the editor, clock on Edit -> Plugin, click on "New Plugin", select the Blank template and enter a name, click on "Create" and let Unreal do its thing. Once finished, there should be a new "Plugins" directory with a subdirectory for your plugin in your content drawer. You're then free to move all your assets over to your plugin's directory. Functionally, nothing should change, but the plugin can be installed more easily by moving it into another project's Plugins directory and uninstalled by deleting it from there.
If you want, I can still do all that for you when I have some time to spare, I just wanted to let you know that plugins aren't as scary as you might think 😄
IMO it's more convenient to add a plugin in order to add addational functionality to an Unreal project than to copy another project's content folder into the content folder of one's own project and It's also less error prone: The first time I copied your content folder into a subdirectory of my content folder, which broke your assets' dependencies and nothing worked anymore. Copying your content folder again into the root directory of my content folder worked, but if I wouldn't have read a comment on the unreal stating that this is still UE5 compatible I would've just assumed your work has been deprecated. If this were a plugin, I couldn't have even made this mistake.
The text was updated successfully, but these errors were encountered: