• Welcome to Valhalla Legends Archive.
 

CHAT Logon Sequence

Started by Smarter, March 22, 2007, 09:40 AM

Previous topic - Next topic

brew

Quote from: Smarter on March 23, 2007, 02:50 PM
There two sepearte programs, and the 2nd one needs to be VERY fast, as if you don't know what Recon servers are, i'll explain. Recon Wars, are a battle.net based server, that people connect to on any client (mostly Chat as of it's easy for connection), and every X amount of hours, the server drops all connections, and then allows (pretty much ends the bnetD and then reopens it), so at any time theres 100-3000 people all connecting at the same time,  and the idea is to catch the connection first, to get ops in the channel, as first person in the channel gets ops. So, people set a delay time in MS and the bot will reconnect, well many people have come up with methods to improve their chance of connecting, but like, settings 8 sockets and having each of those connect @ the designated delay, i'd like to improve that archaic way by making the program in C# ( as .NET Sockets are known to be faster ;))

Are you sure? I always thought a winsock class would be faster then a winsock object (wouldn't it? or are objects a type of class.. i don't know oop well) and C-anything is faster in general... so...
And if you're going for something like that why not have a connection attempt every 40 or so ms, since there are no ipbans. And whoever said you're limited to 8 connections? Use proxies. If you happen to have 100-3000 people connecting at the same time, and let's say they connect RIGHT at the absolute second it gets back up, it would still be better to attempt some 10 connections per second then having 8 bots occasionally attempt a connection. anything to better your chances of connecting first, i guess, and there would be no better way of increasing your chances by increasing the number of connection attempts. So if you do get a proxied connection connected at that exact time, you can probably designate the non-proxied connections and switch ops to that one later on or w/e. Btw i hope the assbot source helped you (it connected without any problems to bnet a few years ago)
<3 Zorm
Quote[01:08:05 AM] <@Zorm> haha, me get pussy? don't kid yourself quik
Scio te esse, sed quid sumne? :P

Smarter

I already thought of the proxie idea, but I was told that it would be just like DDOSing the proxie, and would kill it, and proxies die off to fast, i was also told that because of the multitude of connections and the way it all works in general, by connecting so much, you increase your chance of "sneaking in" a good connection, I was given a formula before that always seemed to help me grab, HackeZ (Davin) as you might know, made a program in VB that hit a connection on Dialup as good as people on servers, tho his formula was a bit more elaborate than the one he gave me: Ping(Avg) + # of Hops * .15 + Padding (20-40), for MS Delay, his program would ping the server, then each one of the hops, and mathmaticly decide the exact time it would take to get to a server, then record times to the server during a drop and all kinds of shit, and make a perfect delay...
Since '99

BrutalNet.Net

brew

Problem solved?! Now just throw it in I guess... (why does davin know so many random facts like that... it scares me)
<3 Zorm
Quote[01:08:05 AM] <@Zorm> haha, me get pussy? don't kid yourself quik
Scio te esse, sed quid sumne? :P

Smarter

I wonder if anyone had any ideas on what it would take to figure that out (the exact time it requires to connect to a server, (or how bout we make it a little broader, what would be the best method to use, if a server only allowed lets say 100 connections and 1000 people are trying to get those connections, but you want to be first, what method would best gurantee you a place in that line?).
Since '99

BrutalNet.Net

brew

You would never know that unless you knew exactly unless you knew specifics about the server, like download speed etc. And there is no magic formula. But if there was it would definately involve your upload speed, the server's download speed, yours and their processor speed, ping, so on. (I really have no clue why number of hops would be used in your previous formula)
<3 Zorm
Quote[01:08:05 AM] <@Zorm> haha, me get pussy? don't kid yourself quik
Scio te esse, sed quid sumne? :P

Smarter

Hops matter in this, not exactly sure why ... and system stats don't matter, i'm speaking connectivity, by pinging each Hop, you can see your ping time to that, and further convert that into some sort of algorithm.. im just not sure how, lol.
Since '99

BrutalNet.Net

raylu

Hops can matter if you choose to calculate it for each hop.

I think that's a bit overcomplicated, though.

EDIT: Actually, this whole idea is overcomplicated and rather stupid...
Pie?

Smarter

Yes it is, but you don't realize what people get out of this, if you run one of these drop servers, and it's efficient, and works well. People will donate constantly, people actually buy shells that are closer to these servers to load their bots on. They spend alot of money on these things, I of course don't, but it does tend to be slightly enjoyable, it's kindof a game of power, and we all know how much people love power. Also, a person named "nslai", made a bot for this before, people were offering him 100.00's for a copy of it... but he didn't release it, kept it private. When I finally got ahold of a copy, it took me months, and it was a copy for BSD. There's always an alternative plan behind this, if I can make a bot for windows (the main OS these people use of course), that works great on a crap connection, then theres a business opportunity as well as a lesiure one ;).
Since '99

BrutalNet.Net