Quote:
Originally Posted by Farius~
I do not like, is more than necessary, this highly charged, has too many useless things a launcher is just to put updates, nothing more.
|
Well if your knowledge ends by just swapping variables on already released launcher then - Yes. But magic starts when you handle option.txt, if you get what i mean.
p.s Mine have also falling snow. Should i remove it?
@
As i said above you can try:
1. Add option to change game resolution directly from the launcher and various game options if you like. Just like in-game.
2. Optional MD5 hash check of the updates to minimize client side problems (make an option for the user to 'untick' if he doesnt want that check (for speed optimization/performance, depending on update sizes and pc specs of the user).
3. I have a nice falling snow to bring some Christmas feeling to the end user. However this might reduce performance.
4. Custom progress bar. My idea was originally animated Trans-up pet instead of all those boring gray progress bars..
5. Simple AntiHack tool? Custom coded service which will install at first launch of the launcher which will check for cheat engine and such programs.
6. I didnt had a chance to check Titan Dekaron but as far i remember they claimed they had background updater where you can play without boring (the game will update itselfs to the latest version on background). So update first important files, rest like textures, anim etc leave to update on background (still need to find time to implement that lol) = less waiting time = more happy users
7. I really dont like launchers with thousands of files. Make it simple as it could be. My Launcher is just 1 file. It have everthing build in. When someone start it for the first time then it creates his configuration file with default values for localhost etc etc. You can make some simple protection (rewrite file) for that file too if someone accidently delete accidently some character/line.
8. Saying all that as far as i remember .NET 4.5 introduced built-in compression mething for files (that existed before too but just for streams etc). More here if you dont want to use commonly used SharpZipLib:
This will kill XP support, just to know if your target is XP too.
9. Some 'nasty' "Reset" button just in case somehow user screwed something (just rewrite your update.dat or whatever you called it to version 1.0.0 or whatever number will be your first update)
I think ive covered most stuff which ive used. Hope it helps.
Cheers
IDEAS for updater
i will make new and smaller soon.
