UFunction * cm = (UFunction*)UObject::FindObject('Function ') Here, a code for demonstration with ME3 On The Hook: I figured I had to use Console.OutputText earlier, but only after downloading UDK I realized how it is supposed to be called. ME3's PlayerController.TeamMessage is as 'empty' as ClientMessage. This was found in the TeamMessage from UDK.

So you may ask 'What about ME3?' - well, let's take a look at Engine.pcc with PCC Editor 2.ġ) Rebuild ClientMessage from scratch via hex.Ģ) Change all references in all PCC's, from Outer.ClientMessage to something else.Īfter some tests here and there, I finally found what actually has to be coded into ClientMessage: ssage2.png -> Here I opened PlayerController.uc (not actually recommended unless you know what you're doing, even Unreal X-Editor warns about this) and I put everything from ClientMessage into a comment tag. ssage1.png -> CheatTestMessage was created by me, and it uses Outer.ClientMessage. I have here screens of a test I did with it using UDK-2011-12: Its actual 'identity' is PlayerController.ClientMessage, from the Engine package.

The original behavior (what Epic did in UT3 and other Unreal games I played) makes the game write the message on the screen (temporally) and on the console. Long story: Outer.ClientMessage is used by various functions/methods in order to give feedback to the player (example: God - 'God mode on', Ghost - 'You feel ethereal'). Outer.ClientMessage caught my attention in the past, but only now I tried to actually restore it.

Winject mediafire