Alright I've recently been studying the 39.dll. And im having troubles with a couple of things. One, im working on a lobby waiting room where you wait for the host to start the game. Ive been able to manage this in mplay however soc(39.dll) is much different. Can someone help me set this up?
Other news: Well im starting to convert me Block mini games Game to online. Which is why I asked the question above. I wont be releaseing any demos for it forawhile.Other Other News: I recently busted out the dream cast, and damn its fun. NfL 2k is epic. Its soo good for how old it is. I loved dream cast, to bad it had some problems and failed. Also im accepting any minigame ideas you guys might have for my mini game Game. The link is in my previous blog.
loads faster, can send more information per byte. Much more efficent.
//more information per byte//
A byte is set at 8 bits, and that doesn't change with the dll.It's not that you can send more information, it's the amount of control you have over it. Game Maker its mplay functions have only two types of data types, string and number. The number format is a long data type. IIRC that's 4 bytes for a number ranging to 2^32 positive and negative (You'd have to read up on this more for the exact numbers, I can't remember them clearly). With 39.dll I can send a short data type which is only one byte and can handle a value from 0 to 255 positive and negative. Now it really doesn't make sense to use mplay's long data type when sending a number that can fit comfortably into a short data type with 39.dll.
Another advantage is non-blocking connections. Notice how that in mplay if you want to open a port or connect to a port it will freeze your game. With 39.dll you have the option of avoiding that freeze.Directplay on its own already restricts the amount of utility you get out of it. When it was translated into GM, this just got worse. The end result is something that isn't really effective for games of any decent size. It's lack of control over udp ports also makes it rather difficult to make an action game.Oops forgot to add something.
The most important reason to use 39.dll or any other sockets for multiplayer is that these sockets are universal. If you learn how to use winsock on GM, you'll be able to adapt quite readily to using it on any other programming language. Limiting yourself to directplay would be a waste.ah, well thanks for clearing it up :)
ps i remember u from wc3.