Skip to content

[FEATURE] - Separate Blueprints for different engine versions but using the same link #28

@gtreshchev

Description

@gtreshchev

My problem

Is your feature request related to a problem? Please describe.
Some Blueprint nodes aren't whether forward or backward compatible, leading to the loss of certain nodes (e.g. from UE 5.1 when copy-pasted into UE 5.3).

My suggestion

Describe the solution you'd like
It would be great if there were a feature on the website to organize Blueprint nodes separately for different engine versions. End users could then have a switcher/toggler between the engine versions, automatically updating the Blueprint nodes.

Alternatives

Describe alternatives you've considered
A more comprehensive fix would be to automatically modify the Blueprint nodes based on the engine version, addressing the most common compatibility problems across different engine versions, though this would be a highly complicated task :)

Additional context

This would be particularly useful for developers aiming to support multiple engine versions for their Blueprint nodes but facing issues with forward/backward compatibility. For example, in the case of RuntimeSpeechRecognizer: gtreshchev/RuntimeSpeechRecognizer#17 (comment)

Metadata

Metadata

Assignees

Labels

feature/websiteNew feature or request on blueprintUE website

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions