Nearly every tutorial I see online has me shoving endless amounts of stuff into the Level Blueprint. Is there any reason why I should try and learn to use it with the “self contained” blueprints? I haven’t found much information on the subject, which makes me nervous to try it out. Everyone seems to default to level, but somebody at my school (who knows a lot more about UE4 than me) suggested that I stop doing this, as it will inhibit my work at some point.
one problem with doing things in the level blueprint is that the logic will only exist in that one level. as a general rule in my opinion the only things to go into a level blueprint are things that are relevant only to the current level (scripted events within the level). Of course you can put whatever you like in the level blueprint and its entirely up to you. Some of the positive points to using separate actors and things for different aspects would be: re-usability as in you can re-use things in different levels or as parts of different actors, organization - you can organize your project better and find the code your looking for quicker, etc. The more you work in unreal and the more scripting you do the more you will realize that actors are a good way to go. i actually dont see many tutorials that use the level blueprint but i would guess the ones youve seen use it because its easy to get references to things in the level while using the level blueprint.
I cant believe how many tutorials are teaching using the level BP, I come across them all the time. My only guess is that its easier for a self contained tutorial or something.
But here is the thing, you can do things with the level bp that you can’t with any other bp. You need a direct reference to things dragged into the level? The level bp is it.