Jump to content
AC Tool Forums

The WABBIT

Moderators
  • Content Count

    629
  • Joined

  • Last visited

2 Followers

About The WABBIT

  • Rank
    Forum Master
  • Birthday 02/03/1966

Profile Information

  • Gender
    Not Telling
  • Location
    Denver, Colorado

Contact Methods

  • Yahoo
    The_WABBIT1@yahoo.com

Recent Profile Visitors

16,249 profile views
  1. Yes you can do this. But it is not done by a single command. This requires that you use 3 commands, two of which are for the button. I would suggest that you read the Help file. And then try to create a test script. And then post here if you are having problems getting it to work.
  2. Well, I do seem to remember stating in my previous post. That I recommend that you read up on Procedure .. End and ProcessMessages. I guess that you had not could that. It is good that you did eventually read up on it, after ego had given you a snipped of code, and had gotten you script to work properly.
  3. If this is for a AC Tool script, then I would suggest that you read the AC Tool Help file since you have not done that yet. I would recommend that you read up on Procedure .. End and ProcessMessages.
  4. Well, the problem was with the Sessions table of the DB. It had about 712 entries and all of them had some form of corruption. The Sessions table handles keeping track of individual member login sessions. So, there was not real data loss. Prior to my trying to access the forums. There was one member, according the the logs that was able to access the forums. That person had done so about 4+hrs prior to my attempt. And then there was Ego, sometime prior to even that person.
  5. Sorry, that I had not checked in for over a 9 days. As I attempt to check on the Forums at 7:25 AM [UTC-6]. I find that the Forums was down, do to some script error. Is what I kept getting when I attempted to look at any page. Logging into the Admin Control page, showed that there was an error with on specific maintenance script. This lead me to see if changing it from being run one way to another would fix the problem. Of course it did not, but it did allow a more meaningful error message to show up on the Forums main page that I was trying to view. Some how, earlier today, one of the Forums' DB Tables had crashed. So, I fired up the old trusty phpMyAdmin, provided by the Site Host, backed-up the DB. Then repaired the DB Table in question. As soon as I finish this post and it looks like everything should be fine. I'll do another backup of the Forums' DB.
  6. Although was very polite with you. And I never did "dismiss" your report as you have claimed multiple of times. Even though you had made the claim that AC Tool, by using the KeyDown, was freezing your whole computer. With no additional information for me, or anyone else, to use to test and diagnose the problem. But, in reality it was Notepad that was actually having a problem. And I had completely explained that to in great detail. Along with what is necessary to minimize the problem, if not get rid of it completely. Even with my response to your second post about this issue. Again, with no information for me or anyone else to try to test and find out what is causing your problem. I still responded with information to try to help you. Obviously, you did not like that. Because you had started with accusing me of completely dismissing your report. And making statements that had nothing to do with your problem. And still claiming that you wanted help fix the problem. Yet you still refuse to help by giving me any information that I, or others, need to help test for any problems that there might be between AC Tool and what you have on your system. And yet despite all that, I continued to read through the source code with a fine tooth comb. Search for possible causes as to why individual programs my become unresponsive in Windows 10. And with what was shown in your second video. I even went and downloaded the emulator and the roms needed for the specific game shown in the video. Just so that I can do testing to actually see what is going on there. During that time, Ego attempted to help you. But even with him, you were borderline belligerent in your responses about his attempts to help you. Then when I responded to one of your posts last night. Not only was your reply to my post completely belligerent. But, you continued the claim that I was completely dismissing your report. Resorting to name calling, using degrading comments, and out right stating that anyone, including myself, was stupid and ignorant. What did you say? You even claim that if you ever go and create your own program that you will a best developer there is. Well, if you believe that is fine. And until you get out there and prove those claims by actually creating a program. Now, that this thread has run it's course of myself, and @Ego, trying to help you. And you not giving any information needed to find the actual cause of the problem. And yet still claiming that we are dismissing your report. This thread will be locked. But, will make it clear to you here in the open. Any future posts that you make here in the forums. Will only be for the expressed purpose of getting help with any macro/script that you are writing. Said new threads started by you will placed in the proper sub-forum for the script being made. And you will follow the rules of the sub-forums when you make that new thread. All information listed in those rules will be included in your request for help. You will find the rule for each sub-forum pinned to the top of each sub-forum. Any posts that you make that is not a request for help with the creation of a macro/script will be deleted. Any posts that you make is missing any of information, as outlined in the rules for the sub-forums, will be deleted. Finally, any post that you make that is belligerent, uses name calling, or degrading in any way will be deleted. And you will be given a warning. Once you have receive two warnings, there will not be a third. Your account will be locked and you will be banned.
  7. Okay, I am going to respond to your three posts in. But, I will not be able to do respond to all of them in just one post. So, please hold off on responding to my posts until I have finished responding to all of yours. That is where you are wrong. In order for any developer to test and diagnose a potential problem/bug with their program. They have to have all of the information they can get. This includes, but is not limited to: The version of the developer(s) program that is being used. The Operating System, including the Edition of that Operating System (if there is different editions). The Operating System's version. (This is not the number that may be apart of the Operating System's name.) What other programs are running. What programs, and services, are running in the background. Detailed instructions on how to reproduce the problem/bug. And in the case of programs like AC Tool. Then the developer needs the following information in addition to the above: The name of the game or program that the macro/script is for. If necessary: The name of any programs, and specific version of, that are being used to run the game or program. Game only: What keyboard setting needs to be made in the game, in order for the macro/script to work. Game only: If the game can be modded. Then the name of all the mods being used, along with links to where to get the specific mods. The FULL and COMPLETE macro/script that is being used. Even if that macro/script is still being created. Game only: The location within the game that the macro/script is used. Detailed description of what the macro/script is supposed to do. But, if the problem the user is having. Is getting their script to work the way they want with the game. Then the developer(s) typically only needs the following: The version of the developer(s) program that is being used. The Operating System, including the Edition of that Operating System (if there is different editions). The name of the game or program that the macro/script is for. If necessary: The name of any programs, and specific version of, that are being used to run the game or program. Game only: What keyboard setting needs to be made in the game, in order for the macro/script to work. Game only: If the game can be modded. Then the name of all the mods being used, along with links to where to get the specific mods. The FULL and COMPLETE macro/script that is being used. Even if that macro/script is still being created. Game only: The location within the game that the macro/script is used. Detailed description of what the macro/script is supposed to do. Detailed information of what the macro/script is actually doing. With information as to where in the macro/script the problem is. Now if the user does their own testing. And that test is done on multiple of other systems. Then the developer(s) need the same information for each system that the user did the testing on. And yes, it does matter that the developer(s) have this information. Because the developer(s) need this information to test and attempt to reproduce the problem. And hopefully diagnose what the actual problem is. Whether it is a problem with the program or some other program. For AC Tool, since the information is posted in the public forums. It the information is there for others to use to perform their own tests. To verify that they are, or are not, having the same problem. Believe me, Echo loves helping out in that regards. And he's not shy in telling me if he having a problem AC Tool. And he also let's me know whether or not he is having the same problem as that user may have reported. And he does so here in the forums. And all I got from you was a post with its title stating "Keydown causes my PC to freeze", two lines of code, a stated that you tried it on two computers, and a vid showing you using the code with Notepad. And that Notepad was becoming unresponsive. It can be, it just depends on what you are trying to do with the macro/script. What!? Why'd you mention this? No, I did not need to know. And I did not ask you about this. So, there was no need for you to state that I had to know this. As if I had pressured you to tell me. I am glad that you have attempted to use AC Tool for your gaming projects since Windows XP. I had started using AC Tool back with Windows 2000. Making macros/scripts for Earth & Beyond. I even did one of the very first macros for Maple Story. (It was very small and very simple. All it did move the character forward a fraction of a second, attack for a few seconds, then repeat. With every so many times of moving forward, it would pickup any drops items.) But, there isn't a day that I do not learn something new about AC Tool or how to use it with any particular game. Again, what game or program is not besides the point. And the KeyDown function is working properly. You originally stated that KeyDown is causing your PC to FREEZE. Your own video does not show that your PC was FROZEN. But instead, the program was that Notepad became Unresponsive for a about 8 seconds. The whole time you were moving your mouse around the desktop. Even when Notepad was unresponsive. And the letter 'p' appeared in Notepad right after it was no longer unresponsive. And the fact that you were able to go and create a vid show in its entirety the problem you are experiencing. Just shows that your PC did not Freeze. First, I did not dismiss your post about AC Tool causing your PC to Freeze. In fact, I read the three lines of text, that gave pretty much no information. I watch your vid 30 times to make sure of what I was seeing in the vid. I replied to your post. Told you what the problem actually was. I even explained it detail so that you would hopefully understand. (Just like I always do for those people that I have never seen make a post before. Or those that seem to not seem to have some form of programming knowledge. I have literally written books in a single post when responding to others.) And then based on my own tests, I had even giving you how you can possibly fix the problem. Then in you next post you state the following: Heck, I didn't know which version of AC Tool that you were using. It wasn't until your fourth post, in response to Ego, that you even mentioned. You stated that you had tried KeyRate and that you didn't get the results that you wanted. But, you didn't tell me how you used it. Or even showed any code with it being used. You even tell me that it didn't matter because you had come up with a work around. with the code for that work around and a vid showing the is supposed to be a macro causing your PC to freeze, which did not take place. As well as, showing the work around code doing something. Besides the fact that your PC did not freeze, which what you have stated KeyDown is causing. The vid that you have posted, for which I have now watch 23 times, shows that the KeyDown function is working. Not only do you see Naruto's hand move as he bounced the basketball once. (BTW, what happened to the basketball? I didn't see it.) And you can hear the basketball being bounced the one time. Then the game became unresponsive. And now my response to you statement about someone else reporting this problem. The post that you linked to, shows that the person stated that keydown {RIGHT} <-----lags my computer. You even misquoted them on it with your response to Ego. I have two things to say about it. The line they had shown had shown that they had used the command wrong. And I even mentioned that fact. They did not specifically state what they meant by "lags my computer." All attempt to get more information from the person in order to help them. Was met with zero information being given. This person reported that it was lagging their computer. That is not the same as what you have reported. You have report that it is causing your PC to Freeze. Even if I took their statement to mean that it is causing their computer to be slow, or be slower. That is still not the same as what you have reported. For which, since I knew that AC Tool, because of the use of KeyDown, was not causing your PC the Freeze. I focused on the fact that Notepad was becoming unresponsive. I went through and looked at the code for the KeyDown function. And I further looked at the rest of the code for all of the functions for sending keys to a program/game. And what I had found was that the actual code that sends the key presses to the game/program, had not changed. It is the same code used from when I was using it Windows 2000. I know that it worked fine in Windows 2000, Windows XP, Windows 7. (Hell, you even stated that it worked many years ago. Meaning that you did not have problems with the KeyDown until Windows 10.) And when I did have a system with Windows 10 (versions 19H01 and 20H01). I had no problems with running any macro/script that I had created, that used KeyDown, for the specific games that I play. Even though I do not have a system with Windows 10 on it. I borrow one from a close friend of mine for testing purposes. I do this when I need to test for problems/bugs. I then spent a couple of hours searching for reasons why programs were becoming unresponsive in Windows 10. But, since I had zero information that could help me to diagnose the major problem, or as you are so strongly suggesting is a Major Bug in AC Tool. I then responded to your post with tips as to how to hopefully solve the problem. Because everything that I have found. Shows that the main causes of programs becoming "Unresponsive" are: Drivers (for a lot of people it was drivers for Logitech wireless keyboards and mice.) programs, or services, running in the background Other programs, besides the above, that are running at the same time. Once in a while it was a hardware problem. (But, since you tested on multiple system. I pretty much ruled that one out.) The last two because the background programs and services and other programs running at the same. Can either interfere with other programs working properly. Or there might be a compatibility issue with said program or service. I had hoped that you would perform what I had suggested. And if you still had the problem, then I would have suggested two more ways to hopefully find out would was is possibly causing this. But, instead. Your response was to write this diatribe about how I am dismissing your report. Just, so that you are fully aware. Since my last post, I have been going over AC Tool's code for KeyDown, searching the Internet for possible causes for programs being unresponsive and possible ways to fix it. I even been looking into other possible ways of possible redoing that whole bit of code for sending keys to other programs/games. And yet, you state that I have been dismissive about this!
  8. First off, you state that the original code worked "many years" ago. But you do not state what year that was. Nor do you say what game, or program, you were using it for. And you did not state what version of Windows you were using at that time. So, I can only assume that the problem might be because of Windows 10. I can not really say. But, then after watching your vid. I see that you are playing what looks like NBA Jam. And since there is no version of NBA Jam for the PC. That means you are running it through an emulator. But, I have no idea if this is the game that you played many years ago when the code worked fine for you. With that in mind the problem could be because of the emulator or Windows 10 or both. The only advise I can give you on this is the following. If your problem is with this specific game. And you played it "many years" ago. Then what you need to do is use the exact same emulator that you had used "many year" ago. That also means the exact same version of the emulator from "many year" ago. If the problem goes away, then you know it is the current emulator, or version of the emulator, that you are using. But, if the problem does not go away, then you know it is a Windows 10 problem. Or this is not the game that you played "many year" ago. Then what you can do is try the following: Make sure that you are using the latest drives. DO NOT USE THE BUILD IN WINDOWS 10 GENERIC DRIVERS. But, get the drivers from the Manufacture of the devise installed in your PC. Make sure that no other programs or services (except those that are require for your PC to run and to protect it), are not running in the background. If this does not help to fix the issue. Then I would do a Google search for Windows 10 unresponsive program app. You well receive a whole lot of search results for ways to help fixing this problem. Note, AC Tool is a 32-bit (x86) program as such it may work better with 32-bit (x86) versions program certain programs. But, in general there should be no compatibility between Windows 10 and AC Tool. At least no one has ever made the claim that there is one, that I am aware of. So, if there is any compatibility problems. Then the compatibility problem is cause by the game/program/emulator and windows 10.
  9. Okay, after watching your vid of the problem. And I ran some tests on my end to make sure of what the actual problem is. The problem is not with AC Tool and the problem is not with using the KeyDown command in your macro. The problem is with Windows and Notepad, specifically Notepad. Let's do a simple experiment. Open Notepad, then press and hold the 'p' key down for 8 seconds. What you would see is the following: What you end up with is about 374 p's. That's about 46.75 p's per second. That's a lot of p's. Now, if you were to have AC Tool do the same with the KeyDown command for 8 seconds. What would happen is that AC Tool would end up sending the following: HOLY MACRO Batman! What you have here is 8000+ p's. That's 1000+ p's per second being sent to Notepad. Notepad, and many other document editing programs, can not receive 1000's characters per second. You'll be lucky to find one that would be able to keep up with 100 characters per second. The problem with these programs is two fold: They have a buffer that all key presses go into until it is processed by the document. And then deleted from the buffer. If this buffer fills up, then all additional key presses have to wait until enough characters in the buffer is processed, and then removed, to be added to the buffer. The developers of these programs have also added safe guards. To help keep malicious programs from injecting large amounts of characters to the editing programs. This could cause the program to either Crash to Desktop (CTD) or cause the program to freeze or even completely lockup your computer. Because of this, sending large amounts of characters to Notepad will cause it to become Unresponsive. Until it can process all of the characters it is receiving. And it will also cause AC Tool to become Unresponsive until it can finish sending all the characters to Notepad for the 8 seconds it is supposed. Even if it actually takes longer than the 8 seconds to do so. The reason that you only see a single letter p when using AC Tool to send a character to Notepad. And you see a buck of characters if you press and hold down the character key(s). It is because of the safe guards that are added. And it only effects key presses being injected to the program by another program. Now, you should not have this issue when using AC Tool with Games, especially modern games. The reason for this is that the developer(s) have created the game to process keys being press, or injected, as quickly as possible. But, they do have their limits. Either the key is being pressed, or injected, too quickly for the game to register that the key was pressed, or injected. Or the amount of keys being pressed, or injected, is too much for it to process. Causing the game to become unresponsive until it can catch up. Now to solve your problem what you need to do is use the KeyRate command. You will need to look AC Tool Help file to find out how to use it. I would recommend that you use a value of 10. And you need to add the KeyRate command at the very beginning of your macro. But, if during your testing with Notepad you find that you are still having problems with Notepad becoming unresponsive. Then increase the value by 5, until such time as you do not have that problem anymore.
  10. you need to read AC Tool Help file about {GlobalKeys}.
  11. If I remember correctly, you had stated in that post that it was a mini mining macro. There wasn't much mentioned about it. And the rest of the thread dealt a few other people's macro's that were uploaded.
  12. Hey @Ego, when I was on the WayBack Machine I came across a topic about Earth & Beyond macros, because of the emulator being done. And I happen to come across this code that you posted in that thread: SetActiveWindow Earth & Beyond //1400x900 delay 4 sec keys x // in a roid field should target closest roid delay 1 sec loop 1000 // how many times you want to run the macro MousePos 1385, 600 //mining icon delay 1.5 sec // nice and slow to open or change mouse positions leftclick delay 1.5 sec MousePos 1280, 300 //top left window where an item is delay 1.5 sec leftclick delay 1.5 sec MousePos 1250, 750 // moves cursor to target window to close it delay 1.5 sec rightclick MousePos 1385, 600 // back to mining icon position on screen delay 5 sec // time taken to mine and tractor the item to hold keys d // next roid delay 1.5 sec end There was a few other posts in that thread that had some code. But, other than the above all the codes were just snipips to help fix already attached macros. For which you are not able to download. The WayBack Machine didn't make a backup of the attached files.
  13. Ya, you'll just will have to hope that someone, anyone, from back then that is still visiting the forums might happen to have the macro. I just spent some time on the WayBack Machine for the archive of the forums. And it does show that you that you had posted at least 8 macros. The reason I say at least. Is because the WayBack Machine doesn't make any backups of the sub-forum's pages prior to Jun of 2006. And then it only has only the first 3 pages of posts for each sub-forums. And although you are able to see the posts for the 8 macros. You are not able to download the attached files. Have you tried asking on ImmortalBob, or even Reddit, to see if anyone might have it?
  14. Hey Chazcon, good to see ya. I don't have any clue as to your Macro. From what I am seeing, the forums does not have any posts by you prior to October of 2012. And none of those posts do not have a macro in it or added to it. I'm assuming that you posted the macro some time prior to October of 2012. And since I had taken a long break from everything, between December 2006 and October 2012. I don't know what had happened to the forums during that time. Maybe Bear, or any one of the other Moderators, can shed some light on what happened during that time. Any way, I hope that anyone that played Asheron's Call back then, and is still visiting here, may have your macro. And that they will post the macro here.
  15. First of all, are you actually talking about making the program Full Screen? Or are you talking about Maximizing the program's window? There is a difference between the two. Making the program full screen means that the program takes up the whole screen. There is no window Title bar, and no window borders (if any), and windows taskbar is not present. Maximizing the program's window will have the window Title bar, and window borders (if any), and the Windows taskbar will be present (provided you did not set the taskbar to auto-hide). And, depending on what you actually want to do with the program. There is a couple of problems: The WinKey + Up Arrow will Maximize the currently active window. It does not make the program Full Screen. The Ctrl+Esc is a good alternative to just pressing the WinKey. But, it will not work with any of the WinKey+key shortcuts. All it does is bring up the Start Menu. So, if you actually want to make the program Full Screen. Then what you actually need to do is use the Alt+Return (or Enter) shortcut. This will cause the program to become Full Screen provided that the program was created to be Full Screen. Or if you actually want to maximize the program's window. Then there is actually two ways of doing this. Use the Alt+Space shortcut to bring up the window's sub-menu and then press x to maximize the window. (Alt+Space+x) Some programs/games may interfere with the Alt+Space shortcut. Use the program's taskbar icon to maximize the window. You do this by first hovering over the program's taskbar icon. Wait for the preview of the program's window to popup. Move the mouse to hover over the program's window preview. Right click on the preview. And then select Maximize There you go an answer to your problem.
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use and to our Privacy Policy.