Should I Build inside "Character" or "Player" BP?

I hope this question is understandable, but allow me to explain;

I’m a noob (clearly) and recently purchased an inventory blueprint from the marketplace and it contains both a “character” blueprint and a “player” blueprint. The “character” blueprint inherits the active mesh from the “player” bp, but contains functions that deal with equipping items, using items, attribute regeneration, etc. The “player” bp contains the mesh, but inherits equipment locations, and includes all functions that deal with axis and action mapping, the UI, interaction, etc.

So basically, what is a good standard when it comes to adding additional functionality? Does it matter which bp I build in? Will building in one a TON but the other, very little have certain effects?

I hope this all makes sense because as I start to learn more and add more, I grow more and more paranoid that I may be building my blueprints incorrectly.

Finally, as a side note, I have been trying to contact the creator of the marketplace asset but have been having extreme difficulty in doing so, and it seems others have been as well. That’s why I’m here :slight_smile:

THANK YOU!

I am assuming you are referring to the Character BP and the Player Controller BP.

Depending on what type of game you are making it matters more than in other game types. For multiplayer games I have found that putting most of your code in your Character BP works quite well. The only thing I use the Player Controller BP for is input and UI elements. You may have to experiment a bit depending on your game type. If your game allows the player to switch which characters it is possessing during game play, it will be especially important that you divide the code properly.

You may also want to structure your character BP differently if you plan on reusing it with an AI Controller (mobs). Sometimes you may even want multiple levels of Character BP, such as a Base Character BP that is then inherited by a Player Character BP and a Mob BP.