ConsoleUtils - UE4SS

Users:

Automatic installation

Mod managers should now automatically install this to the correct location.

Manual installation

Place the folder "ConsoleUtils" in the following directory depending on if you're using the Steam version or the Gamepass version of Oblivion:

Steam Users:

"Oblivion Remastered\OblivionRemastered\Binaries\Win64\ue4ss\Mods\"

Gamepass Users:

"Oblivion Remastered\OblivionRemastered\Binaries\WinGDK\ue4ss\Mods\"

Modders:

Adds a new function ExecuteConsoleCommand(command) that is accessible to all Lua mods.

This new function returns the results of a Console Command as a string. This SHOULD be compatible with OBSE64 since the new functionality in OBSE64 is built into the same list of console commands that this ExecuteConsoleCommand method is using, but I haven't personally tested it thoroughly. This is enables the use of a substantial amount of functionality that isn't exposed to the UE side of the Oblivion Remastered engine at all. Example commands that users could make use of are GetActorValue, GetCombatTarget, GetCrime, GetEquipped, GetFactionRank, GetItemCount, IsTrespassing, GetBaseActorValue, HasMagicEffect, GetInSameCell. Other potentially useful console commands can be found at: https://cs.uesp.net/wiki/Category:Function_Types_(CS_1. 0) This mod is using AoB (array of byte) patterns to identify the internal functions and variables that it depends on, so hopefully it won't require updating to keep up with future Oblivion Remastered patches, but it's always possible for those functions to change substantially enough that it needs updated. If it does, please ping me and I'll try and get it updated when I can.

Caution:

Call only from in the Game Thread, either via hooking functions (like ReceiveTick on an Actor), or via ExecuteInGameThread (although it's worth noting that there's a bug in the current release of UE4SS where ExecuteInGameThread occasionally executes outside of the game thread). The `ExecuteConsoleCommand` function does detect if you attempt to call it from an incorrect thread and prevents itself from firing to avoid crashing the game. If it is called outside of the game thread, it will return an error message starting with "Failed to run command." that you can check for to determine if you need to retry the command in another ExecuteInGameThread block. This setup is necessary to be able to get the response of the console command. As mentioned in the Potential Future Features section, I might at some point add the ability to call this function from within Exe