BeBot - An Anarchy Online and Age Of Conan chat automaton
General => Feedback and Suggestions => Topic started by: Getrix on October 22, 2008, 08:41:56 pm
-
Small suggestion, rename this files so we dont need to edit / copy when a new version is released:
"Conf/Bot.conf" -> "Conf/Bot.conf.new"
"Conf/MySQL.conf" -> "Conf/MySQL.conf.new"
Thanks alot for a great tool!
-
some people dont have that problem because they have 2+ bots, in which case there configs are botname.Bot.conf
personally i think its a bad idea, if we did they would be problem caused by people not updating
since they are new to bot they might try to run with Bot.conf.new which ofc wont work
we can make it easier for new install or upgraded , we choose new install because in most cases they will have less experience and are more likly to have problems from it.
however i will try to think of a better upgrade system, altho no idea if i will think of anything
-
It's the question of easier updates or easier first starts...
With the current names new user don't have to rename any files, just set them up. And in case of an update they simply got to remember not to copy the conf directory.
With your suggestion updating is saver, but new users will have to edit and rename the config files. Not really sure that would be better.
Besides, if you use Botname.Bot.conf and Botname.MySQL.conf as config files for your bot you won't run into trouble with updates either. Might just be a slight bother to update the MySQL config files if you are running several bots under one directory structure. Which you don't seem to be doing, wouldn't work with both config files still using default names - at least the Bot.conf would have to be renamed.
-
Point taken, and i can after 2 great answeers see my suggestion wasnt thought-through..
Sorry :(
-
rename this files so we dont need to edit / copy when a new version is released
if no change to the conf happened in the update then it would b a simple matter of renaming ur conf and then back after, or deleting it from the zip before u extract to ur bot folder
as for if there is a change well then u would have to edit your old 1 anyway even if the new 1 was name ...new
my suggestion wasnt thought-through..
just so you know me and alreadythere discused this on IRC before we posted and we decided the old way is better as new installed are often buy people with less experience and people upgrading so we want to make it easier for them, we dont see a way to make it just as easy for new installs useing your way
-
If there is be an easy way to make sure no existing configs are overwritten this side of an update or install script while keeping the easy way for new users I'm open for suggestions.
The supported OSs of bebot mean a script isn't straight-forward either...
-
The supported OSs of bebot mean a script isn't straight-forward either...
Maybe not...all we need to really do is try and find the correct path to php (easy on UNIX, not so easy on Windows...), take AO Username, AO Password, Botname, and AO server, DB Username, DB Pass, DB name, DB server...org ID maybe...
I think it would be doable to create a first run startup script...
I think we should distribute the conf files as Bot.conf.TEMPLATE and MySQL.conf.TEMPLATE. I've accidentally overwritten conf files a couple times when updating. Throwing TEMPLATE in there makes it fairly obvious that this is the format for the conf files and that these files will need to be renamed for the bot to work.
-
what about this option, when running the bot if the conf file isnt found make it, asking for details in console, i already wrote 1 think my self that asks stuff in console
-
That was not a bad idea!
This way a first runner and also experienced ppl will have what they want/need=)
-
told ya i would think of an alternative that would please both new and old users :p