# Unusable Verse modules

**URL:** <https://forums.unrealengine.com/t/unusable-verse-modules/1367579>\
**Category:** Issues and Bug Reporting\
**Tags:** unreal-editor-for-fortnite, fortnite-creative, fortnite\
**Created:** [November 6, 2023, 6:42am UTC](https://forums.unrealengine.com/t/unusable-verse-modules/1367579 "2023-11-06T06:42:27Z")\
**Posts on this page:** 1\
**Showing post:** 11

<div class="post-metadata">

**Author:** ![t.tutiya](https://d1ap1mz92jnks1.cloudfront.net/user_avatar/forums.unrealengine.com/t.tutiya/32/924637_2.png) [@t.tutiya](https://forums.unrealengine.com/u/t.tutiya)\
**Post date:** [April 17, 2024, 7:21am UTC](https://forums.unrealengine.com/t/unusable-verse-modules/1367579/11 "2024-04-17T07:21:01Z")

</div>

More info. From: Ask Epic : Verse

> [@Ask Epic: Verse - March 28 @ 10:00 AM ET](https://forums.unrealengine.com/t/ask-epic-verse-march-28-10-00-am-et/1765393/98):
>
> Due to the way the compiler is currently implemented, processing of types is very dependent on the order the types occur, most obvious with parametric types. This can be resolved in the same file by reordering definitions, but ordering between files is not specified. MaxVerse will alleviate this issue via pervasive leniency.

> Due to the way the compiler is currently implemented, processing of types is very dependent on the order the types occur, most obvious with parametric types. This can be resolved in the same file by reordering definitions, but ordering between files is not specified. MaxVerse will alleviate this issue via pervasive leniency.

---

_[View the full topic](https://forums.unrealengine.com/t/unusable-verse-modules/1367579)._
