ok let me be clear, when I say "plugin" I thought I made it clear I was using the word loosely cause it wouldn't actually plug-in or connect in any way to the server other than through local network messages. what I was asking is something codewalker should know and should save me time actually skimming through the documentation and learning a different code set.
I really just need to know what information is capable to be sent and received with the client and possibly the message composition in a list form.
Unless XMPP uses some secret proprietary message encoding for which I'd have to develop a reading and writing database, then the info between programs is just data and it really doesn't matter which API or program made it. it's not like python or blender will attach some binary signifier that "this message was created with python 2.6.2 socket module, GPL 2011" that could cause XMPP to say "hey that's not my message, I'm not gonna read it", it sends what I script it to send, if I script it to mimic the way XMPP or any other software construct their messages then the PC client won't be the wiser, see what I'm getting at?.
message format is what I'm after, and I'm aware there may be multiple variations, but I'll only end up using a handful.
some of my questions have already been answered and I thank you all for your time in answering them, such as the knowledge the XMPP does not send IP or port externally. or stuff like "you have to send it as an XML stanza, Note that if it isn't a chat message, character presence, or position metadata, PC will ignore it."
it does make it nigh impossible to do what I'm attempting.
I.E. the gates are there but there's no ability to get the message to them, the timer window and score window are there somewhere but again no way to get the data to them. even if I did an XML stanza it would be ignored if it isn't one of the few data types allowed.
I will not write java, so I guess it ends there. the only other way is to make my own interface program to the CoX client itself, and honestly I haven't even tried so.. yeah, not gonna happen any time soon and would seem a bit redundant seeing as Codewalker and Leandro have already come this far.
Unless,.. Injection, that might work, but that's another question. assuming I could send a message to PC that it interprets as a chat message, would it process this message by it's own rules?, or would it pass it to the CoX client code for processing?
if so sending a XML stanza with XMPP's position format containing a script in CoX's server message format telling the client how much time is on the timer or which gate is now active could work.
but no, PC probably just does everything itself, probably doesn't actually send any communication data to the CoX client at all just reads it like a book and emulates it.
So in summary, I know enough now to know it won't work. so much for my idea. thankyou for your time. for it to work PC would at least have to be enabled to receive other data types or for CoX's client code to process the message so injection techniques can be used. greatwork anyways, keep up the efforts.
Incidentally, it's not that we particularly love Openfire, but it is the only XMPP server that worked properly out of the box and wasn't a major pain in the arse to configure. If someone else tests another server and finds that it works fine with Paragon Chat, yay! We can use that.
Thats the other side of it, I could make a python XMPP server, but then I really would have to read all the documentation, 4 years is the standard development time for new projects of this caliber with one person, and 4 years is a long time.
XML stanzas.. I'll at least research that to see if I can do anything with it, can definitely make them in python even if I have to program the rules for their composition myself.
edit: ah yes XML stanzas, the standard XMPP format hence why codewalker dropped the documentation on me. too much to read for 11;57 pm. I'll give it a go after the 10th. but it's learning a whole new language.