Note If you're upgrading from 0.0.9 to 0.1.0 you may want to consider just throwing away your config/abstracts and starting again, it'll probably be easier :)
Upgrading from 0.0.9 to SVN/0.1.0
- Back up your current installation, just in case
cd eggdrop/scripts tar czf bmotion-preupgrade.tar.gz bmotion
- Move your current installation out of the way
mv bmotion bmotion-orig
- Extract the new version into the bmotion dir, using whatever method is appropriate
- Copy abstracts to new install
cp -r bmotion-orig/modules/abstracts/en bmotion/local/abstracts
- Copy facts to new install
cp bmotion-orig/modules/facts/facts.txt bmotion/local/facts/
- Copy your settings file to new install
cp bmotion-orig/modules/settings.tcl bmotion/local/
- Review new settings file to see if there's anything you should be copying over - this is important as 0.1.0 does have some new settings you'll probably want to set
$EDITOR bmotion/modules/settings.sample.tcl
- .restart your bot (.rehash or .bmotion rehash will break because of changes between 0.0.9 and SVN!)
- You now need to teach it which channels to be active on - the SVN version doesn't use the config file for that. On the partyline do:
.chanset #channel +bmotion
for each channel.
That should be it!
Upgrading from <0.0.9 to 0.0.9
Since there were some changes to the way bMotion stores stuff between 0.0.8 and 0.0.9, some extra steps may be needed. It should automatically upgrade everything correctly, of course, but just in case...
Backup your current installation
cd EGGDROP/scripts cp -r bmotion bmotion-bak
Unpack the new one
tar zxf bmotion-0.0.9.tar.gz
Copy old settings over
- You should edit the new settings.tcl instead of replacing it with your old one, because there are some new settings you may want to change.
- Copy modules/facts/facts.txt to your new installation.
- Copy modules/abstracts/* to your new installation.
Start the bot
Start your bot as normal
