# Change default blueprint for StaticMeshActor

**URL:** <https://forums.unrealengine.com/t/change-default-blueprint-for-staticmeshactor/436516>\
**Category:** Blueprint\
**Tags:** unreal-engine, config, defaults, editor, Blueprint, question\
**Created:** [October 27, 2018, 10:51am UTC](https://forums.unrealengine.com/t/change-default-blueprint-for-staticmeshactor/436516 "2018-10-27T10:51:51Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![SuperRey](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@SuperRey](https://forums.unrealengine.com/u/SuperRey)\
**Post date:** [October 27, 2018, 10:51am UTC](https://forums.unrealengine.com/t/change-default-blueprint-for-staticmeshactor/436516/1 "2018-10-27T10:51:51Z")

</div>

In the same way we can override the PlayerController class, GameInstance class, etc. is there a way to set a default blueprint class to use instead of StaticMeshActor?

---

<div class="post-metadata">

**Author:** ![sjcobs](https://d1ap1mz92jnks1.cloudfront.net/user_avatar/forums.unrealengine.com/sjcobs/32/918649_2.png) [@sjcobs](https://forums.unrealengine.com/u/sjcobs)\
**Post date:** [October 27, 2018, 2:35pm UTC](https://forums.unrealengine.com/t/change-default-blueprint-for-staticmeshactor/436516/2 "2018-10-27T14:35:05Z")

</div>

No. I’m not sure that even makes sense though. You can create your own class of static mesh actor if you want, just like any other class. Then you could use that where you wanted. But there is no such thing as a default static mesh actor. You would simply create a custom one and use it anytime you wanted.

---

<div class="post-metadata">

**Author:** ![SuperRey](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@SuperRey](https://forums.unrealengine.com/u/SuperRey)\
**Post date:** [October 28, 2018, 9:41am UTC](https://forums.unrealengine.com/t/change-default-blueprint-for-staticmeshactor/436516/3 "2018-10-28T09:41:57Z")

</div>

The idea is to have custom functionality for each mesh imported into the project right after importing, instead of wrap each mesh with an appropiate Blueprint class after the import is done. Does it make more sense?