Do you think I could just leave this part blank and it'd be okay? We're just going to replace the whole thing with a header image anyway, right?
You are not logged in.
^
I'm a bot nub and heard from Tomahawk some users that using a library is also nubish (I disagree), but I am curious to know how it's done and think that I can learn a trick or two.
Will it help? Is there already a guide somewhere? I don't know. Simply put, how do you do it?
Offline
There's no point in not using PlayerIOClient, because using it to connect to PlayerIO makes perfect sense. If you don't have a specific reason not to use it (such as using a different programming language without it), then you should just use it. Either way you'll be using a library, just more general ones such as TcpListener.
Offline
You can look up the EECloud PlayerIO implementation to find out how it's done. It's not too hard, but if you don't use the PlayerIO library, you'll just be using a networking library instead.
Offline
You can directly inject packets into the socket the packets are being sent and received from if you inject into a specific process, like the embedded client.
This is essentially how I achieved EEProxy, which I'm not going to be releasing because of incredibly messy code and convoluted.
Or, you can simply make your own miniature PlayerIOClient, which I've done as well with even worse sloppy coding.
Essentially all you need to do is handle the API requests, serialise and deserialise protocol buffer formats, and establish a socket on the endpoint you receive.
Once you do that, you just send a properly formatted join Message packet (see EEDecode for the Message class code) with an auth string that the API gives you.
Pretty much once that's all done, you can send and receive packets fairly easily.
Maybe one day I'll actually make it in clean code but it would be much better to write it from scratch.
*u stinky*
Offline
There's nothing noobish about using a library. If the wheel has been invented, don't reinvent it, use code that is made to be used by others.
I personally like to write as much as I can myself, but doing stuff like PlayerIO myself is going too far if you'd ask me.
Offline
I'm a bot nub and heard from Tomahawk some users that using a library is also nubish
I stand by that. Good for you if you start with PIO client and not an EE sdk - that is, just as long as you don't start with a console bot.
If the wheel has been invented, don't reinvent it
The wheel was invented: PlayerIOClient.dll. The other EE libraries are the reinventions.
One bot to rule them all, one bot to find them. One bot to bring them all... and with this cliché blind them.
Offline
Don't get on his case about not wanting to use PlayerIOClient. If I was to make another big EE related project, I'd probably use C++, which isn't supported by PlayerIO, so I would have to roll my own anyway.
Offline
den3107 wrote:If the wheel has been invented, don't reinvent it
The wheel was invented: PlayerIOClient.dll. The other EE libraries are the reinventions.
That's exactly what I said.
Offline
[ Started around 1734497052.9237 - Generated in 0.035 seconds, 12 queries executed - Memory usage: 1.45 MiB (Peak: 1.58 MiB) ]