| | 1 | X3 Frequently Asked Questions |
| | 2 | ------------------------------- |
| | 3 | |
| | 4 | This FAQ assumes that your services are named NickServ, ChanServ and |
| | 5 | OpServ respectively. |
| | 6 | |
| | 7 | Q1) How do I set up X3? |
| | 8 | A1) Read the README and INSTALL files, especially INSTALL. |
| | 9 | |
| | 10 | Q2) How do I set up my IRC server so X3 talks to it? |
| | 11 | A2) That depends on which IRC server you use. Check its |
| | 12 | documentation. Essentially you add a connect block for X3 in |
| | 13 | ircd.conf and point to that at the top of x3.conf. You'll also |
| | 14 | need a UWORLD block etc. |
| | 15 | |
| | 16 | Q3) I get "You must first authenticate with NickServ", help! |
| | 17 | A3) To register an account, /msg NickServ@services.example.com |
| | 18 | register YourName Password. You must be a global IRC operator to |
| | 19 | register the first account; X3 gives the first account "root" level |
| | 20 | (1000) access. To log in afterwards, use the "auth" command instead |
| | 21 | of "register". |
| | 22 | |
| | 23 | Q4) I do not like having to type "/msg NickServ@services.example.com" |
| | 24 | for all of my commands. How can I change that? |
| | 25 | A4) If you want to disable that for the auth command, use "/msg OpServ |
| | 26 | modcmd NickServ.auth flags -qualified". However, that is a BAD idea: |
| | 27 | if you have an auto-perform to log in, and you connect to some other |
| | 28 | IRC network, you will send your password to whoever or whatever is |
| | 29 | named NickServ on that network. |
| | 30 | |
| | 31 | Q5) How do I restrict all users from registering channels? |
| | 32 | A5) /msg opserv modcmd ChanServ.register flags +helping |
| | 33 | This will allow only network staff to register channels. For IRC |
| | 34 | operators and network helpers (users with account flag +H), security |
| | 35 | override can be enabled by sending "/msg ChanServ god on". For |
| | 36 | support helpers (users with account flag +h), security override is |
| | 37 | enabled when the user is in the configured support channel. |
| | 38 | |
| | 39 | Q6) How do I enable HelpServ? |
| | 40 | A6) When you run the "configure" script, you must enable the helpserv |
| | 41 | module; for example, "./configure --enable-modules=helpserv". After |
| | 42 | you compile and start X3 with that option, "/msg OpServ bind OpServ |
| | 43 | helpserv *helpserv.helpserv". After that, you can use "/msg OpServ |
| | 44 | helpserv help" and "/msg OpServ helpserv register"; the "helpserv" |
| | 45 | command acts as a gateway into the HelpServ system. |
| | 46 | |
| | 47 | Q7) How do I enable MemoServ? |
| | 48 | A7) When you run the "configure" script, you must enable the MemoServ |
| | 49 | module; for example, "./configure --enable-modules=memoserv". Then |
| | 50 | see the comment near the start of src/mod-memoserv.c for configuration |
| | 51 | options. |
| | 52 | |
| | 53 | Q8) How do I enable both HelpServ and MemoServ? |
| | 54 | A8) In addition to the post-install configuration steps above, you |
| | 55 | must mention both when you run the configure script. For example, run |
| | 56 | it using "./configure --enable-modules=memoserv,helpserv". (You may |
| | 57 | add the snoop and/or sockcheck modules as well; separate the module |
| | 58 | names with commas.) |
projects / irc / evilnet / x3.git / blame_incremental