DB 2.0 client/server issues UPDATED WITH FIXES!
Posted: 20-04-2004 23:57
Working on a way to run multiple mods with the server using the mod subfolders.
(Pending further testing) : Current workaround is to add deathball to a server in the traditional way or to a ut2004\deathball folder and employ the below workaround to edit the server's ini to make sure that all content is recognized. DO NOT run the server with the -MOD switch. There is no benefit to doing so on the server. If the paths are recognized and there are no conflicts in content, mods can easily co-exist.
_____
Need to find some resolution to servers pushing to clients that have DeathBall installed to the normal folders on servers using the "deathball" folder and vice versa.
(Workaround) : I have tried several different combos and the only time a client was pushed deathball content was when the client has deathball installed to a ut2004\deathball folder and they DID NOT start the game with either deathball.cmd or "ut2004.exe -mod=deathball.." This was the only scenerio where the client did not see the local deathball content. To fix that, you can edit the ut2004.ini file. Inserting the following will add the extra paths and the deathball content will be found.
_____
Unexplainable server crash on startup - Linux and windows. Also - the infamous "Your CD Key is invalid.." problem on clients.
(Fix) After working a bit on trying to solve Agent0007's server crashing, I managed to (i think) duplicate his problem. The immediate crashes stem from what I believe is an incomplete deathball.ini file that was built from a corrupt or non-existant default.ini file in ut2004\system. Anyway, let's fix it.
1.) Get this file and unzip it to your ..\ut2004\system directory. This ensures that you have the right base files that will be used to rebuild your deathball ini files successfully.
2.) In your ..ut2004\Deathball\system directory delete the deathball.ini and deathballuser.ini files - just like the TV guys have been telling everyone to do.
3.) Clients: Start Deathball with the play_deathball.cmd and all will be well.
Server admins: If the multi-mod stuff way above didn't apply and you're running a dedicated deathball-only server, go ahead and use the suggested server startup commandline: "ucc server DB-Cube?game=Deathball.DB_Deathball -MOD=Deathball -ini=deathball.ini ... etc" It should start and all will be well there too.
Game on guys.. Hope these helped.
(Pending further testing) : Current workaround is to add deathball to a server in the traditional way or to a ut2004\deathball folder and employ the below workaround to edit the server's ini to make sure that all content is recognized. DO NOT run the server with the -MOD switch. There is no benefit to doing so on the server. If the paths are recognized and there are no conflicts in content, mods can easily co-exist.
_____
Need to find some resolution to servers pushing to clients that have DeathBall installed to the normal folders on servers using the "deathball" folder and vice versa.
(Workaround) : I have tried several different combos and the only time a client was pushed deathball content was when the client has deathball installed to a ut2004\deathball folder and they DID NOT start the game with either deathball.cmd or "ut2004.exe -mod=deathball.." This was the only scenerio where the client did not see the local deathball content. To fix that, you can edit the ut2004.ini file. Inserting the following will add the extra paths and the deathball content will be found.
Code: Select all
[Core.System]
PurgeCacheDays=30
SavePath=../Save
CachePath=../Cache
CacheExt=.uxx
CacheRecordPath=../System/*.ucl
MusicPath=../Music
SpeechPath=../Speech
Paths=../System/*.u
Paths=../Maps/*.ut2
Paths=../Textures/*.utx
Paths=../Sounds/*.uax
Paths=../Music/*.umx
Paths=../StaticMeshes/*.usx
Paths=../Animations/*.ukx
Paths=../Saves/*.uvx
;====== inserted section begins here
Paths=../Deathball/System/*.u
Paths=../Deathball/Maps/*.ut2
Paths=../Deathball/Music/*.ogg
Paths=../Deathball/Sounds/*.uax
Paths=../Deathball/StaticMeshes/*.usx
Paths=../Deathball/Textures/*.utx
;====== inserted section ends here
;ut2004.ini continues....
_____
Unexplainable server crash on startup - Linux and windows. Also - the infamous "Your CD Key is invalid.." problem on clients.
(Fix) After working a bit on trying to solve Agent0007's server crashing, I managed to (i think) duplicate his problem. The immediate crashes stem from what I believe is an incomplete deathball.ini file that was built from a corrupt or non-existant default.ini file in ut2004\system. Anyway, let's fix it.
1.) Get this file and unzip it to your ..\ut2004\system directory. This ensures that you have the right base files that will be used to rebuild your deathball ini files successfully.
2.) In your ..ut2004\Deathball\system directory delete the deathball.ini and deathballuser.ini files - just like the TV guys have been telling everyone to do.
3.) Clients: Start Deathball with the play_deathball.cmd and all will be well.
Server admins: If the multi-mod stuff way above didn't apply and you're running a dedicated deathball-only server, go ahead and use the suggested server startup commandline: "ucc server DB-Cube?game=Deathball.DB_Deathball -MOD=Deathball -ini=deathball.ini ... etc" It should start and all will be well there too.
Game on guys.. Hope these helped.