chatters - Project Hosting on Google Code

Earlier this year Jul 23, 2009 issue 49 (When setting your status to inactive via the "afk" command, ...) reported by ShahzaibMuneeb - What steps will reproduce the problem? To reproduce the problem you can run the AFK command to set yourself inactive. What is the expected output? What do you see instead? The expected output is that the client setting himself/herself inactive via the "afk" command is shown in grey (inactive) in the who grid. What version of the product are you using? On what operating system? Microsoft Vista Ultimate 32 bit What channel were you using when the problem occurred? Maztekia What version of BYOND are you using? BYOND 444.1024 Please provide any additional information below. From my understanding this problem can be fixed by simply running the update command when the users go inactive (afk). Since the afk command is using a toggling system you can simply place the update procedure call outside the if statements which check if the user active/inactive and what to set to. What steps will reproduce the problem? To reproduce the problem you can run the AFK command to set yourself inactive. What is the expected output? What do you see instead? The expected output is that the client setting himself/herself inactive via the "afk" command is shown in grey (inactive) in the who grid. What version of the product are you using? On what operating system? Microsoft Vista Ultimate 32 bit What channel were you using when the problem occurred? Maztekia What version of BYOND are you using? BYOND 444.1024 Please provide any additional information below. From my understanding this problem can be fixed by simply running the update command when the users go inactive (afk). Since the afk command is using a toggling system you can simply place the update procedure call outside the if statements which check if the user active/inactive and what to set to. Feb 26, 2009 r179 ([No log message]) committed by SoutoJohn - [No log message] [No log message] Feb 05, 2009 r178 (Various updates.) committed by SoutoJohn - Various updates. Various updates. Feb 03, 2009 r177 ([No log message]) committed by SoutoJohn - [No log message] [No log message] Feb 02, 2009 r176 ([No log message]) committed by SoutoJohn - [No log message] [No log message] Feb 02, 2009 r175 (Removed paint and games completely. Disabled file transfers...) committed by SoutoJohn - Removed paint and games completely. Disabled file transfers. Other tweaks, started working on improving ban functionality. Removed paint and games completely. Disabled file transfers. Other tweaks, started working on improving ban functionality. Feb 01, 2009 r174 (Removed an old itunes feature.) committed by SoutoJohn - Removed an old itunes feature. Removed an old itunes feature. Feb 01, 2009 r173 (Various tweaks.) committed by SoutoJohn - Various tweaks. Various tweaks. Feb 01, 2009 r172 ([No log message]) committed by SoutoJohn - [No log message] [No log message] Feb 01, 2009 r171 (Fixed IP resolving.) committed by SoutoJohn - Fixed IP resolving. Fixed IP resolving. Feb 01, 2009 r170 (Telnet users weren't being given op commands on join, fixed....) committed by SoutoJohn - Telnet users weren't being given op commands on join, fixed. Tweaked the join message a little bit. Removed some NetMan calls, waiting for Chatters Channel Server before reenabling those. Telnet users weren't being given op commands on join, fixed. Tweaked the join message a little bit. Removed some NetMan calls, waiting for Chatters Channel Server before reenabling those. Jan 25, 2009 r169 (Quick fix.) committed by SoutoJohn - Quick fix. Quick fix. Jan 25, 2009 r168 (Maztekia to date.) committed by SoutoJohn - Maztekia to date. Maztekia to date. Jan 25, 2009 r167 (Maztekia branch. Quite a few additions ontop of Chatters.) committed by SoutoJohn - Maztekia branch. Quite a few additions ontop of Chatters. Maztekia branch. Quite a few additions ontop of Chatters. Jan 25, 2009 issue 45 (Topic Line Not Filtered) Status changed by SoutoJohn - Fixed. Status: Fixed Fixed. Status: Fixed Jan 25, 2009 issue 44 (Failure in parsing multiple [keyword]:[text] entries.) Status changed by SoutoJohn - Status: Accepted Status: Accepted Jan 25, 2009 issue 46 (System Settings Page Glitch) Status changed by SoutoJohn - Fixed. Status: Fixed Fixed. Status: Fixed Jan 25, 2009 issue 42 (Colons mess up output) Status changed by SoutoJohn - Could not reproduce. ":( :)" outputs properly. Status: WontFix Could not reproduce. ":( :)" outputs properly. Status: WontFix Jan 25, 2009 issue 30 (Fadenames can't be turned off once defined) Status changed by SoutoJohn - Has been fixed a long time ago. Status: Fixed Has been fixed a long time ago. Status: Fixed Jan 25, 2009 issue 38 (Reconnect - Who Output Panel Swapped) Status changed by SoutoJohn - Fixed. Had to load the interface, then swap the widgets as before it would swap widgets during loading, causing the who pane to be missized in the end. Status: Fixed Fixed. Had to load the interface, then swap the widgets as before it would swap widgets during loading, causing the who pane to be missized in the end. Status: Fixed Jan 25, 2009 issue 47 (Connection failure) Status changed by SoutoJohn - Status: WontFix Status: WontFix Jan 25, 2009 issue 48 (Pressing cancel on ban reason box causes the ban to go ahead...) Status changed by SoutoJohn - Fixed. Also fixed kick with the same problem. Status: Fixed Fixed. Also fixed kick with the same problem. Status: Fixed Older Dec 04, 2008 issue 48 (Pressing cancel on ban reason box causes the ban to go ahead...) reported by stephen.badger - What steps will reproduce the problem? 1. First you must be an Operator capable of banning. 2. Type in /ban User 3. The reason box will appear, press cancel. What is the expected output? What do you see instead? You'd expect the ban to not go through, instead the user is banned. What version of the product are you using? On what operating system? Whatever version Crashed dreamed up for Maztekia. My OS is Fedora 9. What channel were you using when the problem occurred? Maztekia. What version of BYOND are you using? 431.1006 What steps will reproduce the problem? 1. First you must be an Operator capable of banning. 2. Type in /ban User 3. The reason box will appear, press cancel. What is the expected output? What do you see instead? You'd expect the ban to not go through, instead the user is banned. What version of the product are you using? On what operating system? Whatever version Crashed dreamed up for Maztekia. My OS is Fedora 9. What channel were you using when the problem occurred? Maztekia. What version of BYOND are you using? 431.1006 Nov 13, 2008 issue 47 (Connection failure) commented on by holydaemon - Also I'm L-Viper in Byond Also I'm L-Viper in Byond Nov 13, 2008 issue 47 (Connection failure) reported by holydaemon - What steps will reproduce the problem? 1. Login 2. Chat 3. Fail What is the expected output? What do you see instead? everything was fine until it kicked me after 15 minutes or so of chatting. then it kicked me in 5 minutes, then again in less than that, etc. What version of the product are you using? On what operating system? Windows, PC What channel were you using when the problem occurred? Maztekia, default What version of BYOND are you using? 430 or whatever the newest one is Please provide any additional information below. What steps will reproduce the problem? 1. Login 2. Chat 3. Fail What is the expected output? What do you see instead? everything was fine until it kicked me after 15 minutes or so of chatting. then it kicked me in 5 minutes, then again in less than that, etc. What version of the product are you using? On what operating system? Windows, PC What channel were you using when the problem occurred? Maztekia, default What version of BYOND are you using? 430 or whatever the newest one is Please provide any additional information below. Sep 14, 2008 issue 46 (System Settings Page Glitch) reported by yotaxp - What steps will reproduce the problem? 1. Open the Settings panel. 2. Click 'Update' on the system tab. What is the expected output? What do you see instead? - The clock appears with formatting tags rather than plain text. It should appear as it does before you press 'Update'. What channel were you using when the problem occurred? - Maztekia What steps will reproduce the problem? 1. Open the Settings panel. 2. Click 'Update' on the system tab. What is the expected output? What do you see instead? - The clock appears with formatting tags rather than plain text. It should appear as it does before you press 'Update'. What channel were you using when the problem occurred? - Maztekia Sep 14, 2008 issue 45 (Topic Line Not Filtered) reported by yotaxp - What steps will reproduce the problem? 1. Turn on chat filters. 2. Use filtered words in the channel topic. What is the expected output? What do you see instead? - You see the raw topic text. - You should see the filtered topic text. What channel were you using when the problem occurred? - Maztekia What steps will reproduce the problem? 1. Turn on chat filters. 2. Use filtered words in the channel topic. What is the expected output? What do you see instead? - You see the raw topic text. - You should see the filtered topic text. What channel were you using when the problem occurred? - Maztekia Aug 27, 2008 r166 committed by SoutoJohn Aug 27, 2008 r165 (Maztekia branch.) committed by SoutoJohn - Maztekia branch. Maztekia branch. Aug 27, 2008 issue 40 (IM bug) Status changed by SoutoJohn - Issue fixed. Status: Fixed Issue fixed. Status: Fixed Aug 27, 2008 issue 40 (IM bug) commented on by SoutoJohn - Issue fixed. Issue fixed. Aug 27, 2008 issue 33 (Blank interface on Login for some users) Status changed by SoutoJohn - Status: Fixed Status: Fixed Aug 27, 2008 issue 39 (Banning doesn't work) Status changed by SoutoJohn - Fixed again. Status: Fixed Fixed again. Status: Fixed Aug 27, 2008 issue 39 (Banning doesn't work) commented on by SoutoJohn - Fixed again. Fixed again. Aug 03, 2008 issue 44 (Failure in parsing multiple [keyword]:[text] entries.) reported by stephen.badger - What steps will reproduce the problem? 1. Attempt to say something that contains two [keyword]:[text] entries, such as "Testing google:ha define:ha". What is the expected output? What do you see instead? You'd expect both to be parsed and links generated consequently. Instead, only the last [keyword]:[text] entry is parsed, any others are left untouched. What version of the product are you using? On what operating system? Version 0.1 Beta on Windows XP x86, Crashed's server. What channel were you using when the problem occurred? Maztekia, the default channel for Crashed's server. What version of BYOND are you using? Version 424.993 Please provide any additional information below. What steps will reproduce the problem? 1. Attempt to say something that contains two [keyword]:[text] entries, such as "Testing google:ha define:ha". What is the expected output? What do you see instead? You'd expect both to be parsed and links generated consequently. Instead, only the last [keyword]:[text] entry is parsed, any others are left untouched. What version of the product are you using? On what operating system? Version 0.1 Beta on Windows XP x86, Crashed's server. What channel were you using when the problem occurred? Maztekia, the default channel for Crashed's server. What version of BYOND are you using? Version 424.993 Please provide any additional information below. Jul 29, 2008 issue 39 (Banning doesn't work) commented on by SoutoJohn - Fixed a while ago. Fixed a while ago.

issue 49 (When setting your status to inactive via the "afk" command, ...) reported by ShahzaibMuneeb - What steps will reproduce the problem? To reproduce the problem you can run the AFK command to set yourself inactive. What is the expected output? What do you see instead? The expected output is that the client setting himself/herself inactive via the "afk" command is shown in grey (inactive) in the who grid. What version of the product are you using? On what operating system? Microsoft Vista Ultimate 32 bit What channel were you using when the problem occurred? Maztekia What version of BYOND are you using? BYOND 444.1024 Please provide any additional information below. From my understanding this problem can be fixed by simply running the update command when the users go inactive (afk). Since the afk command is using a toggling system you can simply place the update procedure call outside the if statements which check if the user active/inactive and what to set to.

What steps will reproduce the problem? To reproduce the problem you can run the AFK command to set yourself inactive. What is the expected output? What do you see instead? The expected output is that the client setting himself/herself inactive via the "afk" command is shown in grey (inactive) in the who grid. What version of the product are you using? On what operating system? Microsoft Vista Ultimate 32 bit What channel were you using when the problem occurred? Maztekia What version of BYOND are you using? BYOND 444.1024 Please provide any additional information below. From my understanding this problem can be fixed by simply running the update command when the users go inactive (afk). Since the afk command is using a toggling system you can simply place the update procedure call outside the if statements which check if the user active/inactive and what to set to.

Earlier this year

Older