Thanks to Cirex.
Cirex built the new directory server straight into the client, and packed the library (.dll) into the executable, so there's only need for one file (infantry.exe) now. He also mentioned the implementation of a security feature (I'm sorry, I don't remember what it was called :()
I also updated the client (graphically), removing the (backup) Directory Server Address text boxes, as they're now useless, along with the Squad Auto-Join Name/password boxes.
As for the installer, it's all fixed and updated. If, and only if, the client installs perfectly (no errors whatsoever!), the installer will proceed with updating their registry with a registry file of my own, replacing/creating a new registry with a basic Mousing layout, and other things, including:
- Skip license agreement automatically (avoid having the user agree to a blank page :?:)
- Basic keyboard configuration to go with their mousing layout
- Advanced options set to some basic things, left advanced options out for the user to choose themselves
- Auto-set detail level to high and rotation points to 64
That's about all I can think of for now.
Unfortunately, while testing the client after finishing it (to avoid any and all bugs!), I was banned instantly on entry. (can someone remove it please?)
Luckily, this means we atleast have some means of protection. Unfortunately, this means it'll make it that much harder to get everyone to update their clients!
As Cirex instructed, we have to:
1) Upload the new client executable (infantry.exe) to the server resources
2) Under [ClientFiles], put in (if it's not already there) 'infantry.exe' as one of the files (and remove infantry.dll!)
3) Get everyone to quit and re-enter, hopefully the client will detect a new client file and update automatically
4) Clients should reset after download completion by themselves, initiating the updated client, where they will be able to logon safely
I suggest doing this change when the servers are empty, and will STAY empty, for a while. This avoids any possible chance of bans and allows room for testing. Make sure that when you test, you're on a new account, not one with powers.
And now, the downloads.
Client file (should only be used for placing on the server, don't distribute this one)
http://ismysick.name/data/data/Infantry/infantry.exe
Installer (this one should be publicly distributed)
http://ismysick.name/data/data/Infantry/infantrysetup.exe
Before releasing them, though, can I get people to test them and make sure they work well? The install process, the registry writing, etc.