Use C # to create a "QQ battle platform room dashboard"

1. What is "QQ vs. platform room dashboard "?

Anyone who likes to play games on "QQ vs. platform" or "haofang vs. platform" knows. Generally, most of the rooms on the platform are full. If you want to find a room, it takes a long time to "squeeze" the room. If it is a holiday or evening, it will take more time to "squeeze" the room, such:

For "QQ combat platform", if the room is full, but abnormal, two prompts will pop up! In normal times, you just press the "Enter key" or "Space key" to close these two annoying pop-up windows, and then click the room with the mouse. if the room is still inaccessible, we can only repeat the previous cycle ...... One or two times are not a problem. Five or ten times may not be a problem. But if you cannot squeeze in more than a dozen or even hundreds of times, you can press it! Of course, if you like hand abuse, you can also say -_-#

I don't like hand abuse, so when I encounter N times or cannot squeeze in, I wonder why I don't write a tool to replace my hand, I used a tool to "squeeze" my room automatically. Could you help me with the two annoying Prompt Windows? As a result, the "QQ battle platform room dashboard" in this article was born like this (How many hands can be liberated, everyone applauded ......)

2. How to squeeze a room "?

As mentioned above, the "squeeze room" means to help us automatically "squeeze" the room, but how does it help us "squeeze? After all, it is a machine, not a human. It will not automatically "squeeze" us as soon as we see the room, unless we have customized a set of rules (or commands) for it ). A machine is a machine. If there is a rule, it will do things. If there is no rule, it will do things. Then it is a "person" (Intelligent Robot ?) .

How should we customize this rule? Let's first take a look at our usual process of entering the room, such:

Well, according to the above process, we will customize the following rules for the "dashboard:

1) Click the room.

2) Determine whether the room is in. If the room is not in, close the two annoying Prompt Windows that show the room is full and return to step 2.

3) If you have entered the room, stop the "squeeze" operation.

3. implement automatic room squeeze.

The implementation here is to use the code to implement the three rules customized above.

1. Click the room:

Here we are simple, justSimulate the mouse and click the current room. Speaking of this, maybe a friend who has developed a WINDOWS application has figured out which API functions to use to simulate, right! The following APIs can be used together to simulate mouse clicks.

1) GetCursorPos: obtains the current location of the mouse.

The prototype is as follows:

[DllImport ("user32.dll")]
Internal static extern bool GetCursorPos (out Point lpPoint );

This function returns the coordinates of the current mouse.

2) mouse_event: simulation of mouse events

The prototype is as follows:

[DllImport ("user32.dll", EntryPoint = "mouse_event")]
Public static extern void mouse_event (
Int dwFlags,
Int dx,
Int dy,
Int dwData,
Int dwExtraInfo
);

This function is defined using different dwFlags parameters to simulate different mouse events, such as pressing the left mouse button or popping up events.

Combined with the above two API functions, we can achieve the effect of automatically clicking the room where the mouse is located ", similar to the following code:

Point point;

If (Win32API. GetCursorPos (out point )){

// MouseAPI is a simple encapsulation of the mouse_event API function.

MouseAPI. SendMouseEvent (MouseAPI. MouseEvents. LeftButtonDown | MouseAPI. MouseEvents. LeftButtonUp, point, true );

}

But the above code is very "mechanical", that is, no matter whether the current mouse is in the room or not, it will automatically "click" once! This is not user-friendly, so let's make another improvement. When we click it, we will first judge whether the current mouse stays in the room of the combat platform, but unfortunately the room of the QQ combat platform is not a standard WINDOWS Control, therefore, the room data cannot be obtained. In the end, we have to simply judge whether the window with the mouse is the Hall of the QQ combat platform, because the hall is a WINDOWS window control that can be obtained, the hall data obtained using Spy ++ is as follows:

That is to say, we can determine whether the type of the window where the mouse stays belongs to "Afx: 400000: 3". If so, it indicates that the mouse stays in the game hall of the QQ game platform, you can click the room (note: the location of the stay here is not necessarily on the room, but this does not affect usage, so I did not handle it)

The following APIs are required:

3) WindowFromPoint: obtains the window where a coordinate position is located.

The prototype is as follows:

[DllImport ("user32.dll")]
Internal static extern IntPtr WindowFromPoint (Point );

4) GetClassName: Get the type name of a window

The definition is as follows:

[DllImport ("user32.dll", CharSet = CharSet. Unicode, SetLastError = true)]
Internal static extern int GetClassName (IntPtr hWnd, StringBuilder buf, int nMaxCount );

After adding the above condition judgment, the code above is improved as follows:

if (Win32API.GetCursorPos(out point)){    hwnd = Win32API.WindowFromPoint(point);    if (hwnd != IntPtr.Zero)    {        string className = Win32API.GetWindowClassName(hwnd);        if (className.Equals("Afx:400000:3"))        {            MouseAPI.SendMouseEvent(MouseAPI.MouseEvents.LeftButtonDown | MouseAPI.MouseEvents.LeftButtonUp, point, true);        }    }}

In this way, the "click the room" step is perfect. When the mouse is not in the room (not in the game lobby), the mouse will not be messy, this makes it easy to switch the window at any time when the room is crowded.

2. Check whether you have entered the room. If you have not entered the room, close the two annoying Prompt Windows that show the room full.

 1) Determine whether the room is in: The same as the previous step to determine whether the mouse stays in the game hall, it also determines whether the mouse stays in the chat room. If so, it indicates that it has been squeezed in. Use Spy ++ to obtain the chat room window types: "RichEdit20A" and "Afx: 44a0000: 0". The judgment code is as follows:

// Determine whether the mouse stays in the chat window if (Win32API. GetCursorPos (out point) {hwnd = Win32API. WindowFromPoint (point); if (hwnd! = IntPtr. zero) {string className = Win32API. getWindowClassName (hwnd); if (className. equals ("RichEdit20A") | className. equals ("Afx: 44a0000: 0") {isOk = true ;}}}

If isOk = true, it indicates that it has been squeezed into the room. Then you can stop the "crowded room", otherwise you have to deal with the two annoying Prompt Windows.

2) Close the prompt window:

First, you need to determine whether these two prompt windows appear, because during the room squeeze process, the QQ combat platform will display a progress bar (window) first ). To simplify the processing, we only need to determine whether the current activity window is a "Prompt window", that is, to simply determine whether the "OK" button is included in the current activity window. If yes, simply think that this window is the prompt window and close it. The following APIs are used:

A. GetForegroundWindow: Get the current activity window

Its definition prototype:

[DllImport ("user32.dll", CharSet = CharSet. Auto, ExactSpelling = true)]
Public static extern IntPtr GetForegroundWindow ();

B. finddomainwex: Find a window.

Its definition prototype:

[DllImport ("user32.dll", EntryPoint = "findjavaswex", SetLastError = true, CharSet = CharSet. Unicode)]
Internal static extern IntPtr find1_wex (IntPtr hwndParent, IntPtr hwndChildAfter, string lpszClass, string lpszWindow );

Close the prompt window. You only need to use the simple method, that is, to send the "Enter key", because the window we get is the current active window and the mode window, therefore, it can accept keyboard messages. For more information about keyboard simulation, see my article C # programming and developing game controllers-API (3).

The final code is as follows:

If (! IsOk) {// if it is not pushed in, check whether a prompt window pops up. if yes, close it hwnd = Win32API. GetForegroundWindow (); if (hwnd! = IntPtr. zero) {// check whether the activity window contains the "OK" button IntPtr buttonHwnd = Win32API. find1_wex (hwnd, IntPtr. zero, "Button", null); if (buttonHwnd! = IntPtr. Zero) {KeyboardAPI. SendKeyEvent (Keys. Enter, KeyboardAPI. KeyboardEvents. KeyDown | KeyboardAPI. KeyboardEvents. KeyUp );}}}

IsOk is the value used to determine whether there is a "squeeze" in. If there is no "squeeze" in, perform the "Close Prompt window" operation above. If the "squeeze in" operation is completed, stop it.

At this point, all the above Code is integrated and added to the Timer execution of Timer. Our "QQ vs. platform room dump" is implemented.

 

Download the following Program (source code is not provided, but you can decompile it to view it ):

/Files/kingthy/QQBattleThruster.rar