Results 1 to 5 of 5
Thread: Why not an anti commander Hack?
-
08-25-08, 12:58 PM #1
Why not an anti commander Hack?
I don't know why this cant be implemented into BF2 Server side by EA to stop the commander hackers.
It would be very simple to at least stop the massive drops of cartillery and other stuff, if not the hacker completely, yes they hook the server, but the hook still has to tell the server to do it.
The game already has an anti spam code for the in game messages, yes sir, no sir.
So why not implement code, so you can not drop the stuff on a massive scale with cartillery anti spam code, similar to the chat spam code, and even report that it is being tried if someone is trying to do it.
We have similar anti spam plugins in our DoD server.
I don't get why they have not done this, it's simple as black and white. EA is just dumb?
-
-
- Join Date
- 02-13-07
- Location
- Fort Worth, TX
- Posts
- 42,785
- Post Thanks / Like
- Blog Entries
- 5
-
-
08-25-08, 04:18 PM #5
Re: Why not an anti commander Hack?
Yes, yes and yes.
Some simple sanity checks at the time of client connection could eliminate 99% of all the hacks. Sanity checks on things like commander resources, proper reported client hashes, name checks, and checks on which client is sending which request (and how often) (like, for example, is the squad leader the one sending the "kick from squad" request or is it the hacker who just connected; is the commander's client the one that issued the "resign" command; has a car drop command been sent in the last 30 seconds; was the commander the one who sent it) instead of using the UI to control player behavior would make BF2 nearly invincible.
Instead, they use the UI like dolts. They don't rigorously enforce client identity. They don't have good reporting tools. They don't have good administration tools. But we keep buying it all the same.
Draco
Thread Information
Users Browsing this Thread
There are currently 1 users browsing this thread. (0 members and 1 guests)
Bookmarks