# Should I make blueprint content compatible with older versions?

**URL:** <https://forums.unrealengine.com/t/should-i-make-blueprint-content-compatible-with-older-versions/345649>\
**Category:** Blueprint\
**Tags:** compatibility, unreal-engine, question\
**Created:** [January 28, 2016, 1:53pm UTC](https://forums.unrealengine.com/t/should-i-make-blueprint-content-compatible-with-older-versions/345649 "2016-01-28T13:53:13Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Nicat](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@Nicat](https://forums.unrealengine.com/u/Nicat)\
**Post date:** [January 28, 2016, 1:53pm UTC](https://forums.unrealengine.com/t/should-i-make-blueprint-content-compatible-with-older-versions/345649/1 "2016-01-28T13:53:13Z")

</div>

Hey. I have made blueprint for marketplace using UE4 10.1 and thinking about to make it compatible with older versions before sending it. Do you think I should go through manually creating whole blueprint again using older version of UE (just tried copy pasting nodes and it crashed :P) or is it not worth it -in case no one (very few people) uses older versions- ?

---

<div class="post-metadata">

**Author:** ![teak421](https://d1ap1mz92jnks1.cloudfront.net/user_avatar/forums.unrealengine.com/teak421/32/902996_2.png) [@teak421](https://forums.unrealengine.com/u/teak421)\
**Post date:** [January 28, 2016, 11:39pm UTC](https://forums.unrealengine.com/t/should-i-make-blueprint-content-compatible-with-older-versions/345649/2 "2016-01-28T23:39:56Z")

</div>

Not sure if there is a way to tell how many people would start a new project on an older version… Meaning, if it was me… I would make certain that it works with 4.10 and 4.11 and nothing more. Haven’t most folks updated for new projects? BUT, I guess if someone wanted to use your product with their project then maybe you should. Wow, I was not helpful at all!

---

<div class="post-metadata">

**Author:** ![Nicat](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@Nicat](https://forums.unrealengine.com/u/Nicat)\
**Post date:** [January 29, 2016, 9:28am UTC](https://forums.unrealengine.com/t/should-i-make-blueprint-content-compatible-with-older-versions/345649/3 "2016-01-29T09:28:21Z")

</div>

Thanks for taking your time to answer. This question can’t be answered directly anyway. At least one user is using 4.10 for sure so I I’ll just go for 4.10-11 😃

---

<div class="post-metadata">

**Author:** ![anonymous\_user\_b4265237](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@anonymous\_user\_b4265237](https://forums.unrealengine.com/u/anonymous_user_b4265237)\
**Post date:** [November 9, 2016, 1:08pm UTC](https://forums.unrealengine.com/t/should-i-make-blueprint-content-compatible-with-older-versions/345649/4 "2016-11-09T13:08:12Z")

</div>

Reviving this topic… I want to submit an audio pack with arranged sound cues to the latest version as well as older versions, what would be the best solution? (apart from downloading the previous versions of the engine and start opening and saving the new projects)

---

<div class="post-metadata">

**Author:** ![anonymous\_user\_b9532c9a](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@anonymous\_user\_b9532c9a](https://forums.unrealengine.com/u/anonymous_user_b9532c9a)\
**Post date:** [November 28, 2016, 7:06pm UTC](https://forums.unrealengine.com/t/should-i-make-blueprint-content-compatible-with-older-versions/345649/5 "2016-11-28T19:06:11Z")

</div>

Hi ,

We only require the last two engine versions to be compatible (or the latest engine version for brand new content). However if you choose to support previous engine versions, the best way to do this is create a copy of the project in the earliest engine version you want to support. Check to ensure that it is supported in the engine versions after this and we can use that project.
