 |
 |
|
|
|
|
|
| Author |
Message |
tekproxy
Distro Developer
Joined: 06 Apr 2006
Posts: 350
Location: Nederland, Texas
|
 Posted: Sat Apr 14, 2007 1:01 pm Post subject: |
 |
|
Some people in a Sphere forum said they asked the RunUO guys about ConnectUO and the protocol for it but they never got a reply. They had the impression that they wanted RunUO to be bound tightly to ConnectUO. I hope this is the case because that would serve as excellent motivation to get this thing up.
From what I gather (and this comes from the RunUO forum), the protocol is simple, and ConnectUO can only handle what is called "RunUO + UOG" requests. I'll have to investigate this more later... It looks like this:
| Code: | | 0xF1 0x00 0x04 0xFF |
RunUO responds with:
| Code: | | RunUO Items=XXX, Mobiles=XXX, Clients=XXX, Mem=XXX |
I'll replace RunUO with POL, throw in an item, mobile and online count and the memory could be configurable, unless the POL core started keeping track of physical memory, or computer stats in general (processor speed, hard drive size, available space, number of processors, operating system, etc...).
I think there's already a stastics script for the webserver (if there isn't, there used to be!). I could put all the computer specs into a config file so other scripts could use the info.
Still trying to dig around and learn more about UO Gateway protocol... |
|
 |
|
|
|
|
|
|
|
|
|
| Author |
Message |
tekproxy
Distro Developer
Joined: 06 Apr 2006
Posts: 350
Location: Nederland, Texas
|
| Posted: Sun Apr 15, 2007 12:47 am Post subject: |
|
|
Now that I thought about it, he probably didn't reply because they private message/e-mailed him. He might be more keen if I posed the question via their forums. I'll post and, failing that, e-mail him when their website comes back up.
This seems like a simple thing to code, and it would be really useful. I wonder what other simple/super useful ideas I've missed.  Maybe if the Distro Development forum had something like "Please post (good) suggestions here." in the description. 
Oh, and by digging around the RunUO code, the exact response packet should look like this:
| Code: | | POL, Name={x}, Age={x}, Clients={x}, Items={x}, Chars={x}, Mem={x}K |
Where {x} is the value.
Name = Server name
Age = Uptime in hours
Clients = Number of connected players
Items = Item count
Chars = Mobile count
Memory = Physical memory in kilobytes (1024 bytes) |
|
|
|
|
