Furmiga, I found a bug with transparents texturepacks... When i try to login with a transparent pack, the FLock blocks it, but if i'm using Optifine, i can change my texturepack while the game is running, so i can change the default pack to transparent pack... If we find a way to block this Optifine function, the issue is solved ^^

EDIT:

When i run /lc reload, the clients who using xray get kicked... So, to solve the issue, i think its necessary an option to /lc ban the alternative client.

FurmigaHumana,

Você poderia adicionar a opção de armazenar as informações do Cliente em um flatfile ou em MySQL ^"

De resto, o plugin é MUITO bom.

@FurmigaHumana

Yes, i'd be honored!

@FurmigaHumana

Well, I guess here's my problem. Basically, the send function can only ever be used to send client based mods. This is because Forge (client side) will end up sending you a message saying that it doesn't detect the mod. It never reaches the point where FLockClient can do its check.

If you can disable the Forge "mod detection" or whatever its called and just let FLockClient manage it instead (toggleable or permissions based), then im sure the send will work perfectly.

Forge message: http://files.enjin.com/228976/Images/ttt.png

Or, if it can send the mods before Forge can do its check...

What triggers the external download? I wasn't able to get it to download. I made the change in the .txt file and added a direct link, but nothing happens. No errors, no download, etc.

Is there something in the settings file that says to use the external link?

@FurmigaHumana

Sweet! Checking it out now!

I was just saying you could always add the feature of gathering "metrics" to the mod so that you'll know whose using it and how.

"I think most of the people only use it to prevent hacked clients, only the basic feature, I dont have metrics on this one so I couldn't actually tell what is going on."

You could always add it to your longgggg to-do list to make the call home. :D

@FurmigaHumana

Security:
  ## Dictionary, the caracters used to generate the security key, dont worry about sequence!
  Dictionary: '0123456789.+-*,/!@#$%\u00a8&*()_+=-[]{}|\/?:;.>,<^~QWERTYUIOPASDFGHJKLMNBVCXZqwertyuioplkjhgfdsazxcvbnm'

In the case of what you just said, couldn't I just change the randomness of the "dictionary", server-side? Or is that not supposed to be touched?

@FurmigaHumana

Ok, makes sense. Of course if it were to be implemented in vanilla, I guess the only thing that would really work is just the client detection... which should be sufficient. The other really cool stuff that you've put into it such as the automatic send'ing, the gui interface, securing the config files, etc. would not even be needed, so only the secured client is the only thing that I think would even apply.

Well, you're the boss :D and any change (or a lack thereof) is very much appreciated!

Thanks, and keep up the great work!

Also, I see that a lot of people are downloading the mod, but I guess its either working for what they need or just aren't using all its features? (not many are replying other than with initial setup errors). If people would understand exactly what this mod / plugins does, I think it could easily be the most important mod any server would ever use.

Oh, another quick question. If someone were to hack the client, wouldn't all they need is the MD5 hash of minecraft.jar and somehow fake that "packet" or whatever and send that over to the server? Is getting that MD5 hash a simple thing in Java? And does everyone have the capability of finding out what the hash is? Or do you have your own hash generation code? Of course, i'm a server admin... not a programmer :).

I know the client works with Vanilla, but do you have a server version that works with Vanilla server?