Home » Archived Forums » RenGuard Network Bans » bypasser - where to report
Re: bypasser - where to report [message #208921 is a reply to message #208181] |
Wed, 19 July 2006 17:59 |
|
jnz
Messages: 3396 Registered: July 2006 Location: 30th century
Karma:
|
General (3 Stars) |
|
|
=HT=T-Bird wrote on Sat, 15 July 2006 14:54 |
Blazer wrote on Fri, 14 July 2006 16:47 | Yep he's a definite bypasser.
Looks like he changes IPs a lot, probably to avoid bans:
207.210.22.157
207.210.16.153
207.210.20.86
207.210.18.68
207.210.19.44
207.210.23.131
|
|
if i used the modem i got for broadband my ipaddress would change everytime i restarted my computer, i can change it now by unpluging the router and plugging it back in. did you do a ip look up? you can see where a ip is from.
RG uses the hdd serial to see detect computers identity. it takes less than 5 minuts to rewrite that. to be totally honest RG is S***. if some n00b really wanted to cheat, it is easy. go to gogle and type in bypass rengaurd and you will get 100's of results. the only thing RG is good for is updates, maps get "de-buged" and blocks put on to stop b2b.
much more better would a server rengaurd, where the server detects cheating insead of a client. so no-one has to complain if some-one cheats. they get banned simple as that. it takes a small time to create another nick but ppl woulnt do that. it takes too long.
i am wrinting a script to detect the big head cheat in the future and see uf that is better than rengaurd, as soon as the bullet doesn't hit the head but the person dies; *BAM* they get banned.
btw: i don't want people to take offence to theis post, it is just what i think. the poeple who programed rengaurd did a good job. they should of planned it better. i also *HAVE* and i do mean *HAVE* *NOT* tested this theory. cheating is for dickheads or ppl just fooling on there own server for a laph
i seen a cheater server the other day, are ppl that go on that loosers, NO. they are just having fun.
|
|
|
|
|
bypasser - where to report
|
|
|
Re: bypasser - where to report
|
|
|
Re: bypasser - where to report
|
|
|
Re: bypasser - where to report
By: Goztow on Mon, 10 July 2006 13:20
|
|
|
Re: bypasser - where to report
|
|
|
Re: bypasser - where to report
By: light on Mon, 10 July 2006 22:59
|
|
|
Re: bypasser - where to report
By: Goztow on Tue, 11 July 2006 00:25
|
|
|
Re: bypasser - where to report
|
|
|
Re: bypasser - where to report
By: luv2pb on Tue, 11 July 2006 10:09
|
|
|
Re: bypasser - where to report
By: Berkut on Tue, 11 July 2006 16:00
|
|
|
Re: bypasser - where to report
|
|
|
Re: bypasser - where to report
By: Goztow on Wed, 12 July 2006 04:01
|
|
|
Re: bypasser - where to report
|
|
|
Re: bypasser - where to report
|
|
|
Re: bypasser - where to report
By: Blazer on Fri, 14 July 2006 14:47
|
|
|
Re: bypasser - where to report
|
|
|
Re: bypasser - where to report
By: jnz on Wed, 19 July 2006 17:59
|
|
|
Re: bypasser - where to report
By: Blazer on Tue, 01 August 2006 17:00
|
|
|
Re: bypasser - where to report
By: Goztow on Sat, 15 July 2006 03:31
|
|
|
Re: bypasser - where to report
By: snoix on Sun, 16 July 2006 18:42
|
|
|
Re: bypasser - where to report
By: Goztow on Sun, 16 July 2006 23:53
|
|
|
Re: bypasser - where to report
By: snoix on Mon, 17 July 2006 04:52
|
|
|
Re: bypasser - where to report
By: cmatt42 on Mon, 17 July 2006 15:25
|
|
|
Re: bypasser - where to report
By: Zion on Thu, 20 July 2006 11:06
|
|
|
Re: bypasser - where to report
By: jnz on Thu, 20 July 2006 11:33
|
|
|
Re: bypasser - where to report
By: Zion on Thu, 20 July 2006 14:40
|
|
|
Re: bypasser - where to report
By: jnz on Fri, 21 July 2006 13:44
|
|
|
Re: bypasser - where to report
By: Zion on Fri, 21 July 2006 14:23
|
|
|
Re: bypasser - where to report
|
|
|
Re: bypasser - where to report
|
|
|
Re: bypasser - where to report
By: Ma1kel on Sat, 22 July 2006 14:58
|
|
|
Re: bypasser - where to report
|
|
|
Re: bypasser - where to report
By: ninjahh on Mon, 31 July 2006 13:52
|
|
|
Re: bypasser - where to report
|
Goto Forum:
Current Time: Tue Oct 15 22:08:27 MST 2024
Total time taken to generate the page: 0.01240 seconds
|