aliendiplomat

Pretty essential idea for a patch. Haven't had a chance to test extensively, however I did notice a couple small issues with the included SQL update when attempting to apply to an 8763 database template. Problem #1: The file attempts to put values in the vehicle_id and passengers field for both the creature_addon and creature_template_addon tables, however neither of these tables have either of those columns in the default MaNGOS 8763 structure. Here's what I ran to add them prior to running the SQL patch for vehicles: -- MaNGOS 8763+ update ALTER TABLE creature_template_addon ADD COLUMN vehicle_id int(11) unsigned NOT NULL DEFAULT '0' AFTER moveflags; ALTER TABLE creature_template_addon ADD COLUMN passengers text AFTER vehicle_id; ALTER TABLE creature_addon ADD COLUMN vehicle_id int(11) unsigned NOT NULL DEFAULT '0' AFTER moveflags; ALTER TABLE creature_addon ADD COLUMN passengers text AFTER vehicle_id; I'm intuiting the field types (someone please correct me if I'm off), though the core complains if passengers is set to an integer, and this way it works. (I'm guessing the passenger field is populated with a string of data representing multiple current passengers?) Problem #2: You appear to have started to insert a section for people using UDB at the end (?), however it was cutoff before the completion of the query. This resulted in the 28887 and 28833 creatures being deleted and replaced with nothing. -- UDB DELETE FROM `creature` WHERE `id` IN (28887,28833); INSERT INTO `creature` (`guid`,`id`,`map`,`spawnMask`,`phaseMask`,`modelid`,`equipment_id`,`position_x`,`position_y`,`position_z`,`orientation`,`spawntimesecs`,`spawndist`,`currentwaypoint`,`curhealth`,`curmana`,`DeathState`,`MovementType`) VALUES (130112, 28833, 609, 1, 1, 25723, 0, 2104.74, -6179.82, 13.47, 1.22173, 360, 0, 0, 26140, 0, 0, 0), (130113, 28833, 609, 1, 1, 25723, 0, 2253.24, -6193.09, 13.4068, 1.85005, 360, 0, 0, 26140, 0, 0, 0), (130114, 28833, 609, 1, 1, 25723, 0, 2264.77, - To resolve I got rid of the DELETE query (since it isn't adding anything back for those ID's which were already modified earlier in the file and so clearly are necessary). I also trimmed off the section that got cut off, leaving the two insert lines that were completed. There was also a minor issue with one of the above creatures, 28887, and the core complaining about incorrect low mana value. I changed `minmana` = 0 and `maxmana` = 0 which is what it was before this patch, instead of 2117/2117 which it attempted to change it to. I left the other values this patch modifies for creature 28887 as they were. Here's the Vehicles SQL patch with these few changes made that you can run against an 8763+ version of the MaNGOS database structure without the aforementioned snags: http://filebeam.com/d9fb3a4b77dc8febd8a453b21b067086

Hey thanks, you rock! And here I was thinking it was just using that as a base and then referencing the .conf file for the correct values I'd set up there! Ran this on the characters table and everything seems to work great! (updated) REPLACE INTO `auctionhousebot` VALUES ('2', 'Alliance', '79000', '88000', '8', '24', '1', '8', '8', '4', '4', '0', '0', '1', '8', '45', '9', '12', '0', '0', '100', '150', '150', '250', '250', '450', '450', '850', '850', '1700', '1700', '3400', '3400', '6800', '70', '100', '70', '100', '80', '100', '75', '100', '80', '100', '80', '100', '80', '100', '0', '0', '0', '0', '0', '0', '0', '1', '1', '5', '12', '15', '20', '22', '10', '200'); REPLACE INTO `auctionhousebot` VALUES ('6', 'Horde', '79000', '88000', '8', '24', '1', '8', '8', '4', '4', '0', '0', '1', '8', '45', '9', '12', '0', '0', '100', '150', '150', '250', '250', '450', '450', '850', '850', '1700', '1700', '3400', '3400', '6800', '70', '100', '70', '100', '80', '100', '75', '100', '80', '100', '80', '100', '80', '100', '0', '0', '0', '0', '0', '0', '0', '1', '1', '5', '12', '15', '20', '22', '10', '200'); REPLACE INTO `auctionhousebot` VALUES ('7', 'Neutral', '79000', '88000', '8', '24', '1', '8', '8', '4', '4', '0', '0', '1', '8', '45', '9', '12', '0', '0', '100', '150', '150', '250', '250', '450', '450', '850', '850', '1700', '1700', '3400', '3400', '6800', '70', '100', '70', '100', '80', '100', '75', '100', '80', '100', '80', '100', '80', '100', '0', '0', '0', '0', '0', '0', '0', '1', '1', '5', '12', '15', '20', '22', '10', '200'); Now I just have to tweak the values a bit more. =) *EDIT: I noticed with the shared AH enabled in mangos conf the bot wasn’t posting a min-max number of items to each auction house (alliance, horde, and neutral) and then showing the results of all three combined. Instead it seemed only to do it once for all three, so my previous settings felt way too low with a max of only 15000 auctions. I also tweaked the price ratios for item qualities to something which tends to match the wowhead going rates more closely, as well as offset the ratios of item preference so less useless stuff is posted and more variety at various levels emerges. Man I love stuff like this!