Setting Up A Basic Mod

Where we left off would be Double-clicking Pal.uproject, You should see this screen PDKNewProject

ModActor Setup

In your Content Browser If there isn't a Folder ( ) named Content make one.
In Content make a Folder ( ) called Mods This is where any mod we make will be at.
Your folder structure should look similar below. (Ignoring dabzQOL and dabzReflex)
Create a Folder ( )in Mods with the name you want your Mod's Pak file to be called. (In this case, I'll be using dabzReflex)
In that Folder ( ), We will be creating a new Blueprint Class that is a Actor. It will be called ModActor
Now your Content Browser should look like so, next double-click your ModActor and make sure you are on the Event Graph tab
Now your ModActor is technically setup, there is some more information to know about it below though.

PreBeginPlay - This event is too early to use to initialize your mod. (Only Works In ModActor)
PostBeginPlay - This event is fired when the Player Controller Begin Play is called (Only Works In ModActor)
- The suggested event to use for initializing most things in your mod.
Event Tick - This event is fired every single tick.
- This is commonly used if you need a event that is updating every single game tick
PrintToModLoader - Allows the ability to log to UE4SS Console through a blueprint. (Only Works In ModActor)
- To use this event, Create a Custom Event in your ModActor called PrintToModLoader exactly.
- Add a initial String variable to this event, called Message. Leave the event alone now.
- You can now call a new function called Print To Mod Loader anywhere.
ModMenuButtonPressed - Used to enable ModButtons in UE4SS's mod list area. (Only Works In ModActor) ModButtons Tutorial

ヒント

ModActor variables are used to display information about your mod in UE4SS's loaded mod category.

They are simply just variables added to your blueprint, that are not used by your Blueprint, they are only used by UE4SS.

ModActorVars

ModActorVarsSetup