Re: Improper behaviour
Posted: 12 Apr 2012, 19:48
Your daddy..Nobody..
No you weren't banned, and you already know this full-well, as you re-join in the next map.~Blade~ wrote:I killed an enemy (psycho) with 1 GEP rocket that also killed Fury. For which I was banned.
Well, Blade, on this particular occasion it would appear that you have slipped through my grasp. Once again you come out smelling of roses. Congratulations. On the bright side, at least now your gaying alias 'P1ayer' has been exposed. There are, of course, countless other logs of you teamkilling. I might as well post an example since no one believes me anyway.None of what you have shown are teamkills
Code: Select all
ScriptLog: P1ayer_322(5) killed Player_568 with a LAW Rocket!
ScriptLog: P1ayer_322(5) killed MRTEAMER with a LAW Rocket!
ScriptLog: P1ayer_322(5) killed P1ayer_322 with a LAW Rocket!
ScriptLog: P1ayer_322(5) killed MRTEAMER with a LAW Rocket!
ScriptLog: P1ayer_322(5) killed MRTEAMER with a LAW Rocket!
ScriptLog: P1ayer_322(5) killed MRTEAMERNone
ScriptLog: P1ayer_322(5) killed MRTEAMER with a LAW Rocket!
ScriptLog: Player_568(2) killed P1ayer_322 with a GEP Rocket!
ScriptLog: P1ayer_322(5) killed Player_568 with a GEP Rocket!
ScriptLog: rodyaj(6) killed P1ayer_322 with an Assault Rifle!
ScriptLog: rodyaj(6) killed P1ayer_322 with a Sniper Rifle!
And here you encourage others to teamkill:
Say: P1ayer_322(5): dont talk to him
Say: P1ayer_322(5): just teamkill him
Show me where I am doing this.~Blade~ wrote:4. You are calling numerous decent players cheaters
But it does exist; it just isn't reliable evidence.it turns out that no such evidence exists
I gave all my evidence to developers. But fine, since people are so insistent, I'll just release it for everyone. Just watch now as everyone makes the same mistakes I have lately and misinterprets the data.and you are not willing to give to anyone
I've already said that the evidence is unreliable. I don't expect anyone to believe it.and expect everyone to believe it.
Code: Select all
MiniMTL: Possible cheat detected:
MiniMTL: Player Caught: .
MiniMTL: Player Address: .
MiniMTL: Cheat Found: Invalid Console class Detected. ()
Code: Select all
MiniMTL: Possible cheat detected:
MiniMTL: Player Caught: agent009.
MiniMTL: Player Address: 94.xxx.xx.xxx:xxxx.
MiniMTL: Cheat Found: Invalid Console class Detected. ()
Conclusion: there is only a 5% chance the four players were hacking. So I don't see the point in actively pursuing these four. More than likely they just had bad pings.~][FGS][Nobody~ wrote:Hello Shades,
your interpretation is correct.
I don't know what Dejavu changed on miniMTL after he stole the source code but if the anti hax protection is still working the way I once programmed it, then it does the following..
When a player joins, miniMTL initiates a delayed check for stuff like custom console classes.
The delay is done because DX needs some time, until replication works reliable for a player after his/her join.
After the check is instigated, further seconds pass before the result is evaluated.
So let's evaluate your first case.
A player joins and immediately leaves again. There it couldn't get any information from the player because the player is not present anymore.
I bet your server log also contains some accessed none warning right before the 'possible cheat detected' message.
I admit, this is definitely a false alert and a weakness of the check, I made for miniMTL 6 years ago. It could have been catched by further checks.![]()
Now your second case.
A player joins and doesn't leave but then (s)he gets kicked along with the 'possible cheat detected' message. As you'll have noticed, it shows more information, such as player name, IP-address, etc, aleady. It only doesn't show the class name of the custom/invalid console class. In case of a custom console class, it should show the corresponding class name within the parenthesis after the 'Invalid Console class Detected.' message
As mentioned above, it initiates the check and waits some seconds before evaluating the result. Usually those wait time is sufficient. However, on a massive lag impact the time could exceed and the result is evaluated before it arrived from the client.
Since no result is treated as wrong result, the player gets kicked along with the message:If no result was returned from the client, the parenthesis are empty, which results in showing such a message.Code: Select all
MiniMTL: Cheat Found: Invalid Console class Detected. ()
Unlike the first case, the cheat found message of the second case is no weakness in the code of miniMTL.
The reason for treateing no result is as wrong result is the following..
Although it's very unlikely, there's the possibility that the missing check result was not caused by lag but by a haxor attempting to bypass the protection.
I admit, the chance for this is approx 5% but in my opinion it was enough to take that into account.
So for your calm.. in 95% of invalid console class cheat detections with EMPTY parenthesis, it's lag and not really a haxor.
HOWEVER, if you got a message like:Then you can be 100% sure to have catched a cheater because in that case it definitely got all information and you even know what the player used to cheat, when you look at the parenthesis in the last line.Code: Select all
MiniMTL: Possible cheat detected: MiniMTL: Player Caught: agent009. MiniMTL: Player Address: 94.xxx.xx.xxx:xxxx. MiniMTL: Cheat Found: Invalid Console class Detected. (Funbot.FunbotC)
Alright, that's the input from my end.
Sorry for the long reply but I had the urge to clear up some mysteries about the miniMTL protection.
Thus feel free to post the content of this PM to your forum or to other people who feel uncertain about miniMTL's oddities.
regards,
Nobody
~][FGS][Nobody~ wrote:The partially filled in message of your second example can be caused by the attempt to byte-hack miniMTL. That are those 5%.
The player name and the player IP are values, that can be obtained by the server without the cooperation of the client because it's serverside.
However the name of the console class requires the client's cooperation because this information just resides on the client end.
If no such information is returned by the client, it can either be caused by the lag or by a hacker that byte-hacked miniMTL to get it not to answer the server's request.
It's not possible to determine if that behaviour is caused by the 95% chance of lag or by the 5% chance of a haxor.
I can just advice to be attentive but not to rush the fences.
I'm not officially related to the current miniMTL anymore but my security code still resides in the mod.
Thus, don't hesitate to consult me on uncertainties about such cheat found warnings.
Code: Select all
Say: (NKZ)LOSC(13): HHAHAH I Found Aimbot hahhaha !!!
...
Say: (NKZ)LOSC(13): GO TO BLADE he Give the AIMBOT <----- hahah$
...
Say: (NKZ)LOSC(13): And Phantom give the Old Aimbot the last Week
...
Say: (NKZ)LOSC(13): you add List Engine Engine
Say: (NKZ)LOSC(13): and add .Dll
...
Say: (NKZ)LOSC(13): Add the Aimbot.Dll in Winject
...
Say: (NKZ)LOSC(13): oups with my aimbot kill teamkilling xd
That's not its job though really, It's meant to just be a clean simple and secure gametype, not much else.Poor wrote:Maybe ANNA should log more details, such as team switches and teamkills.
Well do you mind me showing your IP publically? This isn't 100% you I suppose. It is from the Middle East and supposedly there is only one other active player from the Middle East apart from you. You are from the Middle East, right? I guess I don't know it is you for sure; this is why I didn't even want to show the evidence in the first place. As I've said: evidence is unreliable.~DJ~ wrote:I have never used an alias ever named as 'agent' or anything like that, can you please provide logs and other stuff publicly as well? Mine atleast? you have stated the following two:
a) me with the alias 'agentxxxx' log
b) blank cheat message log
so can I see both of em'?
Code: Select all
MiniMTL: Possible cheat detected:
MiniMTL: Player Caught: agent009.
MiniMTL: Player Address: 94.xxx.xx.xxx:xxxx.
MiniMTL: Cheat Found: Invalid Console class Detected. ()
Code: Select all
inetnum: 94.xxx.x.x - x
netname: ADSL-LNS3
descr: Jordan Telecom Group (Orange)
descr: for ADSL customers
If that's the penalty for averting cheaters running around with god mode, infinite bio and infinite ammunition, then I can bear that.-Majin- wrote:You are disallowing the good and bad natures of playing the game.
Since I'm realist, it's never been my intension to make it perfect but to make it fair.-Majin- wrote:No matter how hard you try and work on this game, It won't be perfect..
Back in the days, there were more players simply because the game wasn't that old yet and the major metabolic end product that occurred later on, didn't happen yet. I bet things would be better these days, if we had had Nephthys and ANNA 7 years ago already.-Majin- wrote:Remember In 2005 how many players enjoyed playin this game?
Sure it was.. to an extend, but it wasn't the solely condition to play DXMP.-Majin- wrote:What was fun? All the crazy metabolic end product we did together lam bug, water bug, shot time all that sh1t..
That might be true but as I said before.. there's no causal relationship to disallowing bugs... unless your only definition of having fun in DXMP is to exploit bugs etc..-Majin- wrote:Back then there was 30 players in just 2 servers.. Now days cuz of all the rules you can barely find 10 players in one server.
Yes, I would. Since you're just talking of minor bugs that disturb the game, you should get an impression of how a game could be really ruined in order to comprehend why we're doing all the effort with miniMTL/CRD back then and ANNA these days.-Majin- wrote:Bet you I won't..
I partially agree. I can provide the tools/mods to avert cheats. However, I can neither avert the mob to exchange and try cheats, nor can I make the hosters to use the tools/mods to protect their servers. The best protection is obsolete if it's not being used.-Majin- wrote:Obviously you ain't stopping cheaters from Doin their old habits cuz you still supposedly got ppl passing aimbots to eachother.
WÜT, that goes beyond my imagination now.-Majin- wrote:You're an antivirus that has been infected.(not you personally, speaking of dxmp).
Uhh, I assume you didn't get to know ANNA yet.-Majin- wrote:Even thought I haven't been around for about a year now.. I still know what's going on more often than dxmp police do.