-
Posts
8,397 -
Joined
-
Days Won
170
Content Type
Profiles
Forums
Downloads
Events
Posts posted by Benway
-
-
... nichts mu
-
Guten Morgen an alle,
ich habe folgendes Problem ich habe unseren server hier angemeldet und
-
-
Taz, new to MS Windows? :D sounds like "fatal exception" Error ... usually some memory clutter; having the translation (schwerer Ausnahmefehler xD) in mind, i still wonder what a "light regular error" would be ;P
- 1
-
Haben in der mp-cfg den Wert 125 gesetzt.
Wie? poste mal
-
Nobody cares for your "issues". Get a life or join #whine&care. I'm done now reading more useless yada yada from dipsticks, who's only inclination is to waste our time, all followups will now join their fav member group instantly.
-
We ban guids, ban is valid and stays. Case CLOSED
-
can you explain the logic behind needing a website to have a team account?
Regulations in place for security reasons will not be debated in public forum areas.
-
I want people to not be able to have a 333 setting. I think it is a unfair advantage to other players that cant do the special jumps. This is what my server is set to right now. pb_sv_cvar "com_maxfps" OUT 0.000001 43 So I would leave that setting in there and add pb_sv_cvar "com_maxfps" IN 43 150 ? What is the OUT and the IN mean? Thank you for your help.
pb_sv_cvar [cvar_name] [iN|OUT|INCLUDE|EXCLUDE] [Param1] [optional_Param2] ... PB will kick players with cvars in/outside the specified range.
IN = setting has to be between Param1 & Param2 inclusive.
If no Param2 is present, setting must equal Param1.
OUT = setting may not be between Param1 & Param2, both Param1 & Param2 are not allowed as well.
If no Param2 present, setting may not equal Param1.
INCLUDE = setting must include the string given in Param1.
EXCLUDE = setting may not include the string given in Param1.
Does not change or remove previous blocks of same cvar, both will operate, unless a "pb_sv_cvarempty" was issued.
thus
pb_sv_cvar com_maxfps OUT 0.0001 43
pb_sv_cvar com_maxfps OUT 151 1000
pb_sv_cvar com_maxfps OUT 0
would equal
pb_sv_cvar com_maxfps IN 44 150 // 43 is connected with a no-recoil exploit of q3e
as said i see no use to restrict 0 (uncapped) as only a stable FPS value will have any effect on jumping/recoil/hitboxes.
333 is in connection with a hitbox delay exploit (player is hard to hit), has not v. much to do with jumping. Sorry to destruct your illusions, but this "unfair advantage" to be able to do the special jumps is a result of practice, i.e. of wasting time on boring Trickjump Maps like e.g. this guy --> http://www.youtube.com/watch?v=cDXpxSDB3TE who always used com_maxfps 76 or 125. (no, to restrict these values was ... dorky)
P.S.:
]\com_maxfps "com_maxfps" is:"125" default:"85" ]\condump sof2_fps.txt
whatever.
-
pb_sv_cvar com_maxfps OUT 0.000001 43
pb_sv_cvar com_maxfps OUT 151 1000
why? game default is 0 (no setting/uncapped)
-
... auf Bearbeitung warten http://www.pbbans.com/forums/index.php?showtopic=66969
-
-
hmm ... possibly this http://www.pbbans.com/account_application.php is the missing link?
-
: PB UCON Profile not added due to duplicate profile name (pbbanshub)
pb_sv_uconempty
pb_sv_uconadd 1 64.27.21.46 pbbanshub pbbanshub
pb_sv_writecfg
-
its easy. if you did your homework, http://www.evenbalance.com/publications/bf2-ad/index.htm
BF2CC does not pick them up ... they do register in the pblogs. -
ich rate von der Benutzung s
-
Der Ban war fehlerhaft und ist jetzt gel
-
-
-
It is or has been coined the "Ghost Hack". BF2CC does not pick them up and they cannot be seen through, for instance, our control panel in our internet interface.
Thankfully, they do register in the pblogs.
Usually i just spam http://www.evenbalance.com/publications/bf...ex.htm#commands in cases like this, as i'm tired to repeat myself - guess tired from answering ~1k posts re so called smart (the opposite baby) hacks for ET spoofing dis and spoofing dat (all kind of game specific nonsense (basicly same problem as described here), no need to run a cheat to "spoof" client-sided items, /console or editor will do ... simply use server-sided /pb_sv_plist and you don't even mention any spoofed unneeded gizmos, leave alone "mirroring (MAC-based-pseudo-guid) bans" etc. etc. clientsided fool-catchers that only will work on noob admins using flawed admin-mods' !ban Name) - maybe about time again for an extended remix ;p
^EB Link^ in a full sentence: You really should start to use PunkBuster Server - instead of flimsy, flawed game specific trash. This goes for all games, nobody running a pb enabled server never ever thought about using game's /BanUser
/BanClient /BanID or similar, seems just EA managed to brainwash everybody with "ranked" restrictions (more afraid of admins than cheaters? obviously yes), "hash" "account" BS plus marginal pb integration in a console that was designed to be a pain. Just note the last sentence of above quote, how come?
And no, it's not a smart hack (basicly tis an exploit of game vulnerabilities), it's BF admins having no clue about PB, partially due to the poor game integration, ok admitted, but still: Ban the GUID (no, no "hash" "name" "Global ID" or whatever BS) via RCon & PunkBuster Server - to have WebTool* setup is your best bet: >click!
[ console: /rcon login 'pass' then " /rcon exec PB_SV_
... " ] or [ HLSW: exec PB_SV_Ban
"reason" or exec PB_SV_BanGuid "reason" resp. exec PB_SV_BanMask ] >click HSLW setup is BF-Port-Guesswork, ServerIP:ServerPort:GamespyPort (default=29900 others are used though),
for the proper RCon port search FTP /mods/bf2/settings/modmanager.con e.g. mm_rcon.rconPort 6711 (or 4711, 4712), >click1click2
Note: this is plain rcon w/h daemon, i.e. not the same port as bfcc
The safest way was to ban via 1. PB WebTool* or HLSW ( "reason in quotes"
I know its not convenient with no console echo, but: it works. Opposed to the rendered useless convenience.
*From my experience even totally unresponsive (dead rcon, /connect stalls) servers still could be accessed and restarted via PB WebTool.
Does anyone know of any way of defeating it?You could wait for 2 patches (one no doubt: /rcon logout, crash2desktop, "namehack" etcetc = game) ...
or setup PB WebTool*: http://www.pbbans.com/info-center-hubguide.html#webtool http://www.evenbalance.com/publications/bf...dex.htm#webtool , hint to guess a working port: http://forums.theplanet.com/index.php?showtopic=80480 IRC quakenet.org #pbbans
Subsequently banning (pb) guids is the only reliable solution. IP is no alternative really (banning dynamic IPs = always a temp. ban ... yet space for another */me facepalms* Story/Hoax: player was using ... yes, a Router ;P )
P.S.: you cannot "manipulate" a GUID (assigned by PunkBuster SERVER), what is possible is to create *.reg files REGEDIT4 [HKEY_LOCAL_MACHINE\SOFTWARE\Electronic Arts\EA GAMES\Battlefield2\ergc] @="cd-key_here" - just this requires another/more cd-key(s).
-
-
http://www.evenbalance.com/index.php?page=faq-bf2.php
What is a guid?In general, GUID is an acronym that stands for �globally unique identifier�. The guid inside PunkBuster is used to identify players with something more solid than their playing name or IP address. Your guid is loosely based on the cdkey that was used to install the game on your computer. When Server Admins kick or ban a player from their server(s), PunkBuster uses the player's guid to enforce the kick/ban. Since it is based on the game installation, it is a better way to identify individual players than by looking at their IP address or playing name. For those concerned about privacy, PunkBuster uses a 128-bit one-way hash (a mathematical function) to generate the guid from the cdkey so that no one can figure out or compute your cdkey by knowing your guid
Vermutung: der cd-key wurde von einem trojaner aus der windows registry ausgelesen. Danach wurde der key zum cheaten benutzt. Der MPi link zeigt die History mit den unterschiedlichen IPs.
Neues Spiel ist notwendig.
-
-
q3key ftw ;P
What's that?
in Enemy Territory
Posted
its a CVar that is set to random player names connected to the current server. Taken from experience, don't ask me why :P
might be the last player one was following in spectator mode