OldUnreal (Engine)

I am not running it on Windows or a Linux system if anyone is wondering.

That leaves us with Mac or plain BIOS

I am not running it on Windows or a Linux system if anyone is wondering.

That leaves us with Mac or plain BIOS

LOL.... Ye do not know thy computers well.... To give you a hint...
MacOS is based majority on it and became 100% Unix.

He's engraving zeros and ones on a piece of rock, then uses his pagan powers to transform it into an abstract "existence" which finds it's embodiement in your computer.

Either that or he's using something like FreeBSD, Unix (not linux) or... Solaris ?

Unix (not linux)

And GNU, GNU (not Unix)

Remember guys, Gnu is Not Unix :p

Correct! FreeBSD

The above two screen shots of someone spamming servers and poeple
placing fake servers is the inspiration for the following feature:

OpenMSL.Net Unified Banlist!

I plan on adding a feature that will access openmsl.net and check if
there is a new ban list and then download it. Pricks like the above
can be effectively eliminated.

To ask poeple... Think this is a good idea?

The list will be controlled by me and only submissions are actual good
reasons along with some kind of support like screen shots! (Look Above).

The two poeple above are going to be the first 2 entrys on this list
if it does indeed get added as a feature.

Edit: Forget to mention, http://www.openmsl.net is now open and the
master: master.openmsl.net will eventually be up within an hour of
the Beta OpenMSL Release.

That's a gr8 idea mate. Maybe even you could make that every admin needs to tell you to ADD his server to your Whitelist and that it's available then. Although the first thing looks better to me, idk what do you think btw that's also a good way to stop hax0rz.

OpenMSL 0.0.1bRC1

The Win32 binarys will be up within 24 hours. Right now its just
FreeBSD and Linux Binary Builds + Source Code.

Download at: http://www.openmsl.net

Can I build it under Fail32? Pls tell me before I try so and f*ck something up. =]

Yea it compiles under Fail32....

http://www.openmsl.net/openmsl-0.0.1bRC2-WIN32.rar

This is a very unofficial RC2 WIN32 version, the source is not
released yet as its still a work in progress... and It's really RC2
not RC1 like it says . I want to fix a few things and such before
it official goes to RC2 like a few slight undocumented features .



And Yea... It doesn't segfault anymore... or try to access nul memory
locations like the good ole' Alpha loved doing.

And oh I would not recommend anyone actually using that above win32
binary yet along with the other releases. There will be a few RC betas
before it gets good enough to become 0.0.2

This is Hawks build of it btw the other developer working with me.
I think he made it look more sexy looking with native logging.

speaking of net protocols.. is there a cross platform lib for UDP for linux and windows? it seems winsock is a flaming POS with udp recieve and gives tons of problems. Just curious, really.

speaking of net protocols.. is there a cross platform lib for UDP for linux and windows? it seems winsock is a flaming POS with udp recieve and gives tons of problems. Just curious, really.

I believe POS describes most things in Windows. I am not aware of any
such lib. I think WINSOCK2 is suppose to be better somehow...

Cool, I will learn something new here. And "return 666; //this is never reached lol", wtf?

Btw why does my AV detect a packet crafter? o_O

I only use windows for the apps, but yeah it has its moments.. and I was using winsock 2 lol.

Cool, I will learn something new here. And "return 666; //this is never reached lol", wtf?

Btw why does my AV detect a packet crafter? o_O

http://upx.sourceforge.net/

Because there is one? It's an exe packer not a packet crafter lol.

It's packed with the generic binary distro so you can unpack it if
you really feel like.

2nd edit: Hawk packed it not me so the Win32 version is not UPX Packed.

Forgot, that is to avoid compiler warnings. The function returns in
the code if there is an error or not, what its suppose too, etc. so
that code is never reached but if you don't add a return you got an
irritating compiler warning that warns you that this function does
not return.

Return; or return err; or return 0;?

Return; or return err; or return 0;?

No, I posted the second part as OT. I didn't mean a runtime packer, I meant a raw TCP packet crafter I used to DDoS some díckholes back in those days, and I just felt nostalgic about doing that again, so I got a packet crafter and AntiVir deleted it. Same with WinNuke XP... I compiled it and AntiVir detected and deleted it.