Yea, it depends on the speed of your computer. I can use as example 2sec. delay and it works. 1sec delays never work. Tried it with my premium char. If you stay on enter or if you press it to fast, then it will be bugged and you see no characters. 2sec+, just try the value which is good for you.Quote:
hey i got it to work
the problem with me that i cant see my charac when i gets in its due to the delay of autopress change it to 4 and it will work =)
Think about it again. Then you will figure out that this will not work pretty accurate. If I do it how you want it, then will this happen: On the first loop, the keypresser will start to press all keys for all the buffs at the same time and only one of them will be casted. On the second time it will run how it should. After 600 seconds the first buff will be casted and after 610 seconds the second one. Then after 900 seconds the first one and after 915 seconds the second one and so on. What you think how good this is if you got like 4 buffs. With 300,305,310,315 loops. After the third loop the last buff is already 45 seconds from the first buff away and not just 15. This is just rly unaccurate. What i can do of course is to make for every single button that have to be pressed a own Auto Key file wich all have the same delay of 300sec. Then i start them all manually on to the same client. And every time if i want to stop or start it, i got to stop or start like 4-5 Auto Keys. So, a field to set a delay before starting the auto key loop of as example 300 or whatever you need would be really nice. So the first key starts after 0s and loop all 300s and activate the first buff, the second key starts after 5s and loops also all 300s. The delay betwen both buffs will be always 5s. Not less, not more and everything run fine. And with this, you can do a lot more things. Like switching weapon, buff, switch back to main weapon and use another 2-3 buffs. However you want it. And it will be always acurrate with the same delay between all buffs. Do you get it now that this delay before start of the single key is needed if you want to use more then one key. You also never press all keys on the same time on your keyboard to write, do you?Quote:
@fuuu222: I don't quite understand the idea about Delay before start. What is it for? If you want to make a buffer, you only need to make sure you stopped your bot and start buffing. Let's say your buffs is 300s cooldown, but the animation require 4s to cast, so simply set it to 305s.
Key: 1 Delay before start: 0 Loop Delay: 300
Key: 2 Delay before start: 5 Loop Delay: 300
is equivalent to:
Key: 1 Loop Delay: 305
Key: 2 Loop Delay: 300+smt
Oh, im sry i think i didnt realized that the delay means that he waits that delay before he press the second key. I thought it would press all keys at the same time and just use the delay as loop. Well, this means that i can use it how i want to. I'm really sry.Quote:
As for the buffs, I understand a bit. If you have buff with very different cooldown, it's hard to config. But still i dont understand what the delay before start is for.
My script works like this:
begin:
send 1st key
wait xx second
send 2nd key
wait yy second
...
goto begin
To write a perfect buffer, every second you need to check if any cooldown finished to send the key again. One buff needs one timer to count, so i'm not sure if it consumes lots of cpu. And to make sure you are in the right tab, you always need to send {F1} or {F2} before sending the buff key.
A buffer and a key presser are two different things. One sends keys with a predefined order, other sends keys in random order based on the cooldown
If you have any idea of other algorithm to code it. Feel free to tell me :)
As first, dont double post. As second, you have to rename every SRO_Client to something else, like 1, 2, 3, 4, 5, 6, 7, 8 and so on. The dev said he fixed that problem that you dont have to rename the SRO_Clients, but there is no new update available, it's still V3.0. So go with this solution. If you dont rename them, then all auto key processes will press enter on the last selected(focused) SRO_Client. Btw. there is some little bug which will happen if you have running like 8+ auto key processes. You have sometimes the problem to double click in windows to start programs as example. You have to double click very fast. I got no idea why. Just saying. And its no big deal, since you never need doubleclick. You usually can just right click and choose to open out of the menu or whatever you want.Quote:
When I press autokey,it starts with pressing enter,but When I put on some other program,like Firefox,I have feeling that program doesnt click enter every time.
When SRO client is on top,There is always message :"The server is full" or "Requesting user information".
But If I was working on firefox for some time,and I instantly change to sroclient,there is no any message.That means that presser didnot press any key for a long time.
And I am not logged in for 3 hours with 8 SRO clients.
Thanks on answer. But do you recomend me to use max 5 clients in one time? Will that bug happen if I open max 5 clients?Quote:
greetz, John
You can open 16 clients if your pc can handle it. There is no problem. Only rename them. As i said, that double click thingy is rly no big deal. Just told ya so that you know about it and dont wonder later why you cant open programs on double click. As i said, just right click and open. However, you dont notice that bug by 10 clients usually. If you use like 16 or more, then you notice it for sure. ^^Quote:
Well I dont think that using 4 GB of ram (like me) you can open 16 SRO clients,I can open 8,with no extra lag,but I think that 10th client would make lagg.Quote:
Atm, do like fuuu222 tells. Or if i'm not wrong, client in isro has a protection that it only allows you to send key if the client is focus. To resolve this problem, you need to minimize the client by pressing Ctrl+F1. After it is minimized you can do anything you want even hidden; script will not send keys if it's hidden only. I always do test with ecsro client so i prevent much bug.
As for the double click thingy. Running too much key presser will eventually flood the input stream. It's like you hold a key and try to click a button and it won't work as you wish. Too much client will consume much CPU too.
I never minimize mine, i always keep them on top to look at them after a while and if they were minimized it takes to long to open them all again in a row. I can load up to 12-16 clients and run while that games like Warrock or Race Driver Grid or CoD4. At least smooth running software which is programmed well. I cant run as example Americas Army 3 while that. So bad programmed shit is that and still got no really good grahpics. However, if i dont play games i often use like 16-20 clients to login for more characters at once. I got 6gb ram, and XP 64bit and a normal CPU with 2x 2,8 Ghz cores. I use usually only 12 clients per character that i want to login. More than 12 with a press delay of 2sec is not usefull for logging in. Means 6 login tries a second. Some ppl cant use a 2sec delay or 3. But a 4 second delay works kinda for everyone without that bug that you see no characters after successfull login.Quote:
But from now on,I will just rename clients,and I hope that it will work fine,and if it doesnt,I will minimize everything using CTRL+F1.