Jump to content

Benway

Site Staff
  • Posts

    8,397
  • Joined

  • Days Won

    170

Everything posted by Benway

  1. there is nothing to discuss, waste of ammo, beta == pb unsupported. Ever since. Period. Epic was all the whine of Longhorn beta noobs unable to read, whining 1st: doesn't work, 2nd: banned for game hook #81234 :P
  2. http://www.pbbans.com/account/server.php Jeweils Server-Game1 l
  3. means there was no evidence found for cheating, clean players information is not public for security reasons. Our database is based on GUIDs http://www.evenbalance.com/index.php?page=support-bf2.php
  4. *************************************************************** Team: Night-Fighter (|NF|) Account ID: 4852 Streaming Status: Streaming (5 / 5) ***************************************************************
  5. server werden automatisch deakiviert, wenn sie 3 tage nicht streamen. 86.110.94.11:30300 Call of Duty UO (PBBans Hub) last streamed log received: December 03, 2008 at 9:43:04 am post#4 + pb_sv_task 10 7000 pb_sv_ver
  6. http://www.pbbans.com/forums/index.php?showtopic=29047
  7. pbsvuser.cfg ins server /pb hochladen, /rcon pb_sv_restart ( pb-restart l
  8. Wenn das die einzigen Fehlermeldungen sind, ist PB Server asbach uralt (pb kennt pbucon noch nicht) ... manuelles punkbuster update http://www.evenbalance.com/index.php?page=dl-cod.php (pb coduo = pb cod1)
  9. game : bf2 i can't spot a problem in the streamed logs , random example : [12.01.2008 00:21:13] ->PBSV: Auto Screenshot 007862 Requested from 20 LOCSMOKE [12.01.2008 00:21:16] ->PBSV: Screenshot c:\game\ATAC\GameServers\TC*edit*\pb\svss\pb007862.png successfully received (MD5=E6C88AB8637BBAB151E5E44380235114) from 20 LOCSMOKE [*edit*1e7f(-) 71.33.*.*:57142] ... looks absolutely normal. Post your pb/pbsv.cfg , maybe this helps to find the issue
  10. persistent/reliable methods : 1. manual updates via 2.a. PAT (linux servers only) 2.b. jPat (FTP update only)
  11. LoL. Das ist consolisch :P /rcon pb_sv_writecfg pbucon.use /rcon pb_sv_restart /rcon pb_sv_autoupdban 1 /rcon pb_sv_task 10 7000 pb_sv_ver /rcon pb_sv_usessionlimit 9 /rcon pb_sv_uconadd 1 64.27.21.46 pbbanshub pbbanshub /rcon pb_sv_writecfg oder so: http://www.pbbans.com/account/webtool.php
  12. http://www.pbbans.com/forums/index.php?showtopic=71571 http://www.pbbans.com/forums/index.php?showtopic=29047 / http://www.pbbans.com/info-center-hubguide.html
  13. LoL @this topic http://www.annoyances.org/
  14. 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
  15. 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
  16. 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.
  17. We ban guids, ban is valid and stays. Case CLOSED
  18. Regulations in place for security reasons will not be debated in public forum areas.
  19. 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.
  20. 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)
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.