# Please Improve Your Systems or At Least The Documentation Epic Games

**URL:** <https://forums.unrealengine.com/t/please-improve-your-systems-or-at-least-the-documentation-epic-games/1268802>\
**Category:** Verse\
**Tags:** unreal-editor-for-fortnite, fortnite-creative, fortnite\
**Created:** [August 22, 2023, 1:12pm UTC](https://forums.unrealengine.com/t/please-improve-your-systems-or-at-least-the-documentation-epic-games/1268802 "2023-08-22T13:12:30Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![EpikGeymir](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@EpikGeymir](https://forums.unrealengine.com/u/EpikGeymir)\
**Post date:** [August 22, 2023, 1:12pm UTC](https://forums.unrealengine.com/t/please-improve-your-systems-or-at-least-the-documentation-epic-games/1268802/1 "2023-08-22T13:12:30Z")

</div>

Dear Epic Games,

This is not a question, this is a feedback letter for you and I’m making it public so that community can see it as well.

Today, through this error, I have learned that structs have a max size, if you have a struct with a size larger than the max, you encounter this error and a launch crash when launching a session.

Error Log In Question:  
“LogWindows: Error: appError called: Assertion failed: GetIntNum(Property, IntType) \< MaxZeroComparisons [File:D:\build++Fortnite\Sync\Engine\Source\Runtime\CoreUObject\Private\Serialization\UnversionedPropertySerialization.cpp] [Line: 166]  
Unexpectedly large property type encountered $ExprResultStack\_17”

Message to you Epic Games, here is what you could do instead and become a proper company:

- 
  1. First of all, if there is a hard size limit for structs, how the hell am I even allowed to compile the script without any problems. Compile should give me a clear error, instead of an ambiguous server launch error.

- 
  1. I do understand the needs and requirements of having max memory allowed for scripts, and the total of the map. But having a limited size for a property is just lazy. I should be fine as long as my total memory consumption is ok.

- 
  1. Or if you’re so defensive about you hard size limit for structs you can at least let me have 1byte, 2 byte short and 4 byte integer and float (which is what they should be named, what was your idea on making the INT and FLOAT as 8 bytes, when almost everywhere else it’s 4 bytes. You could have just named them something else if you really wanted to make them 8 bytes, for example: StupidEpicGames8ByteInt and StupidEpicGames8ByteFloat), so that I can have more members in one struct without you changing the max struct size.

- 
  1. The Documentation, You have a hard size limit on your structs and it’s not mentioned anywhere, not even once, are you serious! Even if you are lazy enough to not add it as a static check to the compile process, at least write the useless documentation properly.

---

<div class="post-metadata">

**Author:** ![AndrewScheidecker](https://d1ap1mz92jnks1.cloudfront.net/user_avatar/forums.unrealengine.com/andrewscheidecker/32/926976_2.png) [@AndrewScheidecker](https://forums.unrealengine.com/u/AndrewScheidecker)\
**Post date:** [August 22, 2023, 2:40pm UTC](https://forums.unrealengine.com/t/please-improve-your-systems-or-at-least-the-documentation-epic-games/1268802/2 "2023-08-22T14:40:39Z")

</div>

Thanks for the report. There isn’t a limit on the size of structs, and it’s a bug that you get that error.

We’ve fixed one bug already that triggered this error for large optional structs (e.g. `?my_large_struct`), but that fix is not yet in the public release of Fortnite. I believe that’s what you’re seeing here, but can you confirm that you’re hitting this bug for a large optional struct, and not simply for a large struct?

---

<div class="post-metadata">

**Author:** ![EpikGeymir](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@EpikGeymir](https://forums.unrealengine.com/u/EpikGeymir)\
**Post date:** [August 22, 2023, 2:45pm UTC](https://forums.unrealengine.com/t/please-improve-your-systems-or-at-least-the-documentation-epic-games/1268802/3 "2023-08-22T14:45:05Z")

</div>

It’s not an optional struct just a plain struct

---

<div class="post-metadata">

**Author:** ![AndrewScheidecker](https://d1ap1mz92jnks1.cloudfront.net/user_avatar/forums.unrealengine.com/andrewscheidecker/32/926976_2.png) [@AndrewScheidecker](https://forums.unrealengine.com/u/AndrewScheidecker)\
**Post date:** [August 22, 2023, 7:01pm UTC](https://forums.unrealengine.com/t/please-improve-your-systems-or-at-least-the-documentation-epic-games/1268802/4 "2023-08-22T19:01:14Z")

</div>

What about a function with the `<decides>` effect that returns the “large” struct?

---

<div class="post-metadata">

**Author:** ![100T\_Damon](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@100T\_Damon](https://forums.unrealengine.com/u/100T_Damon)\
**Post date:** [August 23, 2023, 3:07am UTC](https://forums.unrealengine.com/t/please-improve-your-systems-or-at-least-the-documentation-epic-games/1268802/5 "2023-08-23T03:07:15Z")

</div>

I ran into the same issue today, and was able to resolve it by removing the effect from a function that returned the impacted struct.

The problem can also be resolved by changing the impacted structs to classes. I ultimately opted for this approach, as it does not require changing any other parts of the codebase.

---

<div class="post-metadata">

**Author:** ![100T\_Damon](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@100T\_Damon](https://forums.unrealengine.com/u/100T_Damon)\
**Post date:** [August 23, 2023, 7:24am UTC](https://forums.unrealengine.com/t/please-improve-your-systems-or-at-least-the-documentation-epic-games/1268802/6 "2023-08-23T07:24:31Z")

</div>

I ran into the same issue today, and was able to resolve it by removing the `<decides>` effect from a function that returned the impacted struct.

The problem can also be resolved by changing the impacted structs to classes. I ultimately opted for this approach, as it does not require changing any other parts of the codebase.

---

<div class="post-metadata">

**Author:** ![AndrewScheidecker](https://d1ap1mz92jnks1.cloudfront.net/user_avatar/forums.unrealengine.com/andrewscheidecker/32/926976_2.png) [@AndrewScheidecker](https://forums.unrealengine.com/u/AndrewScheidecker)\
**Post date:** [August 30, 2023, 6:11pm UTC](https://forums.unrealengine.com/t/please-improve-your-systems-or-at-least-the-documentation-epic-games/1268802/7 "2023-08-30T18:11:39Z")

</div>

The fix is in the 26.00 build of UEFN that is now live. Please let us know if you see the problem again.
