Q. Will Punkbuster
ban me for using GUIDTracker in a PB enabled server?
A. No. According to Glenn
Courington of Even Balance, the worst that can happen is you may get a
Restriction Kick from servers running PB Server Restrictions 2 (which
is at the discretion of server operators). If
this does happen and you still want to play on that particular server, then
simply shutdown GUIDTracker, log back in and play. You will not be
banned for using GUIDTracker.
Q. Are there any fees
associated with using GUIDTracker?
A. No. GUIDTracker can be used
and downloaded free of charge.
Q. Will there ever be
a Linux
version?
A. No (but you may be able to
run it under Wine etc).
Q. Why did you write
GUIDTracker?
A. Primarily, I was sick of
players in my local BFV server misbehaving and pretending to be someone else.
Q. Why did you add a
"watchlist" system to GUIDTracker?
A. Because PunkBuster
no longer updates for BFV and I wanted a way of quickly identifying particular suspect players when they joined the server.
Q. What makes you
suspect
players are cheating?
A. Having played BFV for many
years and delving into mod making myself, I'm acutely aware of how accurate weapons are and
because of this, it was easy to tell those players using aimbots and
anti-recoil macros. One thing these clowns seem to forget is that every
FPS game has deliberate built-in randomness which effectively stops
one player from dominating every encounter, every time. This
deliberate built-in randomness forbids things like all your bullets
hitting a single point in space and one-shot kills from happening all
the time.
Q. What does knowing a
players
alias achieve?
A. It allows you to identify
players you may or may not have come up against previously. However,
after writing GUIDTracker, I found another use - I noticed a trend in
the data collected. Many cheaters that were caught had been using
multiple (more than 20) aliases in an effort to remain "un-noticed" as
they bounced from server to server. Because GUIDTracker tracks every
alias a player has been seen using, it can be useful in helping to identify suspect players.
Q. Can I donate to the
GUIDTracker project.
A. I don't ask for money nor do
I expect it, however, I also won't stop you from offering it :-)
Q. Where is the evidence
of
those GUIDTracker says are cheaters?
A. All evidence regarding
cheaters is held by the relevant anti-cheat organisation (PunkBuster, PunksBusted or PBBans). GUIDTracker simply
identifies GUID's that show up on their public ban lists, it does not maintain a list of confirmed cheaters itself.
Q. Will GUIDTracker lag my
game?
A. No, it shouldn't. Much of
it's time is spent sitting idle waiting for the PBCL.LOG to be updated.
Q. Why does
GUIDTracker have to
connect to the internet?
A. It's part of the process in keeping the alias database up-to-date and to provide results from user queries.
Q. Can I use
GUIDTracker
without being in a game.
A. Not really. The whole point
of GUIDTracker is that it is a players/admins tool used to monitor the
PBCL.LOG. You can however, query the alias database without having to run a game.
Q. Is there a "PBSvr"
version
of GUIDTracker?
A. No, however, if enough
interest is shown and I get access to a server logs, I would
consider coding one up.
Q. I have a problem
starting or
using GUIDTracker. What can I do?
A. Email me with as much
information about the problem as possible so I can hopefully find a
solution.
Q. How can I help the
GUIDTracker project?
A. Use this program as often as
you can and email me with any ideas or improvements you would like to
see. Remember, it's only as good as the updates it receives.
Q. How can I get on
the Watch
List? Can you do it for me?
A. There's always some twit
that asks me this. The answer is you can't and no I won't.
Q. Why isn't my GUID or
the
GUID of someone I know in the GUIDTracker database?
A. Because like all databases,
it must be populated first which is why GUIDTracker sends in updates of
all the undocumented GUID's and aliases it finds.
Q. Can all
Punkbuster enabled
games be supported?
A. No. Some games have no
console access and some don't produce a pbcl.log which GUIDTracker
needs in order to track GUID's and aliases.
Q. Why aren't players showing up in the window?
A. The most likely cause is
that you haven't set the correct directory to use. You can confirm this by looking at Log Size field on the appropriate game tab of GUIDTracker. If it's blank or shows 0 Lines, then GUIDTracker
isn't monitoring the correct PB Client directory. If this is the case, Reset your Log Location and set it again to the correct file .
CREDITS
Programmer: MickK (aka PartyPooper)
Testers:
- CosmicBlue (aka GunnyBlue )
- Giteen7
- Maester
| 
FAQ
