Ban of mods

[MisterFix]

There is a need for a ban of some mods, as it was in ModLoaderMp. It would be nice to have the choice to use it as a white or black list.

 

Is it possible to implement this?

[OvermindDL1]

I thought ModLoaderMP's version of that never worked?

[MisterFix]

You are wrong, it worked perfectly.

[LexManos]

By perfectly you mean really shitty,

Mods can bypass bans in many many ways.

I have it sitting there as a 'TODO' but honestly I dont think its worth the effort. OMFG I randomize my name on sending, I bypassed the ban, omg!

[MisterFix]

No doubt, you can bypass this ban. That's why I ask the white list mode.

[LexManos]

*reports my hack mods name as Forge's name*

Boom bypassed.

You're better off not trusting the client at all and just monitoring them more and being liberal with your bans.

[darkhog]

  On 5/26/2012 at 12:28 PM, LexManos said:

*reports my hack mods name as Forge's name*

 

Don't you think that it would look suspicious if there would be reported two mods with same name? Boom, hack detected.

[OvermindDL1]

I could see a possible way using a white list while disallowing duplicates, maybe, any problems with that idea?

[Jarofdoom]

  On 5/28/2012 at 7:13 PM, darkhog said:

  Quote

*reports my hack mods name as Forge's name*

 

Don't you think that it would look suspicious if there would be reported two mods with same name? Boom, hack detected.

 

Forge's ident code is easily disabled, no?

[LexManos]

Yes, edit the packet to not report any duplicates, bypassed.

[darkhog]

No, checking for duplicates would be done server-side. Basically server would store list of String variables containing all mods for for specified client. So if client would report ForgeAPI two times, it will be detected. Also packets that report nothing (empty strings or null) will be detected also and user will get kicked or banned, depending on policy of server.

[LexManos]

But the client wouldn't report anything two times

as I said, the client is modded, you NEVER trust them.

NEVER trust anything they ever say ever, if they trll you that they are white, they are back. If they tell you they are male, they are female, if they tell you they are 10, they are 5.

CLIENTS LIE!

There is NO way to prevent it.

[OvermindDL1]

  On 5/29/2012 at 10:59 PM, LexManos said:

But the client wouldn't report anything two times

as I said, the client is modded, you NEVER trust them.

NEVER trust anything they ever say ever, if they trll you that they are white, they are back. If they tell you they are male, they are female, if they tell you they are 10, they are 5.

CLIENTS LIE!

There is NO way to prevent it.

 

Hence why the client needs to be a dumb client only sent rendering and interpolation data to it from the server, which handles everything.

[Alex_hawks]

  On 5/30/2012 at 2:49 AM, OvermindDL1 said:

Hence why the client needs to be a dumb client only sent rendering and interpolation data to it from the server, which handles everything.

And you want to remove single player, why?

[darkhog]

  On 6/1/2012 at 9:33 AM, Alex_hawks said:

And you want to remove single player, why?

Can't it be like that (in pseudo code):

if (connectedtoserver) {

be dumb client}

else {

do normally}?

[ScottKillen]

Then the server still has to trust the client...which is really the heart of the matter.

[OvermindDL1]

  On 6/1/2012 at 9:33 AM, Alex_hawks said:

  Quote

Hence why the client needs to be a dumb client only sent rendering and interpolation data to it from the server, which handles everything.

And you want to remove single player, why?

You mean like how MC already is becoming in 1.3?  Have you not seen the snapshots?  It is already like that. 

[DarkGuardsman]

if you really want to remove cheating you would have to have the something scan the client every time it started. Check to make sure every file is in order with a server side cache.