X-Git-Url: https://jfr.im/git/irc/evilnet/x3.git/blobdiff_plain/c8ca69a02e41114aa1303505df301df5f4fd686c..37e08c82c2958b3b96ada2bf76a9578f1dbbb2b3:/UPGRADE diff --git a/UPGRADE b/UPGRADE index 80911e8..f58a94c 100644 --- a/UPGRADE +++ b/UPGRADE @@ -1,24 +1,27 @@ ************************************** -*** X3 IRC Services *** +*** X3 IRC Services *** ************************************** *** IMPORTANT UPGRADE INSTRUCTIONS *** ************************************** -From srvx 1.4: - Rename srvx.conf to x3.conf - Review .conf file settings. - * remove giveops, givevoice from set_shows and add "Voice" above "Protect". - * you can change from srvx.db to x3.db here also (dont forget to rename the file) - Run all of the steps below +Generally version-to-version upgrades can be done without trouble. The code +for the most part aims to be backward-compatable. You should back up the .db +files first (but you back those up anyway, dont you?) -As of CVS version 1.24: - bind chanserv 'uset autoop' and 'set voice' (see note below). +Sometimes when upgrading, some commands may have changed. When you upgrade +your .db file may not have command bindings for new commands added. +There is now a command to assist with this: rebindall. +If you don't have the 'rebindall' command bound, first bind it: + /msg O3 bind o3 * *modcmd.* +Then, after any upgrade, or after adding modules, or changing command effecting settings +such as 'email', you can simply run: + /msg O3 rebindall +to ensure you have all the latest commands bound on all services. - -NOTE about command bindings: -You may do: 'bind x3 * *chanserv.*' to re-bind ALL builtin commands on chanserv. This -is the simplest approach and probably a good idea to run for each module (chanserv, -opserv, nickserv, modcmd, etc) after upgrading or changing some features (such as email). +You may do: 'bind nick * *module.*' to re-bind ALL builtin commands on a givin module, +(chanserv, opserv, nickserv, modcmd, etc) if you prefer to update them individually +(if you unbind some default commands, and want them to stay unbound). Alternatively you can edit the .db by hand or using the 'bind' command on irc. -IMPORTANT: You will need to shut down x3 gracefully (using the die or restart commands) +NOTE: You will need to shut down x3 gracefully (using the die or restart commands) after binding in order for 'set' and 'uset' subcommand changes to function properly since -the listing is cached. +the listings are cached. +