• Change bUseUObjectArrayCache to false in 'UE4SS-Settings.ini', if this doesn't work then you have an outdated mod somewhere causing the issues. Remove all mods and add them back one by one until you figure out what's causing the crashes.

• Make sure you don't have xinput1_3.dll and dwmapi.dll in the same folder. If you do then delete xinput1_3.dll as this is an older version of UE4SS (2.5.2) and you have no reason to be on this old version plus it conflicts with the newer dwmapi.dll version (3.0.0+). These are located in the same folder where you installed UE4SS.

• You might have a UE4SS_Signatures folder in your UE4SS installation folder in which case delete the UE4SS_Signatures folder. It is not needed anymore with UE4SS 3.0.0+ despite what some mods might be saying and will only cause issues.

• You have outdated mods, remove all of them and add them back in one by one until the crashes start to occur again to figure out which mod is causing issues.

• If the mod is crashing when you're pressing F1, make sure your game is up to date (0.3.3 Currently) and that you're not using the Steam version of the mod if you're on Game Pass.

This could be caused by the following:

• If you're on a laptop then there's a chance you might want to change the keybind to something other than F1 or you don't have an F1 key in the first place, in which case you can change it. See the FAQ section on how to change the keybind.

• You didn't follow the installation instructions properly. Verify that CreativeMenu.pak is in LogicMods as seen in the image below.
  

• mods.txt is empty, I am not really sure why people are having this issue, but you should have the following inside the mods.txt:

CheatManagerEnablerMod : 1
ActorDumperMod : 0
ConsoleCommandsMod : 1
ConsoleEnablerMod : 1
SplitScreenMod : 0
LineTraceMod : 0
BPModLoaderMod : 1
BPML_GenericFunctions : 1
jsbLuaProfilerMod : 0




; Built-in keybinds, do not move up!
Keybinds : 1

• You went ahead and edited mods.txt, you should NEVER touch this file ever because it will break things if you don't know what you're doing. It doesn't matter if X mod is telling you to change things in mods.txt, do not touch this file ever. If this is the case then you most likely have BPModLoaderMod set to 0, ensure it is set to 1 as seen in the image in the previous point.

• You are missing BPModLoaderMod in your Mods folder. I've seen cases where people have deleted the Mods that come with UE4SS thinking that they are optional. Do not delete any of the mods that come with UE4SS because this will once again break things. If this is the case then reinstall UE4SS.

• You installed my temporary BPModLoaderMod fix as a client. This fix is not meant to be installed as a client, redownload UE4SS and replace BPModLoaderMod with the original one.

• You have mods that shouldn't be in LogicMods. Generally anything ending with _P should be in the 'Paks' folder rather than the 'LogicMods' folder as these are 'patch mods' rather than UE4SS mods, but of course this isn't as simple anymore because people started adding _P to LogicMods even though this is specifically reserved for Unreal's built-in modding system. In this case, refer to each mod's installation guide and install the mods properly.

Join the discord server and send the UE4SS.log file in the #help channel. Instructions on how to find the UE4SS.log file can be found here: Finding UE4SS.log

Keep in mind if you're using a pirated copy of the game, you won't be receiving any help.