Lyra should be put on Github

Any update on this?

When Epic says, “I will look into it”, it’s the same as “I’ll just throw it into the trash” It sounds so familiar to me. Basically, Epic treats the community like nullptr and they will never change no matter how much money they make.

If Epic is saying Lyra is a template that serves as the Best Practice, they should at least let us know how to properly patch it, let alone, letting us know what changed.

I do not want to touch any of Lyra BP code as it will cause nightmares to patch later on and dealing with BP freaking frustrating. I think it’s the biggest mistake that they removed ScriptingLanguage from UE4 and gave us BP only instead. It’s 10 years too late to realize that ScriptingLanauge is needed.

I expect once Verse is released, most of Lyra’s BP code is ported to Verse so that patching will not be such a mess and I believe they will at least give us a Verse version if they still want to push it as the Best Practice template.

Oh well, after careful investigations, I just decided to wait until Verse releases. I believe Verse will let me catch things up pretty quickly without having to waste time dealing with BP.

Don’t get me wrong, BP has some purpose, but it’s horrible in many situations.

Any update on this?

Any news on this?

Yes Please you got my Vote

1 Like

Just FYI to anyone interested in this. I asked on UDN about this and the official word as of 2022-10-01 is this: There is no official word.

Internally there are some folks at Epic who want to do this. They’re trying to make it happen. There are some obstacles they need to overcome. There is no timeline.

In the interim, DO NOT GIVE AWAY THE LYRA SOURCE CODE by putting it in a public Github repository. You can put it in a private repo that only you and your team can access, but DO NOT MAKE THE CODE PUBLIC.

Epic owns the Lyra code. They license it to us via the UE5 license that we all agreed to. You wouldn’t publish the UE5 Engine code would you? (Answer: No). So don’t publish the Lyra code either.

Hopefully Epic will make some progress on this before too much longer.

3 Likes

I believe Verse is long way from coming to main UE5 branch, moreover Lyra remade with it. It’d rather be sth much simpler in scope as a example usage.
Most of observes see it released initially as part of UEFN - custom standalone Unreal Engine editor for Fortnite, commonly known as Creative 2.0. Probably limited to Fortnite API exposed via it without much ability to tinker with Verse itself beyond scripting runtime behaviour for Fortnite.

Alas, there are hints that later Verse in UE5 might happen. Tim mentioned during UEFN reveal stream in 2021 that “everything Fortnite eventually ends in UE” and Epic is hiring for position like this: Senior Visual Language Programmer

2 Likes

Hello all, good news!
Lyra has been put in GitHub!! :partying_face: :partying_face:
https://github.com/EpicGames/UnrealEngine/tree/ue5-main/Samples/Games/Lyra

5 Likes

For a little more context: Lyra Starter Game Source Code Now on GitHub

Thanks for the feedback everyone!

4 Likes

This topic was automatically closed after 10 days. New replies are no longer allowed.