| 01:11.48 | *** join/#bzflag kierra (~quassel@209.222.8.90) |
| 01:12.34 | *** part/#bzflag Guest76629 (~quassel@209.222.8.90) |
| 01:13.31 | *** join/#bzflag moriah (~quassel@unaffiliated/kierra) |
| 05:39.34 | *** join/#bzflag zuii (~akos@BC06BF93.catv.pool.telekom.hu) |
| 06:23.54 | *** join/#bzflag zuii (~akos@BC06BF93.catv.pool.telekom.hu) |
| 06:28.55 | *** join/#bzflag dngor (~abuse@p3m/dngor) |
| 06:43.07 | *** join/#bzflag kierra (~quassel@209.222.8.90) |
| 08:30.21 | *** join/#bzflag meeba (~lamer@c-73-14-146-7.hsd1.co.comcast.net) |
| 08:31.05 | *** join/#bzflag develCuy (~quassel@unaffiliated/develcuy) |
| 08:42.15 | *** join/#bzflag Cobra_Fast (~coprah@wtwrp.de) |
| 09:01.57 | *** join/#bzflag dngor_ (~abuse@c-67-172-78-202.hsd1.fl.comcast.net) |
| 09:12.54 | *** join/#bzflag bier (~bier@helixnetworks.de) |
| 09:12.54 | *** join/#bzflag Cobra_Fast (~coprah@wtwrp.de) |
| 09:13.11 | *** join/#bzflag meeba (~lamer@c-73-14-146-7.hsd1.co.comcast.net) |
| 09:22.54 | *** join/#bzflag dngor (~abuse@p3m/dngor) |
| 09:34.34 | *** join/#bzflag bier (~bier@helixnetworks.de) |
| 09:34.34 | *** join/#bzflag Cobra_Fast (~coprah@wtwrp.de) |
| 09:35.31 | *** join/#bzflag mdskpr (~quassel@209.222.8.90) |
| 10:08.40 | *** join/#bzflag meeba (~lamer@c-73-14-146-7.hsd1.co.comcast.net) |
| 10:13.19 | *** join/#bzflag DTRemenak (~DTRemenak@2605:e000:141b:412b:c43b:203f:47e7:b6d5) |
| 10:13.19 | *** join/#bzflag DTRemenak (~DTRemenak@about/essy/CrazyCoder/DTRemenak) |
| 10:13.19 | *** mode/#bzflag [+v DTRemenak] by ChanServ |
| 10:14.01 | *** join/#bzflag meeba_ (~lamer@c-73-14-146-7.hsd1.co.comcast.net) |
| 10:32.48 | *** join/#bzflag meeba (~lamer@c-73-14-146-7.hsd1.co.comcast.net) |
| 10:42.42 | *** join/#bzflag Cobra_Fast (~coprah@wtwrp.de) |
| 10:46.49 | *** join/#bzflag Cobra_Fast (~coprah@wtwrp.de) |
| 11:04.38 | *** join/#bzflag DTRemenak (~DTRemenak@2605:e000:141b:412b:c43b:203f:47e7:b6d5) |
| 11:04.38 | *** join/#bzflag DTRemenak (~DTRemenak@about/essy/CrazyCoder/DTRemenak) |
| 11:04.38 | *** mode/#bzflag [+v DTRemenak] by ChanServ |
| 11:13.19 | *** join/#bzflag blast007 (~blast007@bzflag/developer/Blast) |
| 11:36.11 | *** join/#bzflag Cobra_Fast (~coprah@wtwrp.de) |
| 11:38.54 | *** join/#bzflag brad` (~brad@unaffiliated/brad) |
| 11:58.35 | *** join/#bzflag DTRemenak (~DTRemenak@2605:e000:141b:412b:c43b:203f:47e7:b6d5) |
| 11:58.36 | *** join/#bzflag DTRemenak (~DTRemenak@about/essy/CrazyCoder/DTRemenak) |
| 11:58.36 | *** mode/#bzflag [+v DTRemenak] by ChanServ |
| 12:05.47 | *** join/#bzflag echelon (~echelon@bzflag/player/echelon) |
| 12:11.28 | *** join/#bzflag blast007 (~blast007@bzflag/developer/Blast) |
| 12:12.13 | *** join/#bzflag bier (~bier@94.23.12.14) |
| 12:13.47 | *** join/#bzflag meeba (~lamer@c-73-14-146-7.hsd1.co.comcast.net) |
| 12:36.37 | *** join/#bzflag cods (~fred@tuxee.net) |
| 12:44.58 | *** join/#bzflag blast007 (~blast007@bzflag/developer/Blast) |
| 12:45.36 | *** join/#bzflag bier (~bier@helixnetworks.de) |
| 14:26.25 | *** join/#bzflag blast007 (~blast007@bzflag/developer/Blast) |
| 14:48.18 | *** join/#bzflag Cobra_Fast (~coprah@wtwrp.de) |
| 15:07.10 | *** join/#bzflag zuii (~akos@BC06BF93.unconfigured.pool.telekom.hu) |
| 15:54.44 | *** join/#bzflag zuii (~akos@BC06BF93.unconfigured.pool.telekom.hu) |
| 16:02.26 | *** join/#bzflag joevano (~joevano@bzflag/developer/JoeVano) |
| 16:02.26 | *** mode/#bzflag [+v joevano] by ChanServ |
| 16:09.19 | *** join/#bzflag BulletCatcher (~bc@bzflag/developer/BulletCatcher) |
| 16:36.17 | *** join/#bzflag DTRemenak|RDP (~DTRemenak@about/essy/CrazyCoder/DTRemenak) |
| 16:36.17 | *** mode/#bzflag [+v DTRemenak|RDP] by ChanServ |
| 16:54.13 | *** join/#bzflag DTRemenak (~DTRemenak@2605:e000:141b:412b:c43b:203f:47e7:b6d5) |
| 16:54.13 | *** join/#bzflag DTRemenak (~DTRemenak@about/essy/CrazyCoder/DTRemenak) |
| 16:54.13 | *** mode/#bzflag [+v DTRemenak] by ChanServ |
| 16:56.15 | *** join/#bzflag Cobra_Fast (~coprah@wtwrp.de) |
| 17:03.38 | *** join/#bzflag [Gort] (~gort@82-69-126-225.dsl.in-addr.zen.co.uk) |
| 17:03.38 | *** join/#bzflag [Gort] (~gort@unaffiliated/gort/x-9231432) |
| 17:11.43 | *** join/#bzflag Constitution (~josh@bzflag/developer/Constitution) |
| 17:38.06 | *** join/#bzflag Constitution (b8653225@bzflag/developer/Constitution) |
| 17:41.04 | *** join/#bzflag DTRemenak (~DTRemenak@2605:e000:141b:412b:c43b:203f:47e7:b6d5) |
| 17:41.04 | *** join/#bzflag DTRemenak (~DTRemenak@about/essy/CrazyCoder/DTRemenak) |
| 17:41.04 | *** mode/#bzflag [+v DTRemenak] by ChanServ |
| 17:41.22 | *** join/#bzflag macsforme (~josh@bzflag/developer/Constitution) |
| 17:53.08 | Constitution | the windows 10 taskbar close bug should be removed from the 2.4.4 milestone, right? |
| 17:58.49 | Constitution | I finally reproduced the bullet reload delay issue (actually a mouse button issue)... going to have a look at it |
| 18:33.36 | *** part/#bzflag Guest17012 (~quassel@209.222.8.90) |
| 18:34.40 | *** join/#bzflag kierra (~quassel@unaffiliated/kierra) |
| 18:47.54 | blast007 | I really don't know what to even look for with the Windows 10 issue, and I didn't want it holding up the release |
| 19:15.23 | the_map | I've noticed that ahs3's servers became rather popular suddenly; were they put up recently, or did they randomly become popular? |
| 19:19.35 | *** join/#bzflag alpha1-2 (~alpha1@181.90.27.129) |
| 19:22.35 | alpha1-2 | About colors, what is the objetive? To change the main 5 team colors? |
| 19:25.14 | blast007 | the objective was consistency |
| 19:26.09 | alpha1-2 | I can understand RGB improvement, but changing a blue tank in orange will break consistency precisely |
| 19:26.38 | blast007 | we already allowed changing the radar and tank colors (the untexture tanks) via BZDB variables, and I think *some* of the text we drew (perhaps the observer labels) used that radar or tank color |
| 19:27.14 | blast007 | but changes required a restart and manually editing the config and then some text didn't change color to match |
| 19:27.55 | blast007 | this is really a pointless discussion by now, though |
| 19:28.15 | alpha1-2 | what are "untexture tanks"? why pointless? |
| 19:28.50 | blast007 | tanks when textures are disabled |
| 19:32.15 | alpha1-2 | "some text didn't change color to match"? |
| 19:33.26 | alezakos | oh, that's what the tank color vars were used for |
| 19:33.50 | alezakos | I only saw them affecting shot colours |
| 19:37.39 | alezakos | alpha1-2: Before the update, the left and the right part of the scoreboard would show up in different colours if the user had specified a different color for a team, and the colours in the console would remain unchanged |
| 19:39.00 | alezakos | If your issue is ANSI2HTML not supporting RGB ANSI codes, why don't you submit a patch to them? :) |
| 19:44.14 | alpha1-2 | I'm trying to understand... Then you left the colors opened to all the RGB gama just 'cause of its easiness of coding at start (and opened to be modified/improved later, making it only allowed to 5 main colors and some brightness variabilities)? Because, as I said, if user A has blue tanks like reds, and user B has red tanks as blues, it will be a mess if they take screenshots for example. |
| 19:45.34 | alpha1-2 | (no basic consistency) |
| 19:45.45 | alpha1-2 | (too much liberty) |
| 19:47.15 | alpha1-2 | thi is why I asked what is th main objetive behind the improvement. To help colorblinded persons? |
| 19:48.07 | alpha1-2 | then with some brightness levels per color it would be enough (for the future improvements) |
| 19:49.07 | alpha1-2 | or maybe I am missing how colorblinded persons work? |
| 19:50.46 | alpha1-2 | and I would want that blast007 answered me why this discussion would be "pointless" |
| 19:51.24 | alpha1-2 | in a good way |
| 19:51.50 | blast007 | I've already answered. Why must I keep telling you the same thing? |
| 19:52.08 | blast007 | We allowed arbitrary colors for the radar and tank colors. |
| 19:52.32 | blast007 | So why would we switch that to a hardcoded list of 256 possible colors? How does that make any sense at all? |
| 19:54.23 | alpha1-2 | no, I am not talking of switching to 256 colors now, since I undersand that RGB is better. Just wondering what is the objetives behind and if the gamma will be shortened in the future to avoid inconsistencies as I said |
| 19:55.31 | alpha1-2 | (BTW, is it too hard to code in xterm 256 model?) |
| 19:55.40 | alpha1-2 | so hard* |
| 19:55.44 | blast007 | To completely support what we already had partially supported. |
| 19:57.01 | alpha1-2 | ah okay. And the plan for the future? Or thoses inconsistencies I mentioned are not too important? (just asking) |
| 19:57.27 | blast007 | what inconsistencies? |
| 19:58.31 | alpha1-2 | 2 users having completely different colors each one and taking for example totally different screenshots (tank blues will be reds and viceverse) |
| 19:59.27 | alpha1-2 | (I am imagining an extreme scenario) |
| 19:59.32 | blast007 | why is that a problem? |
| 19:59.50 | alpha1-2 | the bases also will change colors? |
| 20:00.44 | alpha1-2 | imagine complainings to an admin, having completely different colors: no consistency |
| 20:00.45 | blast007 | if texturing is off, probably |
| 20:01.12 | blast007 | that's a stupid complaint... |
| 20:02.01 | blast007 | People already use alternate textures in the game, and modified radar colors. |
| 20:02.10 | alpha1-2 | if, instead, in the future you limit to 5 main colors (with brightness variabilities), then problem solved. But, maybe, the main intention is to allow even in the menu options the choice of any color too? |
| 20:02.21 | alpha1-2 | (always in RGB) |
| 20:03.38 | alpha1-2 | in the menu options there will be the same 5 that nowadays? |
| 20:03.58 | blast007 | How about you spend your time fixing your script to support ISO-8613-3 24-bit RGB ANSI escape sequences. |
| 20:04.29 | alpha1-2 | no, I am not worry about my script |
| 20:04.49 | alpha1-2 | I will modify it surely |
| 20:05.13 | alpha1-2 | worried* |
| 20:05.41 | alpha1-2 | then, in the menu options there will be the same 5 that nowadays? |
| 20:06.26 | alpha1-2 | it will be confusing, IMO |
| 20:06.54 | alpha1-2 | no consistency in main team colors along the network |
| 20:07.23 | alpha1-2 | well, not saying more |
| 20:21.32 | alpha1-2 | ah, according to what alezakos said, *team names* (even in the menu) will be called the same, right? (red, green, blue and purple). The same as the others: rogue, rabbit, hunter and observer. This was one of the main concern for me. No consistency along the net. |
| 20:23.23 | alpha1-2 | it doesn't seem so crazy then, even if all the other will change of colors |
| 20:24.57 | alpha1-2 | all the other --> all the rest* |
| 20:33.21 | blast007 | did you think we were going to call teams #3388FF instead? |
| 20:34.15 | alpha1-2 | no, I thought you were going to allow players to call them of any color name (orange, gray, personal one, etc) |
| 20:34.35 | alpha1-2 | since blue will be orange... :P |
| 20:35.03 | alpha1-2 | I was some confused, yes |
| 20:36.04 | alpha1-2 | or: "Choose your favourite (preset) color: <here all the name colors available>" |
| 20:36.22 | alpha1-2 | (names not numbers) |
| 20:36.39 | alpha1-2 | and allowing modifications |
| 20:38.59 | blast007 | eventually, yes, there will be a menu with presets |
| 20:39.21 | alpha1-2 | yes, okay, but never in team names right? |
| 20:41.06 | alpha1-2 | unless you increment the team colors too (which is not bad while it is done consistently) |
| 20:42.17 | alpha1-2 | all will be server sided, tho... interesting... server A will have 10 colored teams; server B will have just 5, etc |
| 20:42.51 | alpha1-2 | you didn't mention this in your GUI improvement? (mouse, etc) |
| 20:49.55 | alpha1-2 | and every team color will have your personal set, OFC |
| 20:50.44 | alpha1-2 | or will mach* |
| 20:50.55 | alpha1-2 | match* sry |
| 20:56.01 | alpha1-2 | about testing RC2: *apparently* (it was weird) I just saw brad's server dissapearing (I will have to test it further, tho): I joined it with 29 minutes left (offical match), I went out and it dissapeared. Then, after chatting here, I returned when it was 15 min. left I think, and it was there. (I was able to see other busy servers, tho). I asked players and they didn't notice it. |
| 20:57.38 | blast007 | were actual players (not just observers) on the server? |
| 20:57.39 | alpha1-2 | maybe just a very rare problem, since the new random list improvement |
| 20:58.32 | alpha1-2 | yes, there were 4 players playing offi and several observers (afk for some minutes until one answered me) |
| 21:00.40 | alpha1-2 | hmm, I did't ask the players tho. Maybe they stopped match some and... observers doesn't count on the top? |
| 21:00.59 | blast007 | observers are ignored when sorting |
| 21:01.17 | blast007 | and servers with the same number of players are ordered randomly among each other |
| 21:01.51 | alpha1-2 | and idle players not considered right? |
| 21:02.11 | alpha1-2 | they are seen as players as well, I mean |
| 21:02.41 | alpha1-2 | if they paused some minutes for example being idle |
| 21:08.25 | blast007 | idle players are counted |
| 21:08.45 | alpha1-2 | ok |
| 21:42.45 | *** join/#bzflag Delusional (~Delusiona@unaffiliated/delusional) |
| 21:45.19 | alpha1-2 | Imagine this other complaint made by a cheater in a FFA server: "he was my mate and was tking me". While the truth was that he was of another color. How could an admin know, through only a screnshoot, that they were really of diff. colors? One solution would be reading the debug log (if they save the team names). I just want to discuss some, to imagine future scenarios, not to make problems. |
| 21:46.57 | alpha1-2 | hmm, yes, the team scores would be different, NVM :P |
| 21:48.07 | alpha1-2 | teams' scores* |
| 21:50.38 | alpha1-2 | (working in brad's issue) |
| 21:55.10 | alpha1-2 | and thinking in my script ("logconverter"), you always will conserve the original "msglog.txt" file, even if you convert it to HTML/PDF with the nowadays version, to being able re-convert it later with a possible new version, so no major problems (I won't commite suicide, don't worry :) |
| 21:55.47 | alpha1-2 | I just hate you alezakos :D |
| 21:56.07 | alpha1-2 | commit* |
| 22:04.50 | *** join/#bzflag nitroxis (n@nxs.one) |
| 22:10.40 | alpha1-2 | now brad's servers are down |
| 22:11.04 | alpha1-2 | I just went out from replaying |
| 22:23.00 | blast007 | alpha1-2: a screenshot has never been proof |
| 22:27.54 | alpha1-2 | admins ask for them usually (clients' logs would be useful too, IMO), they are some hard to edit. But recorded matches/servers logs are the last word, yes |
| 22:32.08 | alezakos | <PROTECTED> |
| 22:32.49 | brad | alpha1-2: down? |
| 22:35.41 | alpha1-2 | blast007: yes, noone online now |
| 22:37.48 | Constitution | I see three of brad's servers up, and I just joined all three successfully |
| 22:37.56 | alezakos | <PROTECTED> |
| 22:38.14 | alezakos | Also note the difference between brad and blast. |
| 22:38.51 | blast007 | alpha1-2: the proof is in server logs and replay files, not screenshots and client logs... |
| 22:39.32 | blast007 | (that, or seeing it first-hand) |
| 22:40.08 | alpha1-2 | I can't see any of brad's servers now (I was just replaying before), by search or by eye search through paging down |
| 22:40.59 | alpha1-2 | are you using RC2 Constitution? |
| 22:42.50 | alpha1-2 | I am a regular player and admins ask for screenshots usually |
| 22:43.55 | alpha1-2 | brad: yes, noone online now |
| 22:44.09 | blast007 | alpha1-2: yes, but that does NOT mean that screenshots are proof |
| 22:44.46 | alezakos | <PROTECTED> |
| 22:45.35 | alpha1-2 | oh yes alezakos, that's it, I was w/o password |
| 22:46.04 | alpha1-2 | this must be a new feature? |
| 22:46.30 | blast007 | no |
| 22:46.36 | blast007 | it's an old feature |
| 22:46.45 | blast007 | servers can advertise themselves to only specific groups |
| 22:47.31 | blast007 | been a feature for 10 years, since BZFlag 2.0.4 |
| 22:47.56 | alpha1-2 | ah okay, but note that anybody can log in into a GU offi server w/o being registered too |
| 22:48.30 | blast007 | can't play or talk though |
| 22:48.34 | *** join/#bzflag BZnotify (~BZnotify@192.30.252.40) |
| 22:48.34 | BZnotify | [13bzflag] 15allejo pushed 1 new commit to 062.4: 02http://git.io/vBKWM |
| 22:48.34 | BZnotify | 13bzflag/062.4 14ea32441 15allejo: Handle Phantom Zone zoning on flag drop... |
| 22:48.34 | *** part/#bzflag BZnotify (~BZnotify@192.30.252.40) |
| 22:48.41 | alpha1-2 | true |
| 22:49.04 | allejo | unregistered players are allowed to join to spark their interest in the league |
| 22:49.21 | blast007 | allejo: Please revert that change. We do not make gameplay changes like that in a stable branch. |
| 22:49.36 | alpha1-2 | then maybe it's a new setting from brad? |
| 22:50.29 | alpha1-2 | (or wrong one?) |
| 22:50.59 | *** join/#bzflag BZnotify (~BZnotify@192.30.252.42) |
| 22:50.59 | BZnotify | [13bzflag] 15allejo pushed 1 new commit to 062.4: 02http://git.io/vBKlZ |
| 22:50.59 | BZnotify | 13bzflag/062.4 14c9ab45f 15allejo: Revert "Handle Phantom Zone zoning on flag drop"... |
| 22:50.59 | *** part/#bzflag BZnotify (~BZnotify@192.30.252.42) |
| 22:51.03 | allejo | my bad |
| 22:51.28 | blast007 | besides, we should probably kill them when they drop it - they're dropping the devices that puts them into a different dimension ;) |
| 22:52.17 | allejo | lol I hardly see that as fair because of a server option :p |
| 22:52.33 | allejo | alpha1-2, it's not a new setting. it's been like that for a while now |
| 22:52.59 | alpha1-2 | okay allejo |
| 22:56.51 | Constitution | allejo: do commit it to master, though :P |
| 22:57.32 | Constitution | wonders who put a shot limit on the PZ flag |
| 22:59.34 | *** join/#bzflag BZnotify (~BZnotify@192.30.252.34) |
| 22:59.34 | BZnotify | [13bzflag] 15allejo pushed 1 new commit to 06master: 02http://git.io/vBK8A |
| 22:59.34 | BZnotify | 13bzflag/06master 145ec4e6e 15allejo: Handle Phantom Zone zoning on flag drop... |
| 22:59.34 | *** part/#bzflag BZnotify (~BZnotify@192.30.252.34) |
| 23:00.08 | allejo | forgot the inconsistency that would introduce between 2.4.2 and 2.4.4 |
| 23:01.00 | allejo | and I believe the issue said quickshot, so probably purplepanzer |
| 23:07.05 | alpha1-2 | well, I ended the brad's issue task, but *maybe* it was just that I deleted password, exit BZ and run it again (I don't remember; I always delete password when exiting). |
| 23:07.06 | alpha1-2 | brad.guleague.org:5158 (Official GU League Match Server [England]) |
| 23:07.08 | alpha1-2 | server: 2.4.3.20150316-DEVEL-linux-gnu - BZFS0221 |
| 23:07.09 | alpha1-2 | BZFlag version: 2.4.4.20151125-RC2-linux-gnu-SDL (0221) |
| 23:07.11 | alpha1-2 | match: offi-20151127-IKEA-vs-BEER-2041.rec |
| 23:07.12 | alpha1-2 | I joined about 29 min. 30 sec. left, I went out about 29 min left., then there was an issue around 27 min. left where klavier (red) went "nr". Game was paused. Just after it, he logged out and returned quickly saying "game crashed", "what happened(?)". Match was started again after 1 minute. What I can see just before is ashvala logging out (who had joined just before as observer) and Kesslar (red) killing benji 13 (purp). These pics show that moment. |
| 23:07.14 | alpha1-2 | http://i.imgsafe.org/6f08d24.png |
| 23:07.15 | alpha1-2 | http://i.imgsafe.org/8f61f71.png |
| 23:07.27 | alpha1-2 | exited* |
| 23:08.48 | alpha1-2 | I returned again (when I was able to see it again, and after chatting here) around 15 min left. |
| 23:15.38 | alezakos | What is your point, |
| 23:15.46 | alezakos | s/,/? |
| 23:16.36 | alezakos | And there's an option that lets you only store your username on the config so that you don't have to erase your password every time |
| 23:19.39 | alpha1-2 | ah okay |
| 23:20.08 | alpha1-2 | "[17:56] <alpha1-2> about testing RC2: *apparently* (it was weird) I just saw brad's server dissapearing (I will have to test it further, tho)(...)" |
| 23:25.55 | alpha1-2 | oh I mix in my mind brad with blast007 and allejo with alezakos :P (I need a break) |
| 23:26.36 | alpha1-2 | or alezakos with allejo* |
| 23:26.58 | *** mode/#bzflag [+o blast007] by ChanServ |
| 23:27.04 | *** kick/#bzflag [alpha1-2!~blast007@bzflag/developer/Blast] by blast007 (alpha1-2) |
| 23:27.04 | *** mode/#bzflag [+b *!*alpha1@181.90.27.*] by blast007 |
| 23:28.59 | *** mode/#bzflag [-o blast007] by blast007 |
| 23:52.26 | *** join/#bzflag nitroxis (n@nxs.one) |
