![]() ![]() #3 The coords of the screen run from 0 to N-1, where N is the width or height. You will end up with less code if you do this. #2 goto is bad - you should rework your code to use for-loops. The << verions says output x, then output ",", etc.) (C++ does not know how to add integers and strings, or even how to add two C-style strings. You should use the newer function instead. #0 mouse_event has been superseded by SendInput. If you don't actually have to move the console cursor, you could move the mouse instead - mouse_event with MOUSEEVENTF_MOVE (this might be necessary whether or not you move the console cursor.) I've never had the never to do this, nor have I come across a neat way to do it. Press the repeated tap key once and empty your magazine easily: You. ![]() You don’t need to click the shoot button over and over just to keep firing. That’s it: Your character will keep running until you hit the same key again no need to hold it. So you need to convert the GDI coordinates into the correct row and column for the console. With the repeated tap tool, we can assign a key to the run feature and press it once. (Are you sure you have RGB(95, 103, 65) on your screen? You could screen cap to Paint, or some other bitmap editor, and check the RGB value is what you expect.)īut the coordinates used by the GDI and the Console APIs are not the same: GDI's GetPixel is working with (well) pixels the Console SetConsoleCursorPosition call uses character rows and columns. The find code works for me (I looked for black, RGB(0, 0, 0), rather than RGB(95, 103, 65).) ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |