More technical solutions are ReadProcessMemory from Kernel32 or DLL injection.
Either hook/detour the WriteGameLog function (best method and very reliable) or scan the memory space until you find where log text is stored and search for your keyword, this is unreliable since text chars can begin and end anywhere and the offsets tend to change based on memory allocation. And only way to detect where they end is by '\0' which can be junk also...