Fixed irc_topic() to honour server/hidden_host_type and associated config settings

[irc/evilnet/x3.git] / INSTALL

diff --git a/INSTALL b/INSTALL
index b55ff5425a7617cf51d18ee7a06845b1c9cb5371..d88eac6391d2b4b180ca33a1845cd0c2e26f8f94 100644 (file)
--- a/INSTALL
+++ b/INSTALL
@@ -14,12 +14,12 @@ files.
 
 Requirements:
 ----------
 
 Requirements:
 ----------

-This release of X3 (1.4) only supports the Undernet P10 and Bahamut
-protocols and is known to link with ircu/Universal (u2.10.09),
-ircu/Undernet (u2.10.10, u2.10.11), ircu-lain, and Bahamut 1.4.32. It
-does not support hybrid, Unreal, or any other ircd not listed. Should
+This release of X3 (1.4) only supports the Undernet P10
+protocol and is known to link to ircu/Undernet (u2.10.11, u2.10.12),
+Nefarious IRCu 0.4.0 and Nefarious IRCu 1.0. It does not support 
+bahamut, hybrid, Unreal, or any other ircd not listed. Should

 you find other compatible ircds, please let us know.  Most of the
 you find other compatible ircds, please let us know.  Most of the

-testing has been done on Nefarious IRCu 0.4.0 (Based on ircu2.10.11.x).
+testing has been done on Nefarious IRCu 0.4.0/1.0 (Based on ircu2.10.11.x).

 
 X3 is known to compile on the following systems as long as you
 are using GNU make (make on Linux, gmake on many other systems):
 
 X3 is known to compile on the following systems as long as you
 are using GNU make (make on Linux, gmake on many other systems):


@@ -54,9 +54,7 @@ Quick Install:
 $ ./configure
     NOTE: The protocol the resulting X3 binary will support is
     determined by the configure script. The P10 protocol is the
 $ ./configure
     NOTE: The protocol the resulting X3 binary will support is
     determined by the configure script. The P10 protocol is the

-    default; if you would like to link to Bahamut, you must pass
-    the --with-protocol=bahamut flag to the configure script:
-    $ ./configure --with-protocol=bahamut
+    default.

 $ make
 $ ${EDITOR} x3.conf
     NOTE: You may want to copy x3.conf.example to x3.conf and
 $ make
 $ ${EDITOR} x3.conf
     NOTE: You may want to copy x3.conf.example to x3.conf and


@@ -73,8 +71,7 @@ Compiling:
      system will have the resources needed for X3 to compile.  If you
      would like to change the path where X3 will be installed to,
      execute configure with the --prefix=/path option.  The default path
      system will have the resources needed for X3 to compile.  If you
      would like to change the path where X3 will be installed to,
      execute configure with the --prefix=/path option.  The default path

-     is ~/X3-X.X.X/, with the X's representing the version.  See the
-     note in "Quick Install" if you are linking to Bahamut.
+     is ~/x3/, with the X's representing the version. 

 
   3) On some systems you may need to edit the Makefile in order for
      it to compile correctly.  Includes, and other such things may
 
   3) On some systems you may need to edit the Makefile in order for
      it to compile correctly.  Includes, and other such things may


@@ -106,22 +103,22 @@ Compiling:
      with no verbosity, use the '-f' flag. If you just want to run it,
      execute X3 without any flags.
 
      with no verbosity, use the '-f' flag. If you just want to run it,
      execute X3 without any flags.
 

- 10) Once you have X3 started, you'll need to register a NickServ
+ 10) Once you have X3 started, you'll need to register a AuthServ

      account:
      account:

-       /msg NickServ@services.irc.com register <account> <password>
+       /msg AuthServ@services.irc.com register <account> <password>

      Make sure that you register the first account -- it is
      automatically granted certain privileges and gives you root-level
      Make sure that you register the first account -- it is
      automatically granted certain privileges and gives you root-level

-     access to OpServ once you are opered up.
+     access to O3 once you are opered up.

 
 

- 11) New operators can be given access to OpServ through NickServ's
+ 11) New operators can be given access to O3 through AuthServ's

      (or whatever you've named the nick/authentication service) oset
      command:
      (or whatever you've named the nick/authentication service) oset
      command:

-       /msg NickServ oset <nick>|*<account> level <level>
+       /msg AuthServ oset <nick>|*<account> level <level>

      Levels are generally beween 0 and 1000 by convention; higher
      numbers correspond to more access. You can also add helpers
      (users with extra privileges such as security override in
      Levels are generally beween 0 and 1000 by convention; higher
      numbers correspond to more access. You can also add helpers
      (users with extra privileges such as security override in

-     traditional configurations) through NickServ:
-       /msg NickServ oset <nick>|*<account> flags +H
+     traditional configurations) through AuthServ:
+       /msg AuthServ oset <nick>|*<account> flags +H

 
 End of file, INSTALL.
 
 
 End of file, INSTALL.