|
|
[ChatRelayBot] Build 72 (Bots)
[ChatRelayBot] Build 72 // Bots
May 9, 2003, 3:58am
http://caesar.homeunix.org/aw/chatrelay.shtml
ChatRelayBot 2.0, Build 72
Beta Notice
This version of the ChatRelayBot is beta software. There are still issues that may come up in the beta version that could cause data loss [related to the program], and affect the stability of either your system or the program. If you do not wish to test beta-quality and potentially unstable software, you should wait until the ChatRelayBot has been officially released as production-quality software.
Version 1.0
The last version of 1.0, ChatRelayBot 1.042, has officially been dropped and will no longer be available for download. It is recommended that you either participate in the 2.0 open beta, or wait until the production-quality release of version 2.0 becomes available.
Bug Fixes
The following bugs have been resolved in this build:
a) The option to "Relay chat to Bot Controllers and Public Speakers only" did not function if you attempted to enable it. This feature from version 1.0 has been removed from the 2.0 feature set.
b) Using the CRB's normal 1.0-style relay service created a "feedback" effect.
c) The censor list was not saved after exiting and reopening CRB.
d) Starting the ChatRelayBot returned error codes in hexadecimal notation (e.g., $3B is 59).
e) Serious Crash Resolved: If the "%" sign was used alone (e.g.: " % "), the ChatRelayBot would report access violation after access violation. If these errors were not dispersed quickly, and the CRB left alone, the program would eventually die of a stack overflow. It is imperative that all users of ChatRelayBot build 71 immediately upgrade to build 72 once this information becomes public knowledge. This bug also appears in version 1.042. Users of CRB version 1.0 should consider upgrading to version 2.0, as version 1.0 will no longer be updated.
f) The ChatRelayBot will now handle disconnections more appropriately.
g) Action text will now relay to the Bone Network.
New Features/Enhancements
a) The following features and/or enhancements have been introduced in this build:
b) Console Message Throttle Control will control the number of console messages sent per 500 milliseconds (this time can be changed).
c) The Configuration dialog now appears as a standard tabbed dialog.
d) The ChatRelayBot can now join and create password-protected Bone channels.
e) Text can now be selected and copied in the GUI CRB's chat history window.
f) The Chat History window in the GUI CRB will now automatically clear itself after 12KB of text. Previously, this was automatically after 1MB of text. Large amounts of text in the window will tend to lag the application.
g) The CRB's bone connection can now be controlled by the Bone icon on the main application.
h) If the configuration file is missing, the Configuration dialog will automatically pop up.
i) The GUI CRB now has a dialog with user information (double-click a user in the presence list).
j) The CRB now is able to identify when it has disconnected from the Bone network.
k) The CRB will now identify the universe and world it is from when connecting to the Bone Network and joining a channel. For example, if your bot is being run in the main universe and is in AAWR, your bot will identify itself on-join with aw://auth.activeworlds.com:5670/aawr.
l) The CRB's log format has changed to allow identification of an instance of a CRB (related to the Console-Mode version of the CRB to be later released). A viewer ships with the GUI CRB that will read the log.
Note that the documentation included with the program has been changed. The monolithic Word document is no longer being maintained; instead, it is now in HTML format (and available online: http://caesar.homeunix.org/aw/crb-help/). The documentation can be downloaded at http://caesar.homeunix.org/aw/crb-help/Help.zip (107KB).
If you've actually managed to read all the way down here, thanks. :)
--
Tony M.
May 9, 2003, 5:41am
/color blue , even this features is on, I get access denied as answer when I
try.
Tengel
[View Quote]"tony m" <ag5v1u7001 at sneakemail.com> wrote in message
news:67gmbvkhirtn1i7t9rdn7ghltnj3f96bdj at 4ax.com...
> http://caesar.homeunix.org/aw/chatrelay.shtml
> ChatRelayBot 2.0, Build 72
>
> Beta Notice
>
> This version of the ChatRelayBot is beta software. There are still issues
that may come up in the beta version that could cause data loss [related to
the program], and affect the stability of either your system or the program.
If you do not wish to test beta-quality and potentially unstable software,
you should wait until the ChatRelayBot has been officially released as
production-quality software.
>
> Version 1.0
>
> The last version of 1.0, ChatRelayBot 1.042, has officially been dropped
and will no longer be available for download. It is recommended that you
either participate in the 2.0 open beta, or wait until the
production-quality release of version 2.0 becomes available.
>
> Bug Fixes
>
> The following bugs have been resolved in this build:
>
> a) The option to "Relay chat to Bot Controllers and Public Speakers only"
did not function if you attempted to enable it. This feature from version
1.0 has been removed from the 2.0 feature set.
> b) Using the CRB's normal 1.0-style relay service created a "feedback"
effect.
> c) The censor list was not saved after exiting and reopening CRB.
> d) Starting the ChatRelayBot returned error codes in hexadecimal notation
(e.g., $3B is 59).
> e) Serious Crash Resolved: If the "%" sign was used alone (e.g.: " % "),
the ChatRelayBot would report access violation after access violation. If
these errors were not dispersed quickly, and the CRB left alone, the program
would eventually die of a stack overflow. It is imperative that all users of
ChatRelayBot build 71 immediately upgrade to build 72 once this information
becomes public knowledge. This bug also appears in version 1.042. Users of
CRB version 1.0 should consider upgrading to version 2.0, as version 1.0
will no longer be updated.
> f) The ChatRelayBot will now handle disconnections more appropriately.
> g) Action text will now relay to the Bone Network.
>
> New Features/Enhancements
>
> a) The following features and/or enhancements have been introduced in this
build:
> b) Console Message Throttle Control will control the number of console
messages sent per 500 milliseconds (this time can be changed).
> c) The Configuration dialog now appears as a standard tabbed dialog.
> d) The ChatRelayBot can now join and create password-protected Bone
channels.
> e) Text can now be selected and copied in the GUI CRB's chat history
window.
> f) The Chat History window in the GUI CRB will now automatically clear
itself after 12KB of text. Previously, this was automatically after 1MB of
text. Large amounts of text in the window will tend to lag the application.
> g) The CRB's bone connection can now be controlled by the Bone icon on the
main application.
> h) If the configuration file is missing, the Configuration dialog will
automatically pop up.
> i) The GUI CRB now has a dialog with user information (double-click a user
in the presence list).
> j) The CRB now is able to identify when it has disconnected from the Bone
network.
> k) The CRB will now identify the universe and world it is from when
connecting to the Bone Network and joining a channel. For example, if your
bot is being run in the main universe and is in AAWR, your bot will identify
itself on-join with aw://auth.activeworlds.com:5670/aawr.
> l) The CRB's log format has changed to allow identification of an instance
of a CRB (related to the Console-Mode version of the CRB to be later
released). A viewer ships with the GUI CRB that will read the log.
>
> Note that the documentation included with the program has been changed.
The monolithic Word document is no longer being maintained; instead, it is
now in HTML format (and available online:
http://caesar.homeunix.org/aw/crb-help/). The documentation can be
downloaded at http://caesar.homeunix.org/aw/crb-help/Help.zip (107KB).
>
> If you've actually managed to read all the way down here, thanks. :)
>
> --
> Tony M.
|
May 9, 2003, 7:08am
ahh, this happen when /whois is enable
[View Quote]"tengel" <tengel at fna.no> wrote in message
news:3ebb5b9b at server1.Activeworlds.com...
> /color blue , even this features is on, I get access denied as answer when
I
> try.
>
> Tengel
>
>
> "tony m" <ag5v1u7001 at sneakemail.com> wrote in message
> news:67gmbvkhirtn1i7t9rdn7ghltnj3f96bdj at 4ax.com...
issues
> that may come up in the beta version that could cause data loss [related
to
> the program], and affect the stability of either your system or the
program.
> If you do not wish to test beta-quality and potentially unstable software,
> you should wait until the ChatRelayBot has been officially released as
> production-quality software.
> and will no longer be available for download. It is recommended that you
> either participate in the 2.0 open beta, or wait until the
> production-quality release of version 2.0 becomes available.
only"
> did not function if you attempted to enable it. This feature from version
> 1.0 has been removed from the 2.0 feature set.
> effect.
notation
> (e.g., $3B is 59).
> the ChatRelayBot would report access violation after access violation. If
> these errors were not dispersed quickly, and the CRB left alone, the
program
> would eventually die of a stack overflow. It is imperative that all users
of
> ChatRelayBot build 71 immediately upgrade to build 72 once this
information
> becomes public knowledge. This bug also appears in version 1.042. Users of
> CRB version 1.0 should consider upgrading to version 2.0, as version 1.0
> will no longer be updated.
this
> build:
> messages sent per 500 milliseconds (this time can be changed).
> channels.
> window.
> itself after 12KB of text. Previously, this was automatically after 1MB of
> text. Large amounts of text in the window will tend to lag the
application.
the
> main application.
> automatically pop up.
user
> in the presence list).
Bone
> network.
> connecting to the Bone Network and joining a channel. For example, if your
> bot is being run in the main universe and is in AAWR, your bot will
identify
> itself on-join with aw://auth.activeworlds.com:5670/aawr.
instance
> of a CRB (related to the Console-Mode version of the CRB to be later
> released). A viewer ships with the GUI CRB that will read the log.
> The monolithic Word document is no longer being maintained; instead, it is
> now in HTML format (and available online:
> http://caesar.homeunix.org/aw/crb-help/). The documentation can be
> downloaded at http://caesar.homeunix.org/aw/crb-help/Help.zip (107KB).
>
>
|
May 9, 2003, 7:31am
can it be added in Option "remember color" so people don't need to type
color command all the time?
[View Quote]"tony m" <ag5v1u7001 at sneakemail.com> wrote in message
news:67gmbvkhirtn1i7t9rdn7ghltnj3f96bdj at 4ax.com...
> http://caesar.homeunix.org/aw/chatrelay.shtml
> ChatRelayBot 2.0, Build 72
>
> Beta Notice
>
> This version of the ChatRelayBot is beta software. There are still issues
that may come up in the beta version that could cause data loss [related to
the program], and affect the stability of either your system or the program.
If you do not wish to test beta-quality and potentially unstable software,
you should wait until the ChatRelayBot has been officially released as
production-quality software.
>
> Version 1.0
>
> The last version of 1.0, ChatRelayBot 1.042, has officially been dropped
and will no longer be available for download. It is recommended that you
either participate in the 2.0 open beta, or wait until the
production-quality release of version 2.0 becomes available.
>
> Bug Fixes
>
> The following bugs have been resolved in this build:
>
> a) The option to "Relay chat to Bot Controllers and Public Speakers only"
did not function if you attempted to enable it. This feature from version
1.0 has been removed from the 2.0 feature set.
> b) Using the CRB's normal 1.0-style relay service created a "feedback"
effect.
> c) The censor list was not saved after exiting and reopening CRB.
> d) Starting the ChatRelayBot returned error codes in hexadecimal notation
(e.g., $3B is 59).
> e) Serious Crash Resolved: If the "%" sign was used alone (e.g.: " % "),
the ChatRelayBot would report access violation after access violation. If
these errors were not dispersed quickly, and the CRB left alone, the program
would eventually die of a stack overflow. It is imperative that all users of
ChatRelayBot build 71 immediately upgrade to build 72 once this information
becomes public knowledge. This bug also appears in version 1.042. Users of
CRB version 1.0 should consider upgrading to version 2.0, as version 1.0
will no longer be updated.
> f) The ChatRelayBot will now handle disconnections more appropriately.
> g) Action text will now relay to the Bone Network.
>
> New Features/Enhancements
>
> a) The following features and/or enhancements have been introduced in this
build:
> b) Console Message Throttle Control will control the number of console
messages sent per 500 milliseconds (this time can be changed).
> c) The Configuration dialog now appears as a standard tabbed dialog.
> d) The ChatRelayBot can now join and create password-protected Bone
channels.
> e) Text can now be selected and copied in the GUI CRB's chat history
window.
> f) The Chat History window in the GUI CRB will now automatically clear
itself after 12KB of text. Previously, this was automatically after 1MB of
text. Large amounts of text in the window will tend to lag the application.
> g) The CRB's bone connection can now be controlled by the Bone icon on the
main application.
> h) If the configuration file is missing, the Configuration dialog will
automatically pop up.
> i) The GUI CRB now has a dialog with user information (double-click a user
in the presence list).
> j) The CRB now is able to identify when it has disconnected from the Bone
network.
> k) The CRB will now identify the universe and world it is from when
connecting to the Bone Network and joining a channel. For example, if your
bot is being run in the main universe and is in AAWR, your bot will identify
itself on-join with aw://auth.activeworlds.com:5670/aawr.
> l) The CRB's log format has changed to allow identification of an instance
of a CRB (related to the Console-Mode version of the CRB to be later
released). A viewer ships with the GUI CRB that will read the log.
>
> Note that the documentation included with the program has been changed.
The monolithic Word document is no longer being maintained; instead, it is
now in HTML format (and available online:
http://caesar.homeunix.org/aw/crb-help/). The documentation can be
downloaded at http://caesar.homeunix.org/aw/crb-help/Help.zip (107KB).
>
> If you've actually managed to read all the way down here, thanks. :)
>
> --
> Tony M.
|
May 9, 2003, 9:44am
If you add new color when bot is online and save it, color.ini will be
deleted and you have only customcolors.txt left, in this file you have this
color
ColorA=FFFFFFFF
ColorB=FFFFFFFF
ColorC=FFFFFFFF
ColorD=FFFFFFFF
ColorE=FFFFFFFF
ColorF=FFFFFFFF
ColorG=FFFFFFFF
ColorH=FFFFFFFF
ColorI=FFFFFFFF
ColorJ=FFFFFFFF
ColorK=FFFFFFFF
ColorL=FFFFFFFF
ColorM=FFFFFFFF
ColorN=FFFFFFFF
ColorO=FFFFFFFF
ColorP=FFFFFFFF
and this was not what I saved
Tengel
[View Quote]"tony m" <ag5v1u7001 at sneakemail.com> wrote in message
news:67gmbvkhirtn1i7t9rdn7ghltnj3f96bdj at 4ax.com...
> http://caesar.homeunix.org/aw/chatrelay.shtml
> ChatRelayBot 2.0, Build 72
>
> Beta Notice
>
> This version of the ChatRelayBot is beta software. There are still issues
that may come up in the beta version that could cause data loss [related to
the program], and affect the stability of either your system or the program.
If you do not wish to test beta-quality and potentially unstable software,
you should wait until the ChatRelayBot has been officially released as
production-quality software.
>
> Version 1.0
>
> The last version of 1.0, ChatRelayBot 1.042, has officially been dropped
and will no longer be available for download. It is recommended that you
either participate in the 2.0 open beta, or wait until the
production-quality release of version 2.0 becomes available.
>
> Bug Fixes
>
> The following bugs have been resolved in this build:
>
> a) The option to "Relay chat to Bot Controllers and Public Speakers only"
did not function if you attempted to enable it. This feature from version
1.0 has been removed from the 2.0 feature set.
> b) Using the CRB's normal 1.0-style relay service created a "feedback"
effect.
> c) The censor list was not saved after exiting and reopening CRB.
> d) Starting the ChatRelayBot returned error codes in hexadecimal notation
(e.g., $3B is 59).
> e) Serious Crash Resolved: If the "%" sign was used alone (e.g.: " % "),
the ChatRelayBot would report access violation after access violation. If
these errors were not dispersed quickly, and the CRB left alone, the program
would eventually die of a stack overflow. It is imperative that all users of
ChatRelayBot build 71 immediately upgrade to build 72 once this information
becomes public knowledge. This bug also appears in version 1.042. Users of
CRB version 1.0 should consider upgrading to version 2.0, as version 1.0
will no longer be updated.
> f) The ChatRelayBot will now handle disconnections more appropriately.
> g) Action text will now relay to the Bone Network.
>
> New Features/Enhancements
>
> a) The following features and/or enhancements have been introduced in this
build:
> b) Console Message Throttle Control will control the number of console
messages sent per 500 milliseconds (this time can be changed).
> c) The Configuration dialog now appears as a standard tabbed dialog.
> d) The ChatRelayBot can now join and create password-protected Bone
channels.
> e) Text can now be selected and copied in the GUI CRB's chat history
window.
> f) The Chat History window in the GUI CRB will now automatically clear
itself after 12KB of text. Previously, this was automatically after 1MB of
text. Large amounts of text in the window will tend to lag the application.
> g) The CRB's bone connection can now be controlled by the Bone icon on the
main application.
> h) If the configuration file is missing, the Configuration dialog will
automatically pop up.
> i) The GUI CRB now has a dialog with user information (double-click a user
in the presence list).
> j) The CRB now is able to identify when it has disconnected from the Bone
network.
> k) The CRB will now identify the universe and world it is from when
connecting to the Bone Network and joining a channel. For example, if your
bot is being run in the main universe and is in AAWR, your bot will identify
itself on-join with aw://auth.activeworlds.com:5670/aawr.
> l) The CRB's log format has changed to allow identification of an instance
of a CRB (related to the Console-Mode version of the CRB to be later
released). A viewer ships with the GUI CRB that will read the log.
>
> Note that the documentation included with the program has been changed.
The monolithic Word document is no longer being maintained; instead, it is
now in HTML format (and available online:
http://caesar.homeunix.org/aw/crb-help/). The documentation can be
downloaded at http://caesar.homeunix.org/aw/crb-help/Help.zip (107KB).
>
> If you've actually managed to read all the way down here, thanks. :)
>
> --
> Tony M.
|
May 9, 2003, 11:00am
I'm unable to reproduce this. Each time, the color is saved in colors.ini and the file is not deleted.
Customcolors.txt are the custom colors from the color selection dialog.
[View Quote]On 9 May 2003 07:44:54 -0400, "tengel" <tengel at fna.no> wrote:
|
>If you add new color when bot is online and save it, color.ini will be
>deleted and you have only customcolors.txt left, in this file you have this
>ColorA=FFFFFFFF
>ColorB=FFFFFFFF
>ColorC=FFFFFFFF
>ColorD=FFFFFFFF
>ColorE=FFFFFFFF
>ColorF=FFFFFFFF
>ColorG=FFFFFFFF
>ColorH=FFFFFFFF
>ColorI=FFFFFFFF
>ColorJ=FFFFFFFF
>ColorK=FFFFFFFF
>ColorL=FFFFFFFF
>ColorM=FFFFFFFF
>ColorN=FFFFFFFF
>ColorO=FFFFFFFF
>ColorP=FFFFFFFF
May 9, 2003, 2:44pm
Option "enabel show avatar name" should be there, so when bot log in, people
can still whisper. and it turn it when it logs out again.
And autolog in, so I don't need to type PPW, this if this kinda bot gonna
run on server, and in somehow server do a restart, so it can log in, without
my help.
[View Quote]"tony m" <ag5v1u7001 at sneakemail.com> wrote in message
news:67gmbvkhirtn1i7t9rdn7ghltnj3f96bdj at 4ax.com...
> http://caesar.homeunix.org/aw/chatrelay.shtml
> ChatRelayBot 2.0, Build 72
>
> Beta Notice
>
> This version of the ChatRelayBot is beta software. There are still issues
that may come up in the beta version that could cause data loss [related to
the program], and affect the stability of either your system or the program.
If you do not wish to test beta-quality and potentially unstable software,
you should wait until the ChatRelayBot has been officially released as
production-quality software.
>
> Version 1.0
>
> The last version of 1.0, ChatRelayBot 1.042, has officially been dropped
and will no longer be available for download. It is recommended that you
either participate in the 2.0 open beta, or wait until the
production-quality release of version 2.0 becomes available.
>
> Bug Fixes
>
> The following bugs have been resolved in this build:
>
> a) The option to "Relay chat to Bot Controllers and Public Speakers only"
did not function if you attempted to enable it. This feature from version
1.0 has been removed from the 2.0 feature set.
> b) Using the CRB's normal 1.0-style relay service created a "feedback"
effect.
> c) The censor list was not saved after exiting and reopening CRB.
> d) Starting the ChatRelayBot returned error codes in hexadecimal notation
(e.g., $3B is 59).
> e) Serious Crash Resolved: If the "%" sign was used alone (e.g.: " % "),
the ChatRelayBot would report access violation after access violation. If
these errors were not dispersed quickly, and the CRB left alone, the program
would eventually die of a stack overflow. It is imperative that all users of
ChatRelayBot build 71 immediately upgrade to build 72 once this information
becomes public knowledge. This bug also appears in version 1.042. Users of
CRB version 1.0 should consider upgrading to version 2.0, as version 1.0
will no longer be updated.
> f) The ChatRelayBot will now handle disconnections more appropriately.
> g) Action text will now relay to the Bone Network.
>
> New Features/Enhancements
>
> a) The following features and/or enhancements have been introduced in this
build:
> b) Console Message Throttle Control will control the number of console
messages sent per 500 milliseconds (this time can be changed).
> c) The Configuration dialog now appears as a standard tabbed dialog.
> d) The ChatRelayBot can now join and create password-protected Bone
channels.
> e) Text can now be selected and copied in the GUI CRB's chat history
window.
> f) The Chat History window in the GUI CRB will now automatically clear
itself after 12KB of text. Previously, this was automatically after 1MB of
text. Large amounts of text in the window will tend to lag the application.
> g) The CRB's bone connection can now be controlled by the Bone icon on the
main application.
> h) If the configuration file is missing, the Configuration dialog will
automatically pop up.
> i) The GUI CRB now has a dialog with user information (double-click a user
in the presence list).
> j) The CRB now is able to identify when it has disconnected from the Bone
network.
> k) The CRB will now identify the universe and world it is from when
connecting to the Bone Network and joining a channel. For example, if your
bot is being run in the main universe and is in AAWR, your bot will identify
itself on-join with aw://auth.activeworlds.com:5670/aawr.
> l) The CRB's log format has changed to allow identification of an instance
of a CRB (related to the Console-Mode version of the CRB to be later
released). A viewer ships with the GUI CRB that will read the log.
>
> Note that the documentation included with the program has been changed.
The monolithic Word document is no longer being maintained; instead, it is
now in HTML format (and available online:
http://caesar.homeunix.org/aw/crb-help/). The documentation can be
downloaded at http://caesar.homeunix.org/aw/crb-help/Help.zip (107KB).
>
> If you've actually managed to read all the way down here, thanks. :)
>
> --
> Tony M.
|
May 9, 2003, 6:15pm
Well, this was funny, I found that color.ini file back, it have been
saven/moved to my desktop, wonder how that could happen
[View Quote]"tony m" <ag5v1u7001 at sneakemail.com> wrote in message
news:if9nbvovcsullecvfu3vls3olb9jtilfj0 at 4ax.com...
> I'm unable to reproduce this. Each time, the color is saved in colors.ini
and the file is not deleted.
>
> Customcolors.txt are the custom colors from the color selection dialog.
>
> On 9 May 2003 07:44:54 -0400, "tengel" <tengel at fna.no> wrote:
>
this
>
|
May 9, 2003, 6:37pm
For future reference, please review this bug writing guideline before submitting any bugs (this applies to all, not just tengel): http://caesar.homeunix.org/bugzilla/bugwritinghelp.html
Bugs should be submitted via email or posted through Bugzilla. Either place you submit it, please try to make use of the guidelines above, especially regarding reproducibility. Making these reports through the newsgroups should be done sparingly. I'm more likely to notice [and resolve] bugs submitted through Bugzilla/email than through newsgroup posts. As you always should, check the bug list on http://caesar.homeunix.org/bugzilla/buglist.cgi before reporting any bugs.
Thanks for participating in the beta, and I still encourage you to submit feedback through the mediums I have asked you to use. :)
[View Quote]On 9 May 2003 16:15:35 -0400, "tengel" <tengel at fna.no> wrote:
|
>Well, this was funny, I found that color.ini file back, it have been saven/moved to my desktop, wonder how that could happen
|
