uhm, PostMessage gets blocked because you are doing a virtual Key Press (you have no possiblity to do an actual key press with any user32.dll function, they all set the isVirtualKey flag)
PostMessage sends a message to TranslateMessageW and TranslateMessageW processes and forwards (only when it's not a virtual key press) the parameters( e.g. click coordinates ) to another function outside of user32.dll. That's the function that you need to call in autoit.
to be more specifi: outside user32.dll = game.dll
You now need to place a conditional BP on TranslateMessageW with the condition to break on WM_LBUTTONDOWN or whatever key you need and then trace trough the calls and find something useful.
PostMessage sends a message to TranslateMessageW and TranslateMessageW processes and forwards (only when it's not a virtual key press) the parameters( e.g. click coordinates ) to another function outside of user32.dll. That's the function that you need to call in autoit.
to be more specifi: outside user32.dll = game.dll
You now need to place a conditional BP on TranslateMessageW with the condition to break on WM_LBUTTONDOWN or whatever key you need and then trace trough the calls and find something useful.