QB#67 - Move custom messages to the database

Trac Ticket #22 - Originally reported by: Krayon

Customisable messages are currently stored in the config.py file. They should be moved to the

When this is done, the messages should be changed from REQUIRING the data placeholders (%s etc) to optionally containing them. The system can be made more advanced, for 1. %normal_cost% = cost of item before 2. %cost% = item 3. %discount% = discount percent 4. %guild% = guild they belong to, %player player’‘s

msg_trade_total_guild_discount = “Well %player%, because you belong to guild %guild%, we are give you a %discount% percent discount off the price. This will therefore only be %cost%gc

The calculated selling and buying values were off when the value was not a whole number, and it''s fractional value >= .5. Now using math ceil and floor functions respectively. Fixes #17.

The message system was functional however no help was available. Created help information for the msg command and listed it in general help. This fixes #16.

Fixed #18 where bot would crash if sent incomplete msg command. Also removed message msg_unknown_request from the config.py file and added msg_message_option and msg_message_nomsg to better explain the invalid msg command requests.

Moved PM responses to seperate file: responses.py

Added Responses table to the database. It will store a list of response messages to override the defaults. From now on, users will not have to (nor should they) modify the responses.py. This was done re #22 which will be closed once the messages support more customisability/flexability.