Timestamps are in GMT/BST.
| 00:02:33 | | IAmBeard has joined |
| 00:15:59 | | Watusimoto_ Quit (Ping timeout: 245 seconds) |
| 00:39:07 | | IAmBeard Quit (Quit: Leaving) |
| 02:54:46 | | raptor has joined |
| 02:54:46 | | ChanServ sets mode +o raptor |
| 02:55:17 | raptor | i guess watusimoto didn't say if my fix was good for him.. |
| 04:25:53 | | zoomber_mbp has joined |
| 04:26:13 | zoomber_mbp | hi raptor |
| 04:29:41 | | zoomber_mbp Quit (Client Quit) |
| 04:41:27 | | kodaws has joined |
| 04:47:36 | | kodaws Quit (Ping timeout: 265 seconds) |
| 04:54:33 | | raptor Quit () |
| 06:35:34 | | sam686 Quit (Ping timeout: 245 seconds) |
| 07:53:34 | | kodaws has joined |
| 08:14:23 | | watusimoto has joined |
| 08:14:23 | | ChanServ sets mode +o watusimoto |
| 11:58:31 | | Watusimoto_ has joined |
| 12:30:59 | | Watusimoto_ Quit (Ping timeout: 256 seconds) |
| 13:16:20 | | Watusimoto_ has joined |
| 13:29:12 | | raptor has joined |
| 13:29:12 | | ChanServ sets mode +o raptor |
| 13:29:54 | raptor | morning |
| 13:34:49 | raptor | watusimoto / Watusimoto_: did my latest fix help your ALT + TAB problem? |
| 14:03:08 | | Watusimoto_ Quit (Ping timeout: 240 seconds) |
| 14:11:19 | | IAmBeard has joined |
| 15:01:23 | | raptor Quit () |
| 16:29:20 | | watusimoto Quit (Ping timeout: 244 seconds) |
| 17:01:03 | | Watusimoto has joined |
| 17:24:32 | | raptor has joined |
| 17:24:32 | | ChanServ sets mode +o raptor |
| 17:26:09 | raptor | good morning! again! |
| 17:49:01 | | kodaws Quit (Ping timeout: 260 seconds) |
| 17:57:00 | Watusimoto | hi |
| 17:57:08 | raptor | hello |
| 17:57:13 | Watusimoto | haven't tested your fix yet, can't quite update yet |
| 17:57:26 | Watusimoto | new lua theory that I'm testing |
| 17:57:39 | raptor | theory? |
| 17:57:48 | Watusimoto | new idea why it's broken |
| 17:58:04 | raptor | it was because of the solar eclipse the other night? |
| 17:58:06 | Watusimoto | I'll be away all next week, and it would be nice is this problemw as behind me so I wasn;t thinking about it |
| 17:58:11 | Watusimoto | probably |
| 18:19:37 | raptor | hmmm... sam686's server like to go down a lot now |
| 18:21:29 | raptor | i've been thinking - do we need to send unique ids with each authenticated player in the game? |
| 18:22:01 | raptor | i say that because you can log on four times on a nexus map with the same registered user |
| 18:22:11 | raptor | and get the 25 flags badge |
| 18:22:39 | raptor | because we compare usernames, which will be different if four of the same name sign on |
| 18:22:49 | raptor | if we also had a unique id attached, we could compare that... |
| 18:34:31 | | Watusimoto Quit (Ping timeout: 260 seconds) |
| 18:39:42 | IAmBeard | sounds like you need a server auth token system |
| 18:40:39 | IAmBeard | a good way is when a user logs in, their token is updated to something like sha1( username + unix_timestamp + some_salt_like_string ) |
| 18:40:48 | IAmBeard | and when you logout, the token clears |
| 18:40:56 | IAmBeard | and every token needs to be unique |
| 18:43:48 | raptor | i'm not sure that would fix the current problem: we need a way to tell that all users with the same login are the same person |
| 18:44:19 | raptor | i was thinkng something as simple as passing along the phpbb id to each client if they're logged in |
| 18:46:20 | IAmBeard | so when you log in after launching bitfighter, it doesn't actually track if you've logged in? |
| 18:47:19 | raptor | it does |
| 18:47:30 | IAmBeard | so all it does right now is say "yup, that's the right username and password, now I know where to send some stats" |
| 18:47:50 | raptor | it adds an 'authenticated' flag |
| 18:48:25 | raptor | the problem comes in when you join a server twice: the server renames one of you so everyone has a unique name |
| 18:49:04 | raptor | actually i need to do a little more research: there *may* be a way to tell it is the same individual, but i'm just not sure yet |
| 18:49:39 | IAmBeard | it may be good for the server to reject same-names |
| 18:49:51 | IAmBeard | it encourages people to create an account, or at least do a unique name |
| 19:16:32 | IAmBeard | not related to bitfighter, but pretty awesome for anyone who grew up on star trek; http://www.buildtheenterprise.org/ |
| 19:17:57 | raptor | interesting... |
| 19:24:57 | | Watusimoto has joined |
| 20:29:42 | Watusimoto | uh... sure! |
| 20:29:50 | Watusimoto | to id comparison |
| 20:30:17 | raptor | hi |
| 20:30:40 | raptor | i was thinking something as simple as just keeping track of the phpbb id on the PlayerInfo object (is that what it is called now?) |
| 20:30:44 | Watusimoto | you're proposing comparing usrer ids to prevent the 1 user connects 4 times badge hack? |
| 20:30:49 | raptor | yes |
| 20:30:53 | Watusimoto | sure |
| 20:31:00 | raptor | ok |
| 20:31:06 | Watusimoto | why not? |
| 20:31:15 | Watusimoto | easy, low cost |
| 20:31:28 | raptor | no reason: i just like to discuss any feature changes |
| 20:32:03 | Watusimoto | maybe you could see if there were another id we could remove (I think we send at least one id somewhere) |
| 20:32:20 | Watusimoto | though I could be mistaken |
| 20:33:38 | raptor | as far as i know the server is always comparing user names because they are guaranteed to be unique |
| 20:38:14 | Watusimoto | yes, i think that's right |
| 20:38:38 | Watusimoto | but then the server will change the name, and send the altered name to the master? |
| 20:39:42 | raptor | yeah - that may be a problem, too: master gets the altered name, but also the authenticated status |
| 20:40:09 | raptor | so raptor.0 can be authenticated but show up in the high score list... |
| 20:41:32 | IAmBeard | i still think it's a good idea to just reject same-name users on the server |
| 20:41:51 | IAmBeard | and first startup, build some sort of profile with a unique name |
| 20:42:09 | raptor | ^^ and that's another possibility, except when a client crashes he'll be locked out of a server until the old connection is kicked |
| 20:42:48 | IAmBeard | or when they connect after a crash, the old connection gets a ping, and if there is no response, then it's dropped |
| 20:43:13 | IAmBeard | essentially if you're registered and connect a second time, the old connection should always be dropped |
| 20:43:24 | IAmBeard | since you're registered, it's almost a guarantee that it's the actual user |
| 20:43:47 | raptor | until your little brother logs in as you on the downstairs computer... :) |
| 20:44:07 | IAmBeard | in my version, signing in and out will be a little more managable |
| 20:44:21 | IAmBeard | so that sort of issue shouldn't be that bad |
| 20:46:07 | raptor | well, what do you think Watusimoto, should we disallow the same user on any given server twice? |
| 20:46:20 | Watusimoto | no |
| 20:46:27 | Watusimoto | because |
| 20:46:52 | Watusimoto | if you get disconnected, the server doesn't realize right away; it would suck to have to wait until the server timed out for you to rejoin |
| 20:47:02 | Watusimoto | however |
| 20:47:24 | Watusimoto | we could change it that if a registered player connects, and is already connected, the already-connected client gets kicked |
| 20:47:59 | Watusimoto | for unregistered players, we could just disallow the same username, forcing them to change names manually |
| 20:48:13 | IAmBeard | well, a reconnect would be like ghosting on irc - because we can guarantee that a user/pass login is current...and for people not registered, then this encourages them to at least set a username beyond the default |
| 20:48:14 | Watusimoto | except it would kind of suck to have to leave the game altogether |
| 20:48:46 | IAmBeard | ah, so we are on the same train of thought :) |
| 20:49:30 | Watusimoto | perhaps if you attempt to connect with unregistered name that is a dupe, the client could propose changing the name to bah.0 (or whatever) to allow player to rejoin immediately |
| 20:49:46 | raptor | propose? |
| 20:50:17 | Watusimoto | "You cannot join because of duplicate user name. Change name to blah.o and retry?" |
| 20:50:22 | Watusimoto | Yes No |
| 20:50:33 | Watusimoto | If no, get dumped back to main menu |
| 20:50:40 | Watusimoto | if yes name changes, and retries |
| 20:51:13 | IAmBeard | is login even necessary before joining a game? |
| 20:51:34 | raptor | for game lobby chat and editor testing |
| 20:51:43 | IAmBeard | ah |
| 20:51:44 | IAmBeard | :) |
| 20:52:59 | IAmBeard | oh, i mean like the menu option |
| 20:53:20 | IAmBeard | so when youre' just in the menu, before even getting to the lobby, login is fairly unnecessary |
| 20:53:56 | IAmBeard | but i suppose timing isn't a big deal |
| 20:54:20 | IAmBeard | when a user initially log in at the beginning of the app, we could just check to see if the name is not in use or registered |
| 20:55:03 | Watusimoto | if two players with same name want to play on separate servers, is that ok? |
| 20:55:09 | Watusimoto | currently yes |
| 20:55:19 | Watusimoto | assuming unregistered name |
| 20:56:48 | IAmBeard | but for statistics sake, it'd be easier to track unique names |
| 20:57:33 | Watusimoto | I don't feel strongly -- we could check if name is in use and reject if so (as we do with bad pw) |
| 20:57:35 | raptor | only registered players really matter: there are a million ChumpChanges |
| 20:57:42 | Watusimoto | well that's the thing |
| 20:58:05 | Watusimoto | I agree with that statement |
| 20:58:23 | Watusimoto | stats for unregistered names are kind of pointless |
| 20:58:34 | Watusimoto | except possibly game results |
| 21:00:08 | IAmBeard | but it does stop a potential problem before it happens |
| 21:00:32 | IAmBeard | but I do agree that it doesn't make a lot of sense for same-names in different servers |
| 21:01:06 | raptor | i don't see a problem with unregistered players anywhere - if they are worried about stats, they should register and be done with it |
| 21:01:29 | | koda has joined |
| 21:08:46 | Watusimoto | yes; especially if they are playing with chumpChange |
| 22:04:57 | | IAmBeard Quit (Quit: Leaving) |
| 22:19:23 | Watusimoto | the lua stack seems to be being corrupted at some point. Not just wrong elements, but weird garbage that causes problems when investigated |
| 22:20:25 | raptor | really? |
| 22:21:41 | raptor | sam686 was good at tracking down that last issue we had with bots + asteroids crashing with a messed up lua stack |
| 22:25:15 | | sam686 has joined |
| 22:25:15 | | ChanServ sets mode +v sam686 |
| 22:25:48 | Watusimoto | this is a whole nother level |
| 22:28:43 | Watusimoto | there's something wrong here |
| 22:28:48 | Watusimoto | it gets worse every time I run |
| 22:28:52 | Watusimoto | I'm doing a full rebuild |
| 22:29:00 | raptor | that was a split-adjective |
| 22:29:10 | raptor | yay full rebuild |
| 22:31:13 | Watusimoto | I don't think it iwll help |
| 22:32:00 | raptor | how far away from the beaten path (the last merge) are you? |
| 22:33:42 | Watusimoto | only one file |
| 22:40:11 | Watusimoto | rebuild didn;t help; will try restarting ide |
| 22:40:18 | raptor | ha |
| 22:55:03 | | koda Quit (Quit: koda) |
| 23:01:59 | raptor | ok, heading home |
| 23:02:13 | | raptor Quit () |
| 23:07:32 | | BFLogBot - Commit 0e18590bfd18 | Author: watusim...@bitfighter.org | Log: Debugging tools: Add dumpTable method, improve dumpStack (now includes optional message) |
| 23:07:34 | | BFLogBot - Commit 8affadeeed5e | Author: watusim...@bitfighter.org | Log: Improve debugging code |
| 23:07:35 | | BFLogBot - Commit e09e4bb8e882 | Author: watusim...@bitfighter.org | Log: Minor improvements to debugging code |
| 23:07:37 | | BFLogBot - Commit f4076c4a0c7f | Author: watusim...@bitfighter.org | Log: Including more debugging code |
| 23:07:38 | | BFLogBot - Commit c5595616af02 | Author: watusim...@bitfighter.org | Log: Merge |
| 23:20:55 | | Watusimoto Quit (Ping timeout: 260 seconds) |
| 23:44:01 | | raptor has joined |
| 23:44:01 | | ChanServ sets mode +o raptor |
| 23:44:44 | raptor | he left! |
| 23:49:52 | raptor | well, let's see what happens when s_bot is run... |