FrameScriptExecuteBuffer protection on Classic?

[Mr.Sergey]

Hello,

That seems like Blizz applied some protection on FrameScriptExecuteBuffer in last update 1.13.6.36714 deployed today, now game client crashes on attempt to call it.

Could someone share some solution if one exists, please?

[aeo]

Hello,

That seems like Blizz applied some protection on FrameScriptExecuteBuffer in last update 1.13.6.36714 deployed today, now game client crashes on attempt to call it.

Could someone share some solution if one exists, please?

they added heavy protection to many lua functions. Complex return address checks are just the beginning.

[65774332]

I m in trouble too

[charles420]

looks like same stuff as ClntObjMgrGetActivePlayer last patch if that helps u any

[sanyle]

Encountered the same situation. Haven't found a solution yet

[sanyle]

Hello,

That seems like Blizz applied some protection on FrameScriptExecuteBuffer in last update 1.13.6.36714 deployed today, now game client crashes on attempt to call it.

Could someone share some solution if one exists, please?

Did you solve this problem?
I suspect it is caused by using SetWindowLongPtr to hook the main thread.
There is no clear answer yet.

[king48488]

Did you solve this problem?
I suspect it is caused by using SetWindowLongPtr to hook the main thread.
There is no clear answer yet.

It's not caused by that

[sanyle]

It's not caused by that

I directly inject the DLL using the following code:

 uintptr_t FrameScriptExecuteAddr = 0x3B1090; 
    static auto const luaDoString = reinterpret_cast<uintptr_t(__fastcall*)(const char*, const char*, int64_t)>((uintptr_t)GetModuleHandle(NULL) + FrameScriptExecuteAddr);
    luaDoString("print(1)", "test", 0);

Not hooked to the main thread.The game can output numbers normally.
But after hooking with WndProc, execute the above code. The game crashes.
I haven't figured out the specific principle, it was just my guess before.
Do you have any suggestions to help me?