Mikaela/Limnoria
1
0
Fork 0
mirror of https://github.com/Mikaela/Limnoria.git synced 2025-05-13 18:07:25 +02:00
Code Issues Projects Releases Wiki Activity

Added FAQ about channel-specific databases.

Browse Source
This commit is contained in:
Jeremy Fincher 2004-08-29 15:57:03 +00:00
parent 0c97cb488f
commit af4f836402
1 changed files with 36 additions and 23 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

59
docs/FAQ
View File

@ -63,11 +63,6 @@ A: Currently, no. Feel free to make your case to us as to why a
with you, we'll change it for the next release. with you, we'll change it for the next release.
Q: How do I make my Supybot connect to multiple servers?
A: Just use the "connect" command in the Owner plugin. Easy as pie!
Q: Can Supybot do factoids? Q: Can Supybot do factoids?
A: Supybot most certainly can! In fact, we offer three full-fledged A: Supybot most certainly can! In fact, we offer three full-fledged
@ -112,25 +107,15 @@ A: As of present, we have no automated way to do so. Strike has
factoids-related plugins. factoids-related plugins.
Q: I found a bug, what do I do? Q: Do I really have to use separate databases for each channel?
A: Submit it on Sourceforge through our Sourceforge project page: A: Of course not! We default to separate databases for each channel
<http://sourceforge.net/tracker/?group_id=58965&atid=489447>. If because, well, that's what jemfinch always thought was
Sourceforge happens to be down when you try to submit your bug, reasonable. Anyway, if you change the configuration variable
then post it in the "Supybot Developer Discussion" forum at our supybot.databases.plugins.channelSpecific to False instead of
forums at <http://forums.supybot.org/>. If that doesn't work, True, for *most* databases, each channel will share the same
email supybot-bugs@lists.sourceforge.net. If that doesn't work, database (the exceptions are ChannelStats, Herald, Seen, and
email jemfinch@supybot.org. If that doesn't work, find yourself WordStats, which are inherently rather channel-based).
some carrier pigeons and ... hah! You thought I was serious!
Anyway, when you submit your bug, we'll need several things. If
the bug involved an uncaught exception, we need the traceback
(basically the stuff from "Uncaught exception in ..." to the next
log entry). We'd also like to see the commands that caused the
bug, or happened around the time you saw the bug. If the bug
involved a database, we'd love to see the database. Remember, it's
always worse to send us too little information in a bug report than
too much.
Q: Karma doesn't seem to work for me. Q: Karma doesn't seem to work for me.
@ -174,3 +159,31 @@ A: No, there isn't, and there probably never will be. Commands have
command, many users would call the command, see that they could command, many users would call the command, see that they could
perform it, and then run the command, thus doubling the activity perform it, and then run the command, thus doubling the activity
in the channel. Is that something you want? in the channel. Is that something you want?
Q: How do I make my Supybot connect to multiple servers?
A: Just use the "connect" command in the Owner plugin. Easy as pie!
Q: I found a bug, what do I do?
A: Submit it on Sourceforge through our Sourceforge project page:
<http://sourceforge.net/tracker/?group_id=58965&atid=489447>. If
Sourceforge happens to be down when you try to submit your bug,
then post it in the "Supybot Developer Discussion" forum at our
forums at <http://forums.supybot.org/>. If that doesn't work,
email supybot-bugs@lists.sourceforge.net. If that doesn't work,
email jemfinch@supybot.org. If that doesn't work, find yourself
some carrier pigeons and ... hah! You thought I was serious!
Anyway, when you submit your bug, we'll need several things. If
the bug involved an uncaught exception, we need the traceback
(basically the stuff from "Uncaught exception in ..." to the next
log entry). We'd also like to see the commands that caused the
bug, or happened around the time you saw the bug. If the bug
involved a database, we'd love to see the database. Remember, it's
always worse to send us too little information in a bug report than
too much.