USE_EQS_DEBUGGER affects runtime EQS results in SingleResult mode

The licensee described it really well so I'll just copy what he said:

When EQS debugging is enabled via USE_EQS_DEBUGGER, queries run in 'SingleResult' mode will not clear discarded items from the result structure. This prevents end users from using the convenient GetAllAs* API to grab whatever is in the result.

The end user is required to store what mode the query was run in so that they can know if they need to explicitly grab the zero-index item to avoid discarded data. This paradigm is shown in UEnvQueryInstanceBlueprintWrapper. The results struct does not provide a way to check for discarded items and it does not contain the run mode to know which API is safe to use. Only one run-mode returns discarded data. It seems the more symmetrical and clean solution would be to have an explicit API to retrieve debug data (i.e discarded items) so that user code can always have a safe API to call.

Fix UE-51650

"Session Disconnected" UEFN

I am not able to find world outliner how to enable it?

Undefined sysmbol: typeinfo for AActor when cross-compile linux dedicated server on windows

Delay nodes occasionally don't fire the "Completed" output in a nativized build

Error UE5 5.0.3

How can i modify the param name in EQS node

I can't open my map from the editor.

What method is used to fill polygonal regions when drawing spline mesh at run time?

My map looks so rigged because part of the skybox is missing it says "Your scene contains a skydome mesh with a sky material but it does not cover that part of the screen