Orb / DevLog: Recent posts

The old method of the update loop used a lot of cpu power as it kept re-cycling through a while test until enough time elapsed.

using time.sleep() I can suspend the thread until the required time has passed, and update again.

The CPU load at idle is changed now from ~50% to ~0%, the way it should be. This should hopefully free up resources and make the sockets much faster/stable.

Sounds:

Data Crash, Join Server, Leave Server.

A bit less errors and fatal crashes should happen now.

I wrote a new server list for YSFHQ in python today. I hope Eric implements it. It fixes the whole 'duhhhh i'm blind gimme packets durrrr' that the old script was doing (it would take anything, upto 13 packets, and HOPE that it got them all.)

The new serverlist will connect, and wait till it has all the data before disconnecting. as a failsafe, it will also disconnect once it receives a full aircraft list.... read more

Deaths not counted towards K:D unless a user commits suicide by causing damage to themselves (not crashes) or when a user is killed by another user.

Found a bug in the YSFHQ PHP Bot script, where all messages of type 32 break the script. Hopefully EricT of YSFHQ can fix this issue soon.

Re-worked orb to allow 'PHP Bot' to read the server, even in YSFHQ mode. PHP Bot, like any user, can be banned and prevented access to the server, this makes your server appear offline to the server list.

Also: Because PHP Bot bypasses the YSFHQ log in system, PHP Bot can not read packets of type32 apart from what Orb specifically sends to it. futhermore, PHP Bot is force booted after sending the aircraft list. This means users can not impersonate phpbot to listen to the server, see who's online, talk or join flight. PHP Bot is essentially a banned client, who can read the server info. That's it.

Whenever a server or client DC's, some functions would return -1, because they receive empty packets instead.

in response, the server tries to send a message to the client, and failing that, closes itself.

(no more bugged packet spam, only one message before a close test)

Acknowledges password upon entering, then polls HQ.
Has a "still working" message every five seconds.
YSFHQ call threaded.

Was comparing to the client sock instead of server sock, and no try/excepts were making a mess.

This should now be fixed again.

Currently clogging the feed, pretty useless, so figured it would be rejected for now.

Fixed the error of NOTHING working if MasterGroup not existing!

The user-> info -> permissions strcuture was flawed and some instances were referencing username, others ThisUserName, causing massive issues for all but the last loaded user from the database. This has been fixed.