-
Re: [RELEASE] RAZcrack Mu Launcher version 3 Final
i know but i don't want to do that anyway thanks
-
Re: [RELEASE] RAZcrack Mu Launcher version 3 Final
man please tell my to MSN OR Messager ;) see Yeah
-
Re: [RELEASE] RAZcrack Mu Launcher version 3 Final
add option and main
exemplo:
_main.exe
-
Re: [RELEASE] RAZcrack Mu Launcher version 3 Final
and one last thing, we need a checker for the updater to be effective, otherwise users will have the trouble of re-downloading the same files all over again, and once the patch size increases, so will the waiting time. it wouldn't be practical without the checker.
an auto-updater with checker will seal the deal ;)
-
Re: [RELEASE] RAZcrack Mu Launcher version 3 Final
-
Re: [RELEASE] RAZcrack Mu Launcher version 3 Final
need some configs for personalization(like background .jpg, update on/off, user can change settings on/off) etc
-
Re: [RELEASE] RAZcrack Mu Launcher version 3 Final
Please share source launcher login MU
-
Re: [RELEASE] RAZcrack Mu Launcher version 3 Final
for ease, how bout the launcher will have a simple tracking file which reads sequence from 1 - infinity then once the update button is pressed, it will read from the client which number the user currently has, as for every complete update the number on the config is changed to a higher one.
for example, in my webserver i have 3 updates in 3 separate folders named 1,2,3 with 3 separate updates (different dates so to speak) then in my client folder where the launcher is, a new config is added named (for example) check.connect or check.update which contains the last number of the successful update patch. so if my config reads 1, it will download contents of folders 2 and 3 only without going back at folder 1, then after downloading, my config data will change to 3 signifying the last successful patch update.
also the launcher has to match the config content to the latest patch folder in the webserver (a cross config can also be an alternative) then once it notes an update it will simply inform the user about the new update (if its manual update) or it can auto update (if ever this function is enabled).
so generally that is the simple and uncomplicated concept of the autoupdate with checker function. hope this gives the launcher creator an idea.
coz if realized, this would solve all our manual patching in which most users get lost on which file is the latest, and what has been changed.
summary
example of what needs to be added.
webserver side:
folder named (in hierarchy) 1 - 3 (depending on # of updates)
1 config (check file - must match check file in client)
client side:
1 config (contains number of last successful patch downloaded)
-if ever webserver config is not equal to client config, an update is either:
announced or indicated (requires launcher modification) or if the autoupdate
config switch exists (1 for auto update, 0 for manual update as proposed)
an auto file transfer is made before the play button is re-activated.
condition : the client config (mentioned above) will only be updated once the
patch transfer is complete.
action: if i have 3 updates, and a client of mine has only 2 updates, it means
in my webserver i have 3 patch folders, and my config reads "3"
the client on the other hand will have "2" in his config to signify that he has the first 2 of my updates but lacks 3.
upon matching 3=>2 a patch update is made. after the update the client config will change to 3 because he has the latest update.
this can be a command added to the launcher, or the patch 3 folder in the webserver will simply contain an updated config with "3" on it.
and so 3=3, no update is made and the user can play.
-
Re: [RELEASE] RAZcrack Mu Launcher version 3 Final
Quote:
Originally Posted by
[hidden]
for ease, how bout the launcher will have a simple tracking file which reads sequence from 1 - infinity then once the update button is pressed, it will read from the client which number the user currently has, as for every complete update the number on the config is changed to a higher one.
for example, in my webserver i have 3 updates in 3 separate folders named 1,2,3 with 3 separate updates (different dates so to speak) then in my client folder where the launcher is, a new config is added named (for example) check.connect or check.update which contains the last number of the successful update patch. so if my config reads 1, it will download contents of folders 2 and 3 only without going back at folder 1, then after downloading, my config data will change to 3 signifying the last successful patch update.
also the launcher has to match the config content to the latest patch folder in the webserver (a cross config can also be an alternative) then once it notes an update it will simply inform the user about the new update (if its manual update) or it can auto update (if ever this function is enabled).
so generally that is the simple and uncomplicated concept of the autoupdate with checker function. hope this gives the launcher creator an idea.
coz if realized, this would solve all our manual patching in which most users get lost on which file is the latest, and what has been changed.
summary
example of what needs to be added.
webserver side:
folder named (in hierarchy) 1 - 3 (depending on # of updates)
1 config (check file - must match check file in client)
client side:
1 config (contains number of last successful patch downloaded)
-if ever webserver config is not equal to client config, an update is either:
announced or indicated (requires launcher modification) or if the autoupdate
config switch exists (1 for auto update, 0 for manual update as proposed)
an auto file transfer is made before the play button is re-activated.
condition : the client config (mentioned above) will only be updated once the
patch transfer is complete.
action: if i have 3 updates, and a client of mine has only 2 updates, it means
in my webserver i have 3 patch folders, and my config reads "3"
the client on the other hand will have "2" in his config to signify that he has the first 2 of my updates but lacks 3.
upon matching 3=>2 a patch update is made. after the update the client config will change to 3 because he has the latest update.
this can be a command added to the launcher, or the patch 3 folder in the webserver will simply contain an updated config with "3" on it.
and so 3=3, no update is made and the user can play.
Nice Idea!
Please Next release!
-
Re: [RELEASE] RAZcrack Mu Launcher version 3 Final
10x, good realease and good job.
-
Re: [RELEASE] RAZcrack Mu Launcher version 3 Final
Quote:
Originally Posted by
[hidden]
for ease, how bout the launcher will have a simple tracking file which reads sequence from 1 - infinity then once the update button is pressed, it will read from the client which number the user currently has, as for every complete update the number on the config is changed to a higher one.
for example, in my webserver i have 3 updates in 3 separate folders named 1,2,3 with 3 separate updates (different dates so to speak) then in my client folder where the launcher is, a new config is added named (for example) check.connect or check.update which contains the last number of the successful update patch. so if my config reads 1, it will download contents of folders 2 and 3 only without going back at folder 1, then after downloading, my config data will change to 3 signifying the last successful patch update.
also the launcher has to match the config content to the latest patch folder in the webserver (a cross config can also be an alternative) then once it notes an update it will simply inform the user about the new update (if its manual update) or it can auto update (if ever this function is enabled).
so generally that is the simple and uncomplicated concept of the autoupdate with checker function. hope this gives the launcher creator an idea.
coz if realized, this would solve all our manual patching in which most users get lost on which file is the latest, and what has been changed.
summary
example of what needs to be added.
webserver side:
folder named (in hierarchy) 1 - 3 (depending on # of updates)
1 config (check file - must match check file in client)
client side:
1 config (contains number of last successful patch downloaded)
-if ever webserver config is not equal to client config, an update is either:
announced or indicated (requires launcher modification) or if the autoupdate
config switch exists (1 for auto update, 0 for manual update as proposed)
an auto file transfer is made before the play button is re-activated.
condition : the client config (mentioned above) will only be updated once the
patch transfer is complete.
action: if i have 3 updates, and a client of mine has only 2 updates, it means
in my webserver i have 3 patch folders, and my config reads "3"
the client on the other hand will have "2" in his config to signify that he has the first 2 of my updates but lacks 3.
upon matching 3=>2 a patch update is made. after the update the client config will change to 3 because he has the latest update.
this can be a command added to the launcher, or the patch 3 folder in the webserver will simply contain an updated config with "3" on it.
and so 3=3, no update is made and the user can play.
Well OK...
But it will take me some time because i am too damn busy with my real life work so be patient...
-
Re: [RELEASE] RAZcrack Mu Launcher version 3 Final
many of my users need Mscomctl.ocx in the sistem32 folder, without it launcher don't work, is there any posebility to integrate it in the launcher(beacause may players play in internet cafes and don't have administrative privileges to pu the file in sistem32)?
-
Re: [RELEASE] RAZcrack Mu Launcher version 3 Final
Quote:
Originally Posted by
shuperh2
many of my users need Mscomctl.ocx in the sistem32 folder, without it launcher don't work, is there any posebility to integrate it in the launcher(beacause may players play in internet cafes and don't have administrative privileges to pu the file in sistem32)?
Yes i know.
But i think that having this file in the same folder with Launcher it's loaded automatically... anyway i will try to include it inside Launcher on next version.
Thank you for noticing.
-
Re: [RELEASE] RAZcrack Mu Launcher version 3 Final
eleos, tora to eida. Em ti, mono enas ellinas 8a ekane tetoia programmatara ! :P
(I was just congratulating him about his program in greek :P)
-
Re: [RELEASE] RAZcrack Mu Launcher version 3 Final
Skyteam with LauncherBuilder and all best tools for Mu had leader a Greek one too....BlurCode
Greece Rulezzzzz :)
-
Re: [RELEASE] RAZcrack Mu Launcher version 3 Final
any news on the autoupdate function ?
-
Re: [RELEASE] RAZcrack Mu Launcher version 3 Final
can u share source file ? please
-
Re: [RELEASE] RAZcrack Mu Launcher version 3 Final
Tell me pls how can add website and update feature from launcher for the port 8080 ?
Tks!!
-
Re: [RELEASE] RAZcrack Mu Launcher version 3 Final
Tell me pls how can I add website and update feature for launcher for the port 8080 ( my musite is configured on 8080 port) ?
Tks !!
Sory for double post I was getting an error with network connection
-
Re: [RELEASE] RAZcrack Mu Launcher version 3 Final
Realy nice launcher, its just too big. That bothers me, make it the size of the skyteam launcher and ill use it.
-
Re: [RELEASE] RAZcrack Mu Launcher version 3 Final
*Sorry for double post, but i get this error when i click update:
http://img68.imageshack.us/img68/421...rerror1ck9.png
Help please.
-
Re: [RELEASE] RAZcrack Mu Launcher version 3 Final
It is a runtime missing ocx
Download it Here
and put it in windows/system32
-
Re: [RELEASE] RAZcrack Mu Launcher version 3 Final
Quote:
Originally Posted by
Sir_Charles
It is a runtime missing ocx
Download it
Here
and put it in windows/system32
Tks man :cloud:
-
Re: [RELEASE] RAZcrack Mu Launcher version 3 Final
let me guess.. doesnt work for 1.03 right?
-
Re: [RELEASE] RAZcrack Mu Launcher version 3 Final
Damn, i cant see my website...
Becouse my website port is 8888, and the launcher don't know how to read that port...