-= HACKBUSTA 3 =-

Build: 5

Authors: Coomman and Venim
Deployment version: }TCP{Wolf aka Mia_The_Chaotic


Install:
--------
Copy all files to your Unreal\system directory.

Add these in Unreal.ini at proper place [Engine.GameEngine]:

ServerPackages=hb3
ServerActors=spawner.makeitso


RUN:
----
hb3 will run on its own and - unlike other console checkers - NOT display any
ingame output. Of course it will log kicked players etc alongside with the
kickreason.


Settings:
---------
Advanced Options -> Hackbusta 3

DisUPak:   If you want to autokick all UPak Console users, enter something
           here (doesn't matter WHAT, just make it so that the string is not
           empty). To allow UPak console users again, just empty this line.
           NOTE: THIS WILL BLOCK GOLD USERS EVEN IF THEY USE THE UBROWSER
                 CONSOLE!! LOG WILL SAY 226F FALSE PACKAGES!
           Blocking UPak users without hackbusta:
           Make a copy of a small file like "Jumpad.u" and name it "UPak.u"
           then make this new file a serverpackage :) This is even better as
           it does not produce the lag resulting from player joins and
           leaves...


NOTES:
------
This code is BETA. No guarantee is given for whatever. If aliens kidnap your
wife, your food starts rotting at an insane speed, your computer grows feet
and runs away or whatever else - bad luck for you.

Compliance:
Unreal 224v (Win), 224b7 (Mac), 225f (Win), 226f (Win), 226b (Win)


LOGFILE:
--------
hb3 logs the reason why it kicks players (e.g. Illegal Console). Some messages
may cause confusion though. Note that hb3 is more aggressive towards players
and may cause a few "false" alerts when it thinks it has been hacked.
Yes, hb3 makes checks to see if the tests are done on each client, and if
those tests fail hb3 will assume the client is hacked and kick him. However,
there are 2 different possible HACKED messages.

One has the not "(SRV)" and one has the note "(CLT)" - representing "SERVER"
and "CLIENT". If it tells you client is hacked with the (CLT) tag it is
DEFINITELY a hacker/cheater! However, a hacked message indicating (SRV) is
very often a false alert! Please observe if the same PLAYER gets booted 
again and again with this message, if yes, you can assume he's a
hacker/cheater, but if he gets only booted once or twice in a row, it was a
networking failure.

PACKET LOSS, BAD CONNECTIONS AND LAG MAY CAUSE HB3 TO FALSELY THINK A CLIENT
WAS HACKED BECAUSE IT COULDN'T VERIFY THE CHECKS WERE DONE PROPERLY - but only
because it didn't receive the values.... NETWORKING FAILURES ARE EVEN MORE
LIKELY TO OCCUR THE VERY FIRST TIME A CLIENT CONNECTS.
