Website hosted by:
Future Point Inc.

Raptor Chat 2001
Raptor Chat 2001 Beta Build 1873, released September 23rd, 2000 - Download Now!
                          Bugs

This page contains a complete list of known Raptor Chat bugs, please read over the list before submitting them to us. If you find a new bug that is not on this page then please submit it to bugs@raptorchat.com, include a description, what you were doing when it happened, any error messages, your operating system and also be sure to include your build of Raptor Chat. To find your current build simply click on the "Info" tab within Raptor Chat or type <build> in the send text field.

The future release row indicates if the bug has been corrected for future releases of Raptor Chat.

Raptor Chat 2001 Beta Build 1836

Please remember that this is a beta release and therefore expected to contain bugs, it's purpose is to locate those bugs and have them corrected for the full release, most of the bugs have already been corrected.

Description: The #RC_User_Online and #RC_User_Offline events are never activated
Cause: This was caused by a conflict that occurred when the new blue dot icon was added to indicate that the monitor was updating.
Work Around: N/A
Future Release: Corrected
 

 

Description: Raptor Chat does not log the scripts history correctly
Cause: This was caused by updates made to another section of the scripts that reflected the performance of this feature.
Work Around: N/A
Future Release: Corrected
 

 

Description: The blue updating dot remains next to a persons name in the Online Monitor
Cause: There is a time out timer to ensure that Raptor Chat does not wait forever for the server to return the results from the /whois command, if it times out then it doesn't update the users icon.
Work Around: N/A
Future Release: Corrected
 

 

Description: Everyone's rank is set to "0" when loading the database at start-up
Cause: Minor miscalculation in the coding
Work Around: N/A
Future Release: Corrected
 

 

Description: Error while connecting to the server (Silent)
Cause: Minor bug in the method used to change your chat state
Work Around: Do not minimize the program before Raptor Chat connects to the server and let it completely load before connecting.
Future Release: Corrected
 

 

Description: The system-tray icon would display disconnected when you are connected
Cause: This was the result of the above bug, also corrected
Work Around: Change your state to "Operator" and then back to "Available"
Future Release: Corrected
 

 

Description: System-tray icon becomes blank occasionally after flashing
Cause: The icon was not being displayed when you double clicked on it
Work Around: Change your state and then change it back to the original
Future Release: Corrected
 

 

Description: The ignore repeating users option ignored users with ant-idle messages
Cause: The user repeated the same anti-idle message over the max number of times allowed and Raptor Chat does not exclude anti-idles from it's calculations
Work Around: Disable the option under Raptor Chat\Options\General
Future Release: Corrected
 

 

Description: Main form stays on top hiding all other windows beneath
Cause: This occurs only after Raptor Chat has been minimized and then restored
Work Around: Restart the program
Future Release: Corrected
 

 

Description: Users are not removed from the sizeable chat window's users list when they leave the channel
Cause: The program was never programmed to remove them
Work Around: You can reset the list be rejoining the channel
Future Release: Corrected
 

 

Description: Online Monitor does not work correctly on FSGS servers
Cause: FSGS replies differently then Battle.Net to the /whois command and Raptor Chat was not programmed to recognize the differences
Work Around: N/A
Future Release: Corrected
 

 

Description: The enter key cannot be used in the built in web browser
Cause: N/A
Work Around: N/A
Future Release: Corrected
 

 

Description: Selecting properties from the web browsers pull down menu causes Raptor Chat to crash
Cause: N/A
Work Around: N/A
Future Release: Corrected
 

 

Description: The "User Ranks" script feature does not work when you activate your own scripts
Cause: Originally programmed not to allow you to activate your own on message events
Work Around: You can also control this through Advanced If Conditions, add the following condition:
(Integer) Function(UserInfo;<user>;4)  Condition  Rank
Condition could be >= (bigger or equal to)
Rank can be any number between 1-7

Example:
(Integer) Function(UserInfo;<user>;4)  =>  3
This will only allow users with a rank equal or greater then 3 to activate the script

Future Release: Corrected
 

 

Description: An error occurs when exiting Raptor Chat through the tray-icon exit option
Cause: That option did not perform the correct shut-down procedures
Work Around: You will have to restore Raptor Chat and exit the normal way. The error also prevents Raptor Chat from saving your settings and database.
Future Release: Corrected
 

 

Description: The options, sizeable chat window and all other windows also close when the main form is minimized
Cause: A global minimize was performed instead of just a local one for the main form
Work Around: None available, although if a window opens while Raptor Chat is minimized then it will display.
Future Release: Corrected
 

 

Description: If you run on a high resolution and have special software to proportionally resize all of the programs components then the Raptor Chat Start-Up form does not display correctly and half of it is hidden.
Cause: The Start-Up form was programmatically resized after being displayed
Work Around: None available, although you can still run Raptor Chat if you do not move your mouse over the form, because if you do not then a 4 second timer will automatically start Raptor Chat for you.
Future Release: Corrected
 

 

Description: Raptor Chat would go crazy in some channels:
- Message field was not cleared after sending text
- Users list did not update correctly
- Messages such as the "/who" command were sent repeatedly
- It was not possible to shutdown or leave the channel
- Possibly more...
Cause: The channel name contained characters that are illegal for use in file names and Raptor Chat was attempting to log the text to a file with the name of the channel. This caused a silent error that prevented Raptor Chat from executing the clean-up functions.
Work Around: Disable chat logging under "General Options", or set Raptor Chat to log everything to the one default log file.
Future Release: Corrected
 

 

Description: Adding a user to an existing group with the /group command causes Raptor Chat to create a duplicate group.
Cause: Raptor Chat did not check correctly for existing groups.
Work Around: N/A
Future Release: Corrected
 

 

The Raptor Chat Website and all content is Copyright (c) 2000 Buaron Software