[rencro]

I'll take a look at the `dot_rune` column at my next opportunity.

Uleat, have a look here, this is sql/git/required/2014_02_20_buff_update.sql

-- UPDATE BUFF TABLES
ALTER TABLE `character_buffs` CHANGE `death_save_chance` `dot_rune` INT(10) NOT NULL DEFAULT '0';
ALTER TABLE `merc_buffs` CHANGE `DeathSaveSuccessChance` `dot_rune` INT(10) NOT NULL DEFAULT '0';
ALTER TABLE `botbuffs` CHANGE `DeathSaveSuccessChance` `dot_rune` INT(10) NOT NULL DEFAULT '0';

ALTER TABLE `character_buffs` CHANGE `death_save_aa_chance` `caston_x` INT(10) NOT NULL DEFAULT '0';
ALTER TABLE `merc_buffs` CHANGE `CasterAARank` `caston_x` INT(10) NOT NULL DEFAULT '0';
ALTER TABLE `botbuffs` CHANGE `CasterAARank` `caston_x` INT(10) NOT NULL DEFAULT '0';

ALTER TABLE `character_buffs` ADD `caston_y` INT(10) NOT NULL DEFAULT '0';
ALTER TABLE `merc_buffs` ADD `caston_y` INT(10) NOT NULL DEFAULT '0';
ALTER TABLE `botbuffs` ADD `caston_y` INT(10) NOT NULL DEFAULT '0';

ALTER TABLE `character_buffs` ADD `caston_z` INT(10) NOT NULL DEFAULT '0';
ALTER TABLE `merc_buffs` ADD `caston_z` INT(10) NOT NULL DEFAULT '0';
ALTER TABLE `botbuffs` ADD `caston_z` INT(10) NOT NULL DEFAULT '0';

ALTER TABLE `character_buffs` ADD `ExtraDIChance` INT(10) NOT NULL DEFAULT '0';
ALTER TABLE `merc_buffs` ADD `ExtraDIChance` INT(10) NOT NULL DEFAULT '0';
ALTER TABLE `botbuffs` ADD `ExtraDIChance` INT(10) NOT NULL DEFAULT '0';

ALTER TABLE `spells_new` CHANGE `not_reflectable` `reflectable` INT(11) NOT NULL DEFAULT '0';

Unfortunately if someone builds a db after that date they would have the wrong bot_buffs info as the "load_bots.sql" does not have this updated info in it.

From load_bots.sql as of 2-7-2015:

CREATE TABLE `botbuffs` (
	`BotBuffId` INT(10) UNSIGNED NOT NULL AUTO_INCREMENT,
	`BotId` INT(10) UNSIGNED NOT NULL DEFAULT '0',
	`SpellId` INT(10) UNSIGNED NOT NULL DEFAULT '0',
	`CasterLevel` INT(10) UNSIGNED NOT NULL DEFAULT '0',
	`DurationFormula` INT(10) UNSIGNED NOT NULL DEFAULT '0',
	`TicsRemaining` INT(11) UNSIGNED NOT NULL DEFAULT '0',
	`PoisonCounters` INT(11) UNSIGNED NOT NULL DEFAULT '0',
	`DiseaseCounters` INT(11) UNSIGNED NOT NULL DEFAULT '0',
	`CurseCounters` INT(11) UNSIGNED NOT NULL DEFAULT '0',
	`CorruptionCounters` INT(11) UNSIGNED NOT NULL DEFAULT '0',
	`HitCount` INT(10) UNSIGNED NOT NULL DEFAULT '0',
	`MeleeRune` INT(10) UNSIGNED NOT NULL DEFAULT '0',
	`MagicRune` INT(10) UNSIGNED NOT NULL DEFAULT '0',
	`DeathSaveSuccessChance` INT(10) UNSIGNED NOT NULL DEFAULT '0',
	`CasterAARank` INT(10) UNSIGNED NOT NULL DEFAULT '0',
	`Persistent` TINYINT(1) NOT NULL DEFAULT '0',
	PRIMARY KEY (`BotBuffId`),
	KEY `FK_botbuff_1` (`BotId`),
	CONSTRAINT `FK_botbuff_1` FOREIGN KEY (`BotId`) REFERENCES `bots` (`BotID`)
) ENGINE=InnoDB AUTO_INCREMENT=0 DEFAULT CHARSET=latin1;

i.e. this issue has been here for a bit, but the new logging erros to gmsay ect is now catching it, pretty spiffy that logging stuff!!!!

EDIT.. from bot.cpp

std::string query = StringFormat("SELECT SpellId, CasterLevel, DurationFormula, TicsRemaining, "
                                    "PoisonCounters, DiseaseCounters, CurseCounters, CorruptionCounters, "
                                    "HitCount, MeleeRune, MagicRune, dot_rune, caston_x, Persistent, "
                                    "caston_y, caston_z, ExtraDIChance FROM botbuffs WHERE BotId = %u",
                                    GetBotID());