]>
Commit | Line | Data |
---|---|---|
c8ca69a0 | 1 | ************************************** |
ca3486a2 | 2 | *** X3 IRC Services *** |
c8ca69a0 AS |
3 | ************************************** |
4 | *** IMPORTANT UPGRADE INSTRUCTIONS *** | |
5 | ************************************** | |
2f21ad2c AS |
6 | Generally version-to-version upgrades can be done without trouble. The code |
7 | for the most part aims to be backward-compatable. You should back up the .db | |
8 | files first (but you back those up anyway, dont you?) | |
1136f709 | 9 | |
2f21ad2c AS |
10 | Sometimes when upgrading, some commands may have changed. When you upgrade |
11 | your .db file may not have command bindings for new commands added. | |
12 | There is now a command to assist with this: rebindall. | |
c8273589 AS |
13 | If you don't have the 'rebindall' command bound, first bind it: |
14 | /msg O3 bind o3 * *modcmd.* | |
15 | Then, after any upgrade, or after adding modules, or changing command effecting settings | |
16 | such as 'email', you can simply run: | |
17 | /msg O3 rebindall | |
18 | to ensure you have all the latest commands bound on all services. | |
19 | ||
20 | You may do: 'bind nick * *module.*' to re-bind ALL builtin commands on a givin module, | |
21 | (chanserv, opserv, nickserv, modcmd, etc) if you prefer to update them individually | |
22 | (if you unbind some default commands, and want them to stay unbound). | |
c8ca69a0 | 23 | Alternatively you can edit the .db by hand or using the 'bind' command on irc. |
c8273589 | 24 | NOTE: You will need to shut down x3 gracefully (using the die or restart commands) |
c8ca69a0 | 25 | after binding in order for 'set' and 'uset' subcommand changes to function properly since |
c8273589 AS |
26 | the listings are cached. |
27 |