#1 - As many as you want!#2 - Yes, tutorial/documents to explain everything are encouraged. For 4.5 we’re expanding the editor tutorial system to better support this (including allow tutorials to be created entirely within blueprints).#3 /#4 - I’d suggest working with the starter/template content.
Hi everyone,
I’m considering submitting some blueprints that I have made for various purposes but just have a few questions to clarify about what needs to be included with the submission.
If there are multiple blueprints used to achieve the one mechanic, i.e. character bp, weapon bp, HUD bp, can these all be included in the one package? Or can you only submit ONE bp at a time?
If the overall mechanic of the bp’s needs communication with the level bp, is it ok to include a tutorial on how to set up the level bp for the package? Or can the level bp info be included in the package as well?
If the overall mechanic requires use of a playable character with sockets, and assets, such as weapons, can this content be included with the bp package? Or does it have to be a separate asset package? Or can a tutorial explain how to work with the starter assets from epic to make the bp functional?
Related to the above question, if a playable character plus weapons and sockets can be included, can we use the character from the starter content included with the engine? Can we also use weapons or other assets migrated from other free epic projects, just for functionality, with the intention that the developer swaps in their own content? Or does it have to be our own content from the top?
Think that’s it for the moment, any help or advice would be much appreciated.
Cheers,