Verse Language Version Updates and Deprecations in Verse

Starting November 1, 2024 in the 32.00 release, we are stabilizing the Verse language to Version 1. We recommend you that upgrade your project both for stability and so that it’ll be easier to upgrade your code incrementally when future Verse language updates arrive. This upgrade is optional; your current version of the project will always continue to work at an older Verse version. That being said, there may be a point in the future where you will need to upgrade your project to a newer Verse version if you want to upload a newer iteration of it.

Since its first public release, we have continued to and evolve the Verse language, with those changes transparently rolling out to users without requiring an upgrade to a new language version. We anticipate that this will continue, with most language changes being backwards compatible with previous versions of the language and rolled out to users with new releases of UEFN.

However, some language changes are not backwards compatible, and may require changes to your code in order for the code to compile. Such backwards incompatible changes will only be triggered if the user upgrades their project to target the new language version.

Warnings will appear any time you save code that is not backwards compatible and indicate your code behavior is deprecated in newer versions of the language. For example, continuing to use coding practices that aren’t compatible with the new Verse Language version result in warnings about your code.