I am attempting to create a war3 name jogger, I have the hashed connection complete, I just need to know if its even possible and if it is, how would I deal with the timers and other stuff that is needed for a name jogger. I need some help. -_- VB6
What exactly is a name jogger?
Logs onto accounts so that they won't expire from inactivity.
Yes it's possible. I wrote something like that a couple years ago for Warcraft III and legacy accounts.
I think the server is more strict about how often it'll let you log on / create an account now though.
He could also add proxy support to his application. Someone created a program called Name jogger, I've never used it buy I'm guessing it has proxy support.
If your not going to add proxy support, you should add more than one connection at once, so you can get through the list faster with less delay. Ie. have four connections on one exe going through one list, if you do it right you can make your delays much shorter.
I am having trouble with the timers, I have never used them in this way before. But I will continue to work on this.
You only said you don't know "how to deal with timers," and you're "having trouble with timers."
I for one have no idea what you're talking about. Be more specific about your problem and someone will try to help.
I dont think he knows how to use timers to make them take the name, then log it and after X time unload it and change name.
Quote from: spear on April 13, 2005, 05:41 PM
If your not going to add proxy support, you should add more than one connection at once, so you can get through the list faster with less delay. Ie. have four connections on one exe going through one list, if you do it right you can make your delays much shorter.
This is an intresting idea. If you do this would it influence it differently if you had one connection. If you load 4 bots and disconnect and delay how would bnet deal with that as opposed to one bot? Would you need an extra amount of delay time opposed to a single connection?
Quote from: spear on April 13, 2005, 05:41 PM
If your not going to add proxy support, you should add more than one connection at once, so you can get through the list faster with less delay. Ie. have four connections on one exe going through one list, if you do it right you can make your delays much shorter.
That might not be such a good idea. Even though it would be getting done about 4 accounts per delay, it would also need to have a longer delay. The more accounts you log on at the same time the better your chance of getting ip banned is. Even thought you probably wouldn't, if your delays were set right, users who are inexperienced with bots would think that it is taking longer, this is why I think it would be better to use 1 winsock control and just log on 1 account per delay.
Quote from: Yegg on April 14, 2005, 02:37 PM
Quote from: spear on April 13, 2005, 05:41 PM
If your not going to add proxy support, you should add more than one connection at once, so you can get through the list faster with less delay. Ie. have four connections on one exe going through one list, if you do it right you can make your delays much shorter.
That might not be such a good idea. Even though it would be getting done about 4 accounts per delay, it would also need to have a longer delay. The more accounts you log on at the same time the better your chance of getting ip banned is. Even thought you probably wouldn't, if your delays were set right, users who are inexperienced with bots would think that it is taking longer, this is why I think it would be better to use 1 winsock control and just log on 1 account per delay.
That's what I assumed what would happen.
Quote from: HeRo on April 12, 2005, 10:16 PM
I am attempting to create a war3 name jogger, I have the hashed connection complete, I just need to know if its even possible and if it is, how would I deal with the timers and other stuff that is needed for a name jogger. I need some help. -_- VB6
Ok, i hate to sound mean but is it just me but if he accutaly made the war3 hashed connection scripts, wouldn't he have no problem setting up a few timers?
Quote from: -MichaeL- on April 14, 2005, 05:37 PM
Quote from: HeRo on April 12, 2005, 10:16 PM
I am attempting to create a war3 name jogger, I have the hashed connection complete, I just need to know if its even possible and if it is, how would I deal with the timers and other stuff that is needed for a name jogger. I need some help. -_- VB6
Ok, i hate to sound mean but is it just me but if he accutaly made the war3 hashed connection scripts, wouldn't he have no problem setting up a few timers?
I was thinking that, but w/e maybe we are wrong :]
He may be doing something a bit more complicated with timers. Maybe he understands it but he hasn't a clue how it should be put together to create the best posible code.
Ah, I assumed that this was a single-name client at first. I suggest having four timers, or perhaps an array of timers (adding more as user specifies), each with a designated proxy for it. Every 10 minutes, which should be plenty of a delay, connect the four bots and "jog" the account.
If you're refering to having a long delay on timers, I suggest doing something like this.
Public iTimerCount1 as Long, iTimerCount2 as Long 'etc for other timers..
Public Sub Timer1_Timer()
Select Case iTimerCount1
Case 10 'asuming its set to 60,000 MS. Set it to whatver you feel nessassary.
'Do connection crap here.
Case Else
iTimerCount1 = iTimerCount1 + 1
End Select
End Sub
Unless you modify those timer variables elsewhere in your code, they're probably better off declared as Static variables inside the _Timer() procedure.
Variables declared inside the subroutine are distroyed upon completion, aren't they? Asuming they are, we wouldn't be able to incrememt them and check them against 10.
Quote from: Joex86] link=topic=11252.msg108646#msg108646 date=1113537716]
Variables declared inside the subroutine are distroyed upon completion, aren't they? Asuming they are, we wouldn't be able to incrememt them and check them against 10.
Not if they're marked with the "Static" modifier, which is what Stealth suggested.
I don't understand what the problem is. Your accounts won't expire for several months. So unless you're dealing with hundreds of accounts (you freaking LOSER -- get a life!), you won't need to log onto each but maybe once per day. With that in mind, you could keep each logged on for a few hours, too.
So add that all up. What's the big deal about getting IP banned for sending too many logons and connecting too fast? Last time I checked, they don't do that unless you're trying to connect really fast. Since when is connecting once or twice per day "really fast"?
If you log on too many within a certain time range you can get ip banned. The faster this is done, the faster you will get ip banned. For people who save 100s of accounts, proxy support would get the job done very quickly.
I thought you just started to get "ignored" by Battle.net, not IPed.
Quote from: tA-Kane on April 15, 2005, 09:59 AM
..unless you're dealing with hundreds of accounts..
Which is where they stand.