[>NF<] Noobs Forever Game Servers - Forums

I really didn't expect this. 06:25 and I was about to go to bed but decided to check the NF site first. Then I looked at the PBBans banner and had the unpleasant surprise of reading:

Latest ban: Gimbo -CI-

I went to the PBBans site to check the details of the ban, and the PB GUID matches his = it wasn't someone else using his nick.

Ban details:

->PBSV: VIOLATION (MD5TOOL) #9002: ^8G^7imbo ^4-CI- (slot #9) MD5Tool Mismatch: libETH.so (len=2048) [2ecf4ac2cb8b3f5d1d6805b4f3f6fc3d(VALID:312) 82.234.*.115:27960]

Full ban details here.

but md5tool isn't a cheat ban.... or is it?? I remember that some time before lots were getting kicked by md5tool mistakes by PB, and they were claiming that they weren't cheating... we can see lots getting kicked in NF by that...

Bad news

Didn't expect him cheating :s (never noticed it too)

qu4s3n4d4 wrote:but md5tool isn't a cheat ban.... or is it?? I remember that some time before lots were getting kicked by md5tool mistakes by PB, and they were claiming that they weren't cheating... we can see lots getting kicked in NF by that...

Why don't tech noobs just play quietly?

You can be kicked by PB with "MD5Tool" in the message because of packet loss between you and the PB server or the PB services being blocked by firewalls, antivirus, etc. in your computer, just like all other PB kicks for the same reason.

Read the fucking ban message more carefully and you'll see that PB, via the MD5Tool, detected the presence of the libETH.so cheat file in his computer.

By the way, even if you download a cheat to, errr, see how it works, even if you delete or uninstall it, traces may remain in your computer which PB or the extra PBBans and PunksBusted checks may detect. So, DO NOT "TEST" CHEATS.

I didn't know libeth whatever is a cheat! Never used one before...

qu4s3n4d4 wrote:I didn't know libeth whatever is a cheat! Never used one before...

Get the undetectable NF Complete Cheat Pack here.

Maybe he just downloaded the fucking thing and PB found it somewhere outside the ET install... or was using it with a lower accuracy setting. Well, the fact is, the file was there.