Dartwraith wrote: ↑Tue Apr 09, 2019 2:09 pm
Can you add in the cheat table function to unblocking cheats, developer console and so on?
How to have to obtain initial Borderlands engine commands, i.e.:
behindview (0/1) = camera firstperson (thirdperson)
playeronly = notarged
ghost = ?
fly = ?
walk = ?
slomo = ?
....
In some sources i readed that in Borderlands direct input of engine command (of unreal engine itself) was blocked by gearbox.
But they used own command list.
I tested the first table you linked in BL2 and patching "Disable Console Say" + the rest. It doesn't do shit aside from allowing some basic engine commands to pass the "say" filter
That being said fly, god, etc. won't work anyway because they're not part of the runtime autocomplete list.
But then again, I found this post:
[Link] Will see what it is that "Enable Developer Commands" actually does.
EDIT - It does this:
[Link] (the second part)
Dartwraith wrote: ↑Wed Apr 10, 2019 9:13 am
There are 2 way to obtain cheats:
1 - with debug information find new commands from gearbox like i wrote above matched to original UE cheats
2 - inject the cheats commands by ChEn like at this cheat table "Borderlands_UEcheats.ct" (on Enhanced doesnt work)
Incorrect. Number #2 is not working as you're explaining it. I had to determine the native functions' effects and replicate that in all UE3 games I wrote tables for. That's not "injecting", it's simply code rebuilding. In some games just emulating the CheatManager and allowing console access will also allow you to use the native commands. But that is because those commands
exist. In BL games they don't.
I'm currently working out the x64 part and enabling the shitz in Enhanced as well. Hold tight.
BR,
Sun