my main concern is that i have numerous files in my system dir called deathball.u.bak, deathball.u.bak.bak etc... same with mapfiles i.e Lowcube, and Cube. How about actually renaming them when released? i.e Cube2 Lowcube2, and the same with texture files. Just make an additional package rather than modifying others, it just causes alot of confusion when a new beta is released, ot final and you get mismatches everywhere, esp when you want to watch some old demos. and i'm sure it won't be much of a problem when releasing betas that you name it deathball180503.u with an .int file.. i'm sure an extra 10k won't hurt ppl, even those poor 28.8 users out there
A few thing to think on when...
Moderators: Jay2k1, DavidM, The_One
A few thing to think on when...
...releasing beta's or finals...
my main concern is that i have numerous files in my system dir called deathball.u.bak, deathball.u.bak.bak etc... same with mapfiles i.e Lowcube, and Cube. How about actually renaming them when released? i.e Cube2 Lowcube2, and the same with texture files. Just make an additional package rather than modifying others, it just causes alot of confusion when a new beta is released, ot final and you get mismatches everywhere, esp when you want to watch some old demos. and i'm sure it won't be much of a problem when releasing betas that you name it deathball180503.u with an .int file.. i'm sure an extra 10k won't hurt ppl, even those poor 28.8 users out there
my main concern is that i have numerous files in my system dir called deathball.u.bak, deathball.u.bak.bak etc... same with mapfiles i.e Lowcube, and Cube. How about actually renaming them when released? i.e Cube2 Lowcube2, and the same with texture files. Just make an additional package rather than modifying others, it just causes alot of confusion when a new beta is released, ot final and you get mismatches everywhere, esp when you want to watch some old demos. and i'm sure it won't be much of a problem when releasing betas that you name it deathball180503.u with an .int file.. i'm sure an extra 10k won't hurt ppl, even those poor 28.8 users out there
- [RoV]WolfMan
- Member
- Posts: 45
- Joined: 01-05-2003 10:51
- Contact:
so why do you keep all those .u files?
the only ones you need is the latest version and perhaps one version which is older....
perhaps im too stupid but it´s not logical to me
the only ones you need is the latest version and perhaps one version which is older....
perhaps im too stupid but it´s not logical to me
Last edited by [RoV]WolfMan on 19-05-2003 13:04, edited 1 time in total.
-
DaJero
Well we won't do that, it's a lot of work to rename everything. Rens2Sea already explained. And besides, you ought to know DeathBall is still under development
. Be prepared to have to update once in a while.
Once 1.7 is done, I'll have a go at writing a program that can manage different versions of DB
Once 1.7 is done, I'll have a go at writing a program that can manage different versions of DB
- [RoV]WolfMan
- Member
- Posts: 45
- Joined: 01-05-2003 10:51
- Contact:
Larc wrote: old version are needed to:
play better (older) versions of maps
hmm i also have older maps but i didnt rename EVERY single map... only the fantastic ones...
plus: tell me how to join servers which have older versions and those with 1.6 or so... you always need to put the old .u files back into the sys directory or rename them to deathball.u if you changed them dont you?
so its not that clever to change them since 1.6 and 1.5 are .exe files which install automatically... that´s no prob..! perhaps 1min and you got em... dont need to rename lots of .us etc.
if i didn't have a seperate shortcut that used the deathball main screen... i'd just delete deathball.u from my computer... then no matter what server i joined it would be correct... though the slow downloads and servers that dont allow it would suck.
i dont suppose you can do code with a variable like deathball<variable_version>.u so that you could update the version and just rebuild to new filenames, without breaking the code.
my simple version switching scheme is to rename files to deathball.u.17b deathball.u.16 deathball.u.13b etc...
then a batch file that copies deathball.u.16 to overwrite deathball.u the only problem with that is you still have to exit ut2k3 before you do it.
if ut2k3 was just smart enough to dl after a version mismatch i wouldnt have as much of a problem... didn't they learn anything from ut? *cough* "de version mismatch" <= delete de.u and join any server regardless of version.
anyway, i'm done.
if you had that you could just update the version define and everyone could be happy.
i dont suppose you can do code with a variable like deathball<variable_version>.u so that you could update the version and just rebuild to new filenames, without breaking the code.
my simple version switching scheme is to rename files to deathball.u.17b deathball.u.16 deathball.u.13b etc...
then a batch file that copies deathball.u.16 to overwrite deathball.u the only problem with that is you still have to exit ut2k3 before you do it.
if ut2k3 was just smart enough to dl after a version mismatch i wouldnt have as much of a problem... didn't they learn anything from ut? *cough* "de version mismatch" <= delete de.u and join any server regardless of version.
anyway, i'm done.
if you had that you could just update the version define and everyone could be happy.