| 00:07.15 | *** join/#bzflag nadine (n=5412873a@zeebrothers.net) |
| 00:08.01 | *** join/#bzflag nadine (n=5412873a@zeebrothers.net) |
| 00:08.05 | *** part/#bzflag nadine (n=5412873a@zeebrothers.net) |
| 00:09.56 | eXtreme | A question |
| 00:10.08 | eXtreme | Is it possible to bind bzadmin to a specific IP? |
| 00:11.01 | blast007 | bind? |
| 00:11.32 | eXtreme | by that I mean choose the "interface" |
| 00:11.45 | eXtreme | actually never mind |
| 00:11.51 | blast007 | hehe |
| 00:11.53 | eXtreme | it's rather pointless anyway |
| 00:11.56 | eXtreme | just ignore me |
| 00:12.51 | trepan | bzfs -i |
| 00:15.43 | brlcad | Thumper_: it's not gone.. it's just intermittent :) |
| 00:17.45 | brlcad | 100 packets transmitted, 96 packets received, 4% packet loss |
| 00:48.30 | *** join/#bzflag wizart (n=wizart@dslb-084-058-148-208.pools.arcor-ip.net) |
| 00:57.51 | *** join/#bzflag randomparticle (n=502ab4be@zeebrothers.net) |
| 01:15.34 | *** join/#bzflag blast007 (n=blast@dsl-134.madison.chorus.net) |
| 01:19.14 | *** join/#bzflag Blue_Eyes (n=Blue@host253-221.pool870.interbusiness.it) |
| 01:21.37 | *** join/#bzflag blast007_ (i=1000@24-196-92-143.dhcp.mdsn.wi.charter.com) |
| 01:23.01 | *** join/#bzflag wegstar (n=wegstar@adsl-69-109-229-143.dsl.pltn13.pacbell.net) |
| 01:28.57 | *** join/#bzflag wegstar (n=wegstar@adsl-69-109-229-143.dsl.pltn13.pacbell.net) |
| 01:29.40 | *** join/#bzflag wegstar (n=wegstar@adsl-69-109-229-143.dsl.pltn13.pacbell.net) |
| 01:34.29 | *** join/#bzflag wegstar (n=wegstar@adsl-69-109-229-143.dsl.pltn13.pacbell.net) |
| 01:36.49 | *** join/#bzflag wegstar (n=wegstar@allegro/user/wegstar) |
| 01:39.20 | *** join/#bzflag wegstar762 (n=wegstar@adsl-69-109-229-143.dsl.pltn13.pacbell.net) |
| 01:40.26 | *** join/#bzflag wegstar344 (n=wegstar@adsl-69-109-229-143.dsl.pltn13.pacbell.net) |
| 01:40.50 | trepan | wegstar344: done yet? |
| 01:41.13 | eXtreme | heh |
| 01:42.04 | wegstar | :) just testing out an irc google homepage module |
| 01:42.45 | trepan | in a private channel? :) |
| 01:43.34 | wegstar | bleh.. fine.. I'll just join #bzflag manually |
| 01:43.52 | wegstar | Or else it would be joining #bzflag everytime I visit the google homepage ;) |
| 01:43.58 | brlcad | my log will appreciate it |
| 01:44.50 | trepan | was that a threat? |
| 01:44.58 | *** join/#bzflag wegstar (n=wegstar@allegro/user/wegstar) |
| 01:46.14 | trepan | the sartorial change becomes you |
| 01:48.01 | brlcad | heh |
| 02:00.59 | *** join/#bzflag JBdiGriz (n=JBdiGriz@adsl-67-125-169-155.dsl.sndg02.pacbell.net) |
| 02:01.00 | *** mode/#bzflag [+o JBdiGriz] by ChanServ |
| 02:10.13 | trepan | with 'color 0 0 0 0', noradar, and noshadow, there's no extra harm that should come from it |
| 02:10.13 | *** join/#bzflag TD-Linux (n=TD-Linux@24-159-197-101.dhcp.roch.mn.charter.com) |
| 02:33.07 | *** join/#bzflag lan56 (i=lan56@user-vcauubf.dsl.mindspring.com) |
| 03:01.15 | *** join/#bzflag linuxlord (n=cf057355@webchat.bzflag.bz) |
| 03:01.44 | linuxlord | how do you make a new server |
| 03:03.12 | trepan | ~bzfs |
| 03:03.14 | ibot | rumour has it, bzfs is the BZflag server, you need: -publicaddr server.name.com:5154 *and* -public " come play here" must be set in your bzfs.conf, *also* open the port (5154 in this case) in your firewall/router *also* see http://www.bzflag.org/wiki/CreatingAServer, or see http://my.bzflag.org/bb/viewtopic.php?t=2915 |
| 03:03.49 | linuxlord | I did all that though and It says file not found |
| 03:04.36 | linuxlord | here is what it says: C:\Documents and Settings\Administrator\My Documents\sample.conf: error: could n |
| 03:05.28 | linuxlord | ot find bzflag configureation file |
| 03:11.20 | *** join/#bzflag amcnabb (n=amcnabb@c-67-169-251-185.hsd1.ut.comcast.net) |
| 04:00.12 | *** join/#bzflag lan56 (i=lan56@user-vcauubf.dsl.mindspring.com) |
| 04:04.26 | *** join/#bzflag wegstar (n=wegstar@allegro/user/wegstar) |
| 04:31.13 | CIA-3 | BZFlag: 03lan56 * 10bzflag/Dev-C++/bzfs.dev: output executable to ../src/bzfs |
| 05:15.15 | *** join/#bzflag L4m3r (n=Chris@s122-55.resnet.ucla.edu) |
| 05:15.49 | *** part/#bzflag L4m3r (n=Chris@s122-55.resnet.ucla.edu) |
| 05:53.07 | *** join/#bzflag CBG (n=CBG@cpc4-stme1-0-0-cust103.cdif.cable.ntl.com) |
| 06:11.18 | *** join/#bzflag Pimpinella (n=frank@213.9.108.240) |
| 06:14.05 | *** join/#bzflag JBdiGriz (n=JBdiGriz@adsl-67-125-169-155.dsl.sndg02.pacbell.net) |
| 06:14.05 | *** mode/#bzflag [+o JBdiGriz] by ChanServ |
| 07:06.15 | *** join/#bzflag _Manu_ (n=_jujibo@98.Red-80-36-59.staticIP.rima-tde.net) |
| 07:06.16 | *** mode/#bzflag [+v _Manu_] by ChanServ |
| 07:06.51 | *** join/#bzflag Pommes (n=fx@p548B0A66.dip0.t-ipconnect.de) |
| 07:31.34 | *** join/#bzflag Blue_Eyes (n=Blue@treebupf.inet.it) |
| 07:57.37 | *** join/#bzflag kyelewis` (n=kyelewis@freematrix/staff/kyelewis) |
| 08:19.42 | *** join/#bzflag awelux__ (n=wizart@dslb-084-058-175-245.pools.arcor-ip.net) |
| 09:02.41 | *** join/#bzflag ToughShooter (n=ts@p54B01204.dip0.t-ipconnect.de) |
| 09:44.43 | *** join/#bzflag SportChick (n=SportChi@ca-redbch-cuda1-c3b-a-40.stmnca.adelphia.net) |
| 09:44.43 | *** mode/#bzflag [+v SportChick] by ChanServ |
| 10:02.12 | *** join/#bzflag bz49 (n=55122d32@webchat.bzflag.bz) |
| 10:45.19 | *** join/#bzflag |zongo| (n=zongo@dhcp24-214.math.uni-bielefeld.de) |
| 11:09.00 | *** part/#bzflag ToughShooter (n=ts@p54B01204.dip0.t-ipconnect.de) |
| 11:46.27 | *** join/#bzflag mmu_man (i=revol@vaf26-2-82-244-111-82.fbx.proxad.net) |
| 13:52.37 | *** join/#bzflag Guest755 (n=0fcba97e@zain.pc-clever.com) |
| 14:15.02 | *** join/#bzflag bz27 (n=810c299b@webchat.bzflag.bz) |
| 14:41.22 | *** join/#bzflag JBdiGriz (n=JBdiGriz@adsl-67-125-169-155.dsl.sndg02.pacbell.net) |
| 14:41.22 | *** mode/#bzflag [+o JBdiGriz] by ChanServ |
| 15:18.35 | *** join/#bzflag ToughShooter (n=ts@p54B0317C.dip0.t-ipconnect.de) |
| 15:37.51 | *** join/#bzflag bz02 (n=406bba16@webchat.bzflag.bz) |
| 15:39.23 | *** join/#bzflag bz12 (n=406bba16@webchat.bzflag.bz) |
| 15:48.09 | *** join/#bzflag Mr_Molez (n=admin@ACBDB0F3.ipt.aol.com) |
| 16:00.06 | *** join/#bzflag matt1100100 (n=d0e64489@webchat.bzflag.bz) |
| 16:00.19 | matt1100100 | hey hey hey |
| 16:00.34 | matt1100100 | anybody play runescape |
| 16:01.23 | matt1100100 | hello |
| 16:01.56 | matt1100100 | coty |
| 16:02.30 | blast007 | Car Of The Year? ;) |
| 16:07.55 | *** join/#bzflag wizatcomputer (n=wizatcom@pool-71-254-29-175.clppva.east.verizon.net) |
| 16:23.49 | *** join/#bzflag |zongo| (n=zongo@dhcp24-214.math.uni-bielefeld.de) |
| 16:32.07 | *** join/#bzflag JBdiGriz (n=jbdigriz@12.147.16.2) |
| 16:32.07 | *** mode/#bzflag [+o JBdiGriz] by ChanServ |
| 16:38.06 | *** join/#bzflag SportyGal (i=DonnaCra@exchange.kingsharbor.org) |
| 16:38.44 | *** mode/#bzflag [+v SportyGal] by ChanServ |
| 16:56.00 | *** part/#bzflag Mr_Molez (n=admin@ACBDB0F3.ipt.aol.com) |
| 16:57.07 | *** join/#bzflag Mr_Molez (n=admin@ACBDB0F3.ipt.aol.com) |
| 16:58.29 | *** join/#bzflag Birdie (n=Birdie__@d54C34DE9.access.telenet.be) |
| 17:05.09 | *** join/#bzflag JBGood (i=Johnq@128.237.243.63) |
| 17:09.02 | *** join/#bzflag amcnabb (n=amcnabb@128.187.180.70) |
| 17:13.50 | brlcad | I finished a tool I was working on that aggregates the sf.net project tracker data according to various criteria and ran it on BZFlag |
| 17:14.58 | brlcad | for those of you that dig the whole project management reporting, tracking, and accounting prevalent in software configuration management, might be of interest |
| 17:15.35 | brlcad | the tools dumps out a massive csv, which can then be formatted up in your favorite spreadsheet |
| 17:15.38 | brlcad | http://bzflag.bz/bztrackers-20060322.pdf |
| 17:27.02 | *** join/#bzflag jbauman (i=Johnq@128.237.243.63) |
| 17:29.20 | brlcad | shows some clear anamolies in the trackers, like how there shouldn't be world files that have high "priority".. meaningless |
| 17:34.28 | brlcad | and the vast count of items that nobody is willing to put their name against to handle them.. especially useful patches :/ |
| 17:35.56 | CBG | brlcad: looks very nice |
| 17:44.05 | *** join/#bzflag Polar (n=csuead@compsoc.sunion.warwick.ac.uk) |
| 17:51.58 | uso | is there an option or a setting to automatically shutdown the server if the countdown is finished? |
| 17:52.23 | uso | like it is used on silvercat for map rotation |
| 17:52.53 | menotume | -g |
| 17:53.34 | menotume | fomr the man page: -g Quit after serving one game. |
| 17:54.11 | uso | have found it ... how could i have overlooked that ... |
| 17:54.15 | uso | thanks |
| 17:54.36 | uso | i searched for shutdown, not for quit ;) |
| 17:54.36 | menotume | np |
| 17:55.47 | uso | next question, is there a possibility to read environment variables in the config file? or to include another file in the config file? |
| 17:56.18 | menotume | with a script, yes |
| 17:57.10 | uso | rewrite the config file before starting the server, is that what you mean? |
| 17:57.20 | menotume | sort of |
| 17:57.22 | menotume | linux ? |
| 17:57.52 | uso | yes, having sed or perl to substitute it |
| 17:58.36 | menotume | ahh, hold on a sec |
| 17:58.37 | uso | i wanted to avoid the whole file to be rewritten ... |
| 17:59.42 | uso | btw i've changed the autoTeam behaviour for 1 vs 1 plus a third player, coasts me more than an hour to understand the logic ;) |
| 18:01.01 | menotume | look at: http://meno.zapto.org/start |
| 18:01.24 | menotume | ooops |
| 18:01.36 | menotume | http://meno.zapto.org/bzcaps/start |
| 18:01.47 | menotume | and http://meno.zapto.org/bzcaps/common.config |
| 18:01.59 | menotume | that's what I use for an easy colution |
| 18:02.13 | menotume | the 'start' script contains alll the config info |
| 18:03.04 | menotume | ahh, and ... http://meno.zapto.org/bzcaps/runbzfs |
| 18:03.05 | menotume | :) |
| 18:03.16 | uso | :) |
| 18:03.28 | menotume | so, some stuff is passed as env vars |
| 18:03.42 | menotume | the main config is echoed to the runbzfs script |
| 18:03.45 | uso | i understand the mechanism, is about what i was afraid of :) |
| 18:04.09 | menotume | works for me, so i can have lots of different 'start' scripts with diff configs |
| 18:05.20 | uso | you have a full shell environment in your chroot? or not chroot'ed? |
| 18:05.28 | menotume | and no perl, just bash (orange) |
| 18:05.34 | menotume | not chrooted |
| 18:05.56 | menotume | it's my machine here - i don't run the server(s) often |
| 18:06.31 | menotume | and, only one instance of bzfs (else the kills would have to be enhanced) |
| 18:06.57 | uso | yes, perl was only thought for pattern matching to replace place holders, but piping it together looks more elegant |
| 18:07.09 | menotume | easier for me |
| 18:07.28 | *** join/#bzflag JBGood (i=Johnq@128.237.243.63) |
| 18:09.32 | uso | and probably last question :) ... i vague remember of a jitterwarn / jitterdrop option, is it only in HEAD? 2.0_branch gives me an error if i use it |
| 18:09.42 | menotume | dunno |
| 18:10.03 | uso | ok, thanks again |
| 18:10.11 | menotume | have fun :) |
| 18:10.42 | uso | later, can't waste bandwidth at the moment ;) |
| 18:12.13 | ToughShooter | uso: the jitterwarn & drop thingy is only in CVS HEAD |
| 18:15.47 | uso | hmm, maybe i look at it later when i decide to make a real server, not only a temporarily one to play around, thanks |
| 18:22.21 | *** join/#bzflag JBGood25 (i=Johnq@128.237.243.63) |
| 18:28.22 | *** join/#bzflag CBG (n=CBG@cpc4-stme1-0-0-cust103.cdif.cable.ntl.com) |
| 18:33.36 | *** join/#bzflag jbauman (i=Johnq@128.237.243.63) |
| 18:48.35 | *** join/#bzflag blast007` (n=blast@24-196-92-143.dhcp.mdsn.wi.charter.com) |
| 19:45.49 | *** join/#bzflag menotume (n=meno@pdpc/supporter/active/menotume) |
| 19:45.50 | *** mode/#bzflag [+v menotume] by ChanServ |
| 19:50.24 | *** join/#bzflag BenUrban (n=benurban@unaffiliated/benurban) |
| 19:54.29 | *** join/#bzflag brad2901 (n=brad@unaffiliated/brad2901) |
| 19:54.30 | *** join/#bzflag Tupone (n=Tupone@pdpc/supporter/active/Tupone) |
| 19:54.30 | *** mode/#bzflag [+v Tupone] by ChanServ |
| 20:10.23 | *** join/#bzflag brad2901 (n=brad@unaffiliated/brad2901) |
| 20:21.00 | *** join/#bzflag Blue_Eyes (n=Blue@host253-221.pool870.interbusiness.it) |
| 20:27.40 | brlcad | CBG: thanks |
| 20:28.15 | brlcad | uso: changed it how so? |
| 20:28.21 | *** join/#bzflag Mr_Molez (n=admin@ACD1307E.ipt.aol.com) |
| 20:28.59 | uso | changed what? the autoteam? |
| 20:28.59 | brlcad | there was discussion a long time ago about the automatic team join algorithm |
| 20:29.36 | brlcad | yeah, you said you changed it.. in what way? |
| 20:29.42 | uso | yeah, i know, and maybe two guys three meanings about that :) |
| 20:30.04 | uso | i was unsure between two variants |
| 20:30.35 | uso | to fill the teams 1-1 1-1-1 1-1-1-1 2-1-1-1 ... |
| 20:30.49 | brlcad | that's how it originally worked |
| 20:31.16 | uso | or to leave the decision to either join a team as the second or to join a new team if it's 1 vs 1 and a third joins |
| 20:31.50 | uso | have done the last, but not tested so far |
| 20:32.12 | uso | yes, but on gu 5154 there are often only a few ppl late in the night |
| 20:32.38 | brlcad | it's basically depth first filling, breadth first filling, or some hybrid based on how many teams/players are already joined |
| 20:32.47 | uso | and most people i talked with would prefer a 1-1-1 instead of the 2-1 now |
| 20:33.05 | brlcad | personally, I think breadth first is how it should be since I've created a server with that many teams |
| 20:33.30 | *** join/#bzflag Bagheera (n=greg@pdpc/supporter/bronze/grumbler) |
| 20:33.35 | brlcad | it was changed to be hybrid that favors depth first |
| 20:33.52 | uso | yes, i think too, but doesn't matter that much with more players |
| 20:34.38 | brlcad | the difference mainly being that depth-first does attempt to encourage teamplay more |
| 20:34.52 | brlcad | since it minimizes teams slightly in favor of bigger teams |
| 20:34.57 | brlcad | at least that's the theory |
| 20:35.11 | uso | yes, but requires at least 4 player to work ;) |
| 20:35.21 | orange | you could certainly argue creating 1-person teams without other teams at least at 2 doesn't make sense |
| 20:35.52 | brlcad | quite true, it's overly imbalanced against the loner |
| 20:36.23 | uso | probably depends on the map too |
| 20:36.27 | brlcad | whereas with at least 3 or 4 on the map and there's other fodder to distract/consider |
| 20:37.00 | uso | at gu it's not a big problem if you have 2 teams with 2 ppl and a loner |
| 20:37.07 | brlcad | so if it was 1-1-1 with four teams specified, there's not much difference between 1-1-2 and 1-1-1-1 |
| 20:37.09 | uso | or even 2 teams with 3 ppl |
| 20:37.40 | brlcad | whereas a big difference between 1-1-1 and 1-2 |
| 20:37.49 | uso | exactly |
| 20:38.16 | brlcad | so you have a patch to commit right? :) |
| 20:38.34 | uso | hehe, i commented out one line :) |
| 20:38.35 | orange | you could fill teams to two people until all existing teams are at 2, then add a new team of 1 |
| 20:38.39 | orange | then repeat |
| 20:38.42 | uso | and not tested so far .. |
| 20:38.55 | orange | 1-1, 1-2, 2-2, 2-2-1, 2-2-2, 2-2-2-1, 2-2-2-2, etc. |
| 20:39.00 | uso | most work was to understand C++ first |
| 20:39.07 | uso | and logic after that :) |
| 20:39.10 | brlcad | orange: that's almost what it does iirc |
| 20:39.20 | brlcad | it's the 1-2 imbalance that makes for trouble |
| 20:39.21 | orange | brlcad: cool, then I like it :-) |
| 20:39.31 | brlcad | i mean, that's what it does now iirc |
| 20:39.35 | Bagheera | so do i |
| 20:39.48 | brlcad | ooh, Bagheera speaks.. :) |
| 20:39.55 | Bagheera | heh |
| 20:39.57 | brlcad | baggy hasn't talked in ages |
| 20:40.07 | Bagheera | just keeping the nick alive |
| 20:40.15 | brlcad | :) |
| 20:40.41 | Bagheera | ...and since i am running off an iMac now, it seemed appropiate |
| 20:40.52 | brlcad | such a different visual image the two nicks conjure up |
| 20:41.52 | Bagheera | hmm, never thought of it like that.... |
| 20:41.54 | brlcad | orange: how about 1-1 1-1-1 1-1-2 1-2-2 2-2-2 2-2-2-1 2-2-2-2 etc? |
| 20:42.37 | orange | brlcad: that works too |
| 20:42.43 | Bagheera | looks better than before |
| 20:42.44 | orange | if your goal is to prevent 2-1 |
| 20:42.48 | brlcad | right |
| 20:43.13 | orange | I'm not even sure how you'd describe that rule :-) |
| 20:44.57 | Bagheera | "no 2 on 1 bully play" |
| 20:44.59 | brlcad | iirc, tupone has a wiki for th current algorithm |
| 20:45.08 | brlcad | yeah.. http://bzflag.org/wiki/AutoTeam |
| 20:46.48 | brlcad | basically, the algorithm balances existing filled teams before filling up new ones |
| 20:48.04 | brlcad | i still like/prefer the "assigned to the weakest team" original implementation, but I'm easy to please ;) |
| 20:48.17 | uso | why not leaving it to the players if they prefer to fill up existing teams or start a new one if there are still empty teams? |
| 20:48.59 | Tupone | brlcad: now is ... assigned to the weakest team |
| 20:49.02 | brlcad | uso: players can always pick their team .. the question is the behavior on automatic |
| 20:49.04 | uso | maybe a 3rd autoteam mode :) ... no autoteam, "soft" and "hard" autoteam ;) |
| 20:49.14 | Tupone | 0 players is not a team |
| 20:49.34 | uso | no, i mean they either decide to open a new team or to go to the weakest team |
| 20:49.50 | Chestal | is there a difference between client and server side autoteam? |
| 20:49.55 | Bagheera | you want to give the clients a choice |
| 20:50.03 | Tupone | Chestal: no client side autoteam |
| 20:50.24 | *** join/#bzflag TD-Linux (n=TD-Linux@24-159-197-101.dhcp.roch.mn.charter.com) |
| 20:50.27 | Tupone | choice is always made server side |
| 20:50.32 | brlcad | Tupone: that's one way of thinking about it.. |
| 20:50.41 | uso | you still have to prefer an autoteam mode if a player joins with mode auto |
| 20:50.42 | brlcad | the 0 players is not a team bit, that is |
| 20:51.13 | Tupone | I prefer 2-2 against 1-1-1-1 |
| 20:51.20 | uso | but if a plyer joins with a teamcolor he should be able to join either one of the weakest teams or an empty team |
| 20:51.36 | Chestal | Tupone: ok, I mean difference between server auto and client joining as red, or server no auto and client joining as automatic |
| 20:52.10 | brlcad | Chestal: I don't think there is a difference any more |
| 20:52.25 | Tupone | if client join red and red is one of the team that server could choose, server respect player wish |
| 20:52.39 | Tupone | otherwise is random |
| 20:53.01 | Mr_Molez | wont this cause problems for HTF games. Or can you choose to use it ? |
| 20:53.04 | brlcad | Tupone: what about 2-1 vs 1-1-1 .. that's the one that seems to cause the problem? |
| 20:53.08 | brlcad | s/?// |
| 20:53.10 | uso | sure? thought if team is not available you get an error |
| 20:53.25 | brlcad | basically just filling up from 3 instead of 2 |
| 20:53.29 | uso | if server is no auto |
| 20:53.38 | brlcad | since 2 vs 1 on an empty team is pretty imbalanced |
| 20:53.58 | Tupone | I understand that ... but too hard to make 2-2 then or 2-2-2 |
| 20:54.35 | Tupone | and I can fight against 2 sometime |
| 20:55.08 | Tupone | it happened and they have to work hard to kill me :) |
| 20:56.19 | brlcad | you could still prefer to drop down from 2-1-1 to 2-1 to 2-2 if a player leaves for example |
| 20:56.36 | brlcad | it's only when building up newly joining, to not join and create an imbalance |
| 20:56.40 | Tupone | I know that now, with the current rule we can play even if just few players |
| 20:57.49 | Tupone | however if you are 4 player 2-1-1 one aloe leave and join, and back to 2-2 so it could be ok |
| 20:58.12 | brlcad | yeah |
| 20:58.26 | Tupone | hope you get :) my english get worst :( |
| 20:58.30 | brlcad | it would still encourage on rebuilding from a depart |
| 20:58.42 | uso | anyway, i don't wanted to open this discussion again ... was only a remark to meno as he complained about a not working 1-1-1 join last night :) |
| 20:58.51 | brlcad | just when building up that initial 3 player, it would try to keep a balance |
| 20:59.10 | Tupone | brlcad: OO , just as reminder :) |
| 20:59.10 | brlcad | basically.. it would _always_ try to keep a balance if it was changed to do 1-1-1 |
| 20:59.31 | brlcad | ah, thanks |
| 20:59.36 | brlcad | heh.. took me a sec |
| 20:59.56 | Tupone | great |
| 20:59.58 | brlcad | Tupone: you saw the tracker sheet? |
| 21:00.07 | Tupone | nope |
| 21:00.11 | Tupone | pfd ? |
| 21:00.13 | Tupone | pdf ? |
| 21:00.15 | orange | team reassignment would be a 'killer feature' for bzflag fair play :-) |
| 21:00.39 | brlcad | http://bzflag.org/bztrackers-20060322.pdf |
| 21:00.43 | Tupone | orange: I don't like automatic reassignment when playing |
| 21:01.08 | brlcad | the current gui notification makes that impractical without changing other things first |
| 21:01.15 | orange | Tupone: it would have to have some kind of notification, like a dialog box that says "you have been automatically reassigned to the red team" |
| 21:01.18 | brlcad | like having assignment queues |
| 21:01.25 | brlcad | s/assignment/waiting/ |
| 21:01.36 | orange | and a dismissable dialog box notification would be another HUGE win |
| 21:01.39 | Tupone | I prefer to be put on a queue |
| 21:01.48 | orange | "You have been kicked for XXXXXX, press OK to acknowledge" |
| 21:02.07 | Tupone | s/queue/parking area/ |
| 21:02.16 | uso | or cancel to play further ;) |
| 21:02.18 | orange | "You have received a message from an admin: blah blah blah\nPress OK to acknowledge" |
| 21:02.19 | brlcad | that data from the pdf was auto-snarfed from the website, set the program to cull closed entries (there are about 700 closed tracker items, about 500 open) |
| 21:02.42 | Tupone | I cannot read that. SF issues? |
| 21:02.45 | brlcad | and does include items closed within the last 45 days |
| 21:02.50 | orange | /dialog_msg brlcad please stop killing teammates or you will be kicked |
| 21:02.55 | brlcad | er, wrong url, sorry |
| 21:03.02 | brlcad | http://bzflag.bz/bztrackers-20060322.pdf |
| 21:03.31 | Tupone | I need to fix pdf :) |
| 21:03.42 | brlcad | ahh, that's right.. |
| 21:03.43 | brlcad | heh |
| 21:03.45 | Tupone | viewer |
| 21:04.01 | blast007 | brlcad: fyi, there is two Closed entries on the last page of the PDF :) |
| 21:04.23 | brlcad | blast007: yeah it includes "recently closed" items, in this case closed within 45 days |
| 21:04.28 | blast007 | ah, ok |
| 21:04.30 | brlcad | configurable |
| 21:04.35 | blast007 | just wondering it if was a bug ;) |
| 21:04.48 | brlcad | so if you were presenting, or having monthly meetings, etc.. you can see the work that was actually completed |
| 21:05.00 | brlcad | i didn't do it for bz, but thought it was interesting to see the results :) |
| 21:09.09 | brlcad | hehe |
| 21:26.51 | Thumper_ | SportyGal: sounds smelly ;) |
| 21:27.09 | SportyGal | Thumper_: ack! true! |
| 21:45.31 | *** join/#bzflag JeffM2501 (n=JeffM@pdpc/supporter/sustaining/JeffM2501) |
| 21:45.32 | *** mode/#bzflag [+o JeffM2501] by ChanServ |
| 21:47.52 | CBG | hey JeffM2501... http://my.bzflag.org/bb/viewtopic.php?t=7421 |
| 21:48.56 | JeffM2501 | k |
| 22:03.21 | *** join/#bzflag jbauman (i=Johnq@JBAUMAN.RES.cmu.edu) |
| 22:20.16 | *** join/#bzflag JeffM_ (n=JeffM@pool-71-109-230-30.lsanca.dsl-w.verizon.net) |
| 22:24.32 | *** join/#bzflag wizart (n=wizart@dslb-084-058-175-245.pools.arcor-ip.net) |
| 22:34.13 | *** join/#bzflag JeffM2501 (n=JeffM@pdpc/supporter/sustaining/JeffM2501) |
| 22:34.13 | *** mode/#bzflag [+o JeffM2501] by ChanServ |
| 22:38.31 | *** join/#bzflag mmu_man (i=revol@vaf26-2-82-244-111-82.fbx.proxad.net) |
| 22:41.42 | *** join/#bzflag brad2901 (n=brad@unaffiliated/brad2901) |
| 22:48.41 | *** join/#bzflag triclops (n=triclops@203-217-88-218.dyn.iinet.net.au) |
| 22:54.58 | *** join/#bzflag quantumdot (n=Juan@VA1-1G-u-1254.mc.onolab.com) |
| 22:56.51 | *** part/#bzflag quantumdot (n=Juan@VA1-1G-u-1254.mc.onolab.com) |
| 23:01.35 | *** join/#bzflag JBdiGriz (n=jbdigriz@12.147.16.2) |
| 23:01.35 | *** mode/#bzflag [+o JBdiGriz] by ChanServ |
| 23:12.43 | *** join/#bzflag Redsoxfan90 (i=ghjkghjk@c-24-218-163-107.hsd1.ma.comcast.net) |
| 23:13.06 | Redsoxfan90 | hi all |
| 23:23.46 | *** join/#bzflag bz35 (n=18daa36b@webchat.bzflag.bz) |
| 23:51.03 | *** join/#bzflag amcnabb (n=amcnabb@c-67-169-251-185.hsd1.ut.comcast.net) |
| 23:55.38 | *** join/#bzflag a_temp_dist (n=ATD@user-12l2r0o.cable.mindspring.com) |
| 23:58.12 | *** join/#bzflag A_Meteorite (n=A_Meteor@ppp-69-227-131-79.dsl.snlo01.pacbell.net) |
| 23:58.25 | *** part/#bzflag A_Meteorite (n=A_Meteor@ppp-69-227-131-79.dsl.snlo01.pacbell.net) |