From: Ludwig N. <lud...@gm...> - 2004-05-08 17:27:24
|
Ruediger Meier wrote: > Ive notived that I subscribed to developer-list, but Iam sure that I had= =20 > selected the user-list somewhere on you homepage. Hope it doesnt matter. XQF seems to not have much users, at least there is no traffic on the users list ;-) > On Saturday 08 May 2004 15:00, Ludwig Nussel wrote: > > Ah, ok. That's the same buggy behavior as in q3a. I'll change the > > code to use the q3a workarounds for all q3 engine games. >=20 > Thx, it would be nice:) > But plz think about launch-scripts which are able to use the current=20 > server-info (see below). >=20 > > > [BTW I would prefer it to use an own launch-script that depends on > > > server-info (or is it possible yet?) In this case for instance someth= ing > > >=20 > > If you right click on a server and choose properties you get a drop > > down box where you can specify a custom config for that server. This > > option is available for q3a but not for RTCW since noone bothered to > > complain about it until now :-) I'll see how hard it is to fix that > > as well. >=20 > Well its a good thing. I like the additional q3a-options menu (for instan= ce to=20 > change memory settings) too. I added it when some mods started to need more than the default memory but I never got any feedback about it. I can't judge whether it makes sense to have it for other games as well. The preset defaults also look ridiculous for today's machines :-) > I think it must be very hard for you to have the knowledge about all inte= rnals=20 > of the different games. But I noticed that its aleready possible to use a= =20 > prelaunch-script that starts when I double-click a server. My suggestion = for=20 > you: >=20 > 1. It should be possible to define an own prelaunch-script for each game > (ok its aleready possible if I type it in the "commandline"-field of=20 > game-configuration - but more important would be the next) >=20 > 2. XQF should export all server-info to this script in form of shell-vari= ables=20 > like: > - $HOSTNAME > - $SERVER_IP > - $GAME > - $MAP > - etc >=20 > so everybody could use its own launch-scripts with all possibillities of = the=20 > text-based shell-commands or IF-THEN-ELSE statements. (For example it cou= ld=20 > automatically start a teampspeak-connection to a ts-server which depends = on=20 > $HOSTNAME) > I think these sugestions shouldnt be difficult to realize for you - pro= bably=20 > XQF works intern in this way. Sure, if people tell me which informations make sense as environment variable I can export it but it would be stupid to just dump _everything_ into the environment. 0.9.14 already exports XQF_SERVER_ANTICHEAT this way. > The advantage would be that you developers dont need to know all things a= bout=20 > a special game or about all crazy needings of some hardcore-gamers. As y= ou=20 > can see I could have solved my "fs_game problem" very easy without askin= g=20 > you to change the source-code. =2E. and noone would have noticed that there is a bug. XQF is free software so if there is something missing you can fix it directly in C and send a patch to this list rather than writing horrible shellscripts to work around it. However, I also think that stuff like TeamSpeak or Cheating Death doesn't really belong into XQF so we need to find some balance here. This list is a good place to discuss it. cu Ludwig --=20 (o_ Lud...@gm... //\ PGP Key ID: FF8135CE V_/_ ICQ: 52166811 |