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.
It appears that using WPE Pro to send packets to EE is much faster than sending them using the PlayerIO API SDK. However, WPE Pro requires a GUI, and possibly Firefox (or another internet browser with flash) running at the same time. When running all of these programs on a server, it is a bit resource-intensive, and limits what servers this can be run on.
Is it possible to reproduce the functionality of WPE Pro using an sdk without a GUI (like a TCP packet filter)?
Offline
It shouldn't be that much faster. You could possibly inject into the browser and then take control over that established socket and send in packet data using EEDecode classes or similar (though, nobody else made a PlayerIO message class)
*u stinky*
Offline
They did, they didn't publish.
Warning!
This user has been found guilty by The Committee of Truth of using honesty, and reminding people of the past, without permission and outside of the allotted timeframes.
I’ve been asked if I’m ChatGPT5.
The answer is no.
I hope this helps! Let me know if you have any other questions.
Everybody edits, but some edit more than others
Offline
You could probably use reflection to access the network socket directly within the PlayerIO library. You would then be able to send raw information as fast as you wanted, just like with WPEPro, but with no need for anything other than standard bot libraries.
[ Started around 1743878868.3064 - Generated in 0.030 seconds, 12 queries executed - Memory usage: 1.41 MiB (Peak: 1.52 MiB) ]