Important: 24.00 is last version of UEFN that supports vmodule file removal

If you still have any .vmodule files in your project now is the time to get rid of them! See this post for the instructions. When 24.01 goes live on Monday, the auto-conversion hack will no longer be present in UEFN.

If you are experiencing any trouble with converting your project reply to this thread and we’ll do our best to help you!

This doesn’t seem to work in 24.10:

The above changes might change the access level of your module from <public> to <internal>, since that is the default access level for modules defined via directories. In most cases this will work just fine. However, if you need your module to be <public>, you have to place a module macro in a Verse file adjacent to your directory that specifies MyModule<public> := module:. Multiple definitions of modules are allowed (called partial module definitions, as long as only one is explicit (a module macro).