Jump to content

DaViper

Members
  • Posts

    185
  • Joined

  • Last visited

    Never
  • Donations

    0.00 GBP 

Everything posted by DaViper

  1. Hehe, if you noticed I had set the min items at 100 and the max items to your 3000 limits...just tried to customize it a little for you and yes it was a dump out of my DB which was made from the xeross's sql in the first place...but glad I could help...
  2. did you setup the auctionhousebot_table? you have to edit this as well, I suggested this to Nacium a long time ago for a basic setting so everyone could have it up and running with little fuss but it was never implemented. give me some time and I'll make an sql for for this purpose and hopefully it will get adopted in the main repos... Ok Here is the new Base sql: -- ---------------------------- -- Table structure for `auctionhousebot` -- ---------------------------- DROP TABLE IF EXISTS `auctionhousebot`; CREATE TABLE `auctionhousebot` ( `auctionhouse` int(11) NOT NULL DEFAULT '0' COMMENT 'mapID of the auctionhouse.', `name` char(25) DEFAULT NULL COMMENT 'Text name of the auctionhouse.', `minitems` int(11) DEFAULT '0' COMMENT 'This is the minimum number of items you want to keep in the auction house. a 0 here will make it the same as the maximum.', `maxitems` int(11) DEFAULT '0' COMMENT 'This is the number of items you want to keep in the auction house.', `mintime` int(11) DEFAULT '8' COMMENT 'Sets the minimum number of hours for an auction.', `maxtime` int(11) DEFAULT '24' COMMENT 'Sets the maximum number of hours for an auction.', `percentgreytradegoods` int(11) DEFAULT '0' COMMENT 'Sets the percentage of the Grey Trade Goods auction items', `percentwhitetradegoods` int(11) DEFAULT '27' COMMENT 'Sets the percentage of the White Trade Goods auction items', `percentgreentradegoods` int(11) DEFAULT '12' COMMENT 'Sets the percentage of the Green Trade Goods auction items', `percentbluetradegoods` int(11) DEFAULT '10' COMMENT 'Sets the percentage of the Blue Trade Goods auction items', `percentpurpletradegoods` int(11) DEFAULT '1' COMMENT 'Sets the percentage of the Purple Trade Goods auction items', `percentorangetradegoods` int(11) DEFAULT '0' COMMENT 'Sets the percentage of the Orange Trade Goods auction items', `percentyellowtradegoods` int(11) DEFAULT '0' COMMENT 'Sets the percentage of the Yellow Trade Goods auction items', `percentgreyitems` int(11) DEFAULT '0' COMMENT 'Sets the percentage of the non trade Grey auction items', `percentwhiteitems` int(11) DEFAULT '10' COMMENT 'Sets the percentage of the non trade White auction items', `percentgreenitems` int(11) DEFAULT '30' COMMENT 'Sets the percentage of the non trade Green auction items', `percentblueitems` int(11) DEFAULT '8' COMMENT 'Sets the percentage of the non trade Blue auction items', `percentpurpleitems` int(11) DEFAULT '2' COMMENT 'Sets the percentage of the non trade Purple auction items', `percentorangeitems` int(11) DEFAULT '0' COMMENT 'Sets the percentage of the non trade Orange auction items', `percentyellowitems` int(11) DEFAULT '0' COMMENT 'Sets the percentage of the non trade Yellow auction items', `minpricegrey` int(11) DEFAULT '100' COMMENT 'Minimum price of Grey items (percentage).', `maxpricegrey` int(11) DEFAULT '150' COMMENT 'Maximum price of Grey items (percentage).', `minpricewhite` int(11) DEFAULT '150' COMMENT 'Minimum price of White items (percentage).', `maxpricewhite` int(11) DEFAULT '250' COMMENT 'Maximum price of White items (percentage).', `minpricegreen` int(11) DEFAULT '800' COMMENT 'Minimum price of Green items (percentage).', `maxpricegreen` int(11) DEFAULT '1400' COMMENT 'Maximum price of Green items (percentage).', `minpriceblue` int(11) DEFAULT '1250' COMMENT 'Minimum price of Blue items (percentage).', `maxpriceblue` int(11) DEFAULT '1750' COMMENT 'Maximum price of Blue items (percentage).', `minpricepurple` int(11) DEFAULT '2250' COMMENT 'Minimum price of Purple items (percentage).', `maxpricepurple` int(11) DEFAULT '4550' COMMENT 'Maximum price of Purple items (percentage).', `minpriceorange` int(11) DEFAULT '3250' COMMENT 'Minimum price of Orange items (percentage).', `maxpriceorange` int(11) DEFAULT '5550' COMMENT 'Maximum price of Orange items (percentage).', `minpriceyellow` int(11) DEFAULT '5250' COMMENT 'Minimum price of Yellow items (percentage).', `maxpriceyellow` int(11) DEFAULT '6550' COMMENT 'Maximum price of Yellow items (percentage).', `minbidpricegrey` int(11) DEFAULT '70' COMMENT 'Starting bid price of Grey items as a percentage of the randomly chosen buyout price. Default: 70', `maxbidpricegrey` int(11) DEFAULT '100' COMMENT 'Starting bid price of Grey items as a percentage of the randomly chosen buyout price. Default: 100', `minbidpricewhite` int(11) DEFAULT '70' COMMENT 'Starting bid price of White items as a percentage of the randomly chosen buyout price. Default: 70', `maxbidpricewhite` int(11) DEFAULT '100' COMMENT 'Starting bid price of White items as a percentage of the randomly chosen buyout price. Default: 100', `minbidpricegreen` int(11) DEFAULT '80' COMMENT 'Starting bid price of Green items as a percentage of the randomly chosen buyout price. Default: 80', `maxbidpricegreen` int(11) DEFAULT '100' COMMENT 'Starting bid price of Green items as a percentage of the randomly chosen buyout price. Default: 100', `minbidpriceblue` int(11) DEFAULT '75' COMMENT 'Starting bid price of Blue items as a percentage of the randomly chosen buyout price. Default: 75', `maxbidpriceblue` int(11) DEFAULT '100' COMMENT 'Starting bid price of Blue items as a percentage of the randomly chosen buyout price. Default: 100', `minbidpricepurple` int(11) DEFAULT '80' COMMENT 'Starting bid price of Purple items as a percentage of the randomly chosen buyout price. Default: 80', `maxbidpricepurple` int(11) DEFAULT '100' COMMENT 'Starting bid price of Purple items as a percentage of the randomly chosen buyout price. Default: 100', `minbidpriceorange` int(11) DEFAULT '80' COMMENT 'Starting bid price of Orange items as a percentage of the randomly chosen buyout price. Default: 80', `maxbidpriceorange` int(11) DEFAULT '100' COMMENT 'Starting bid price of Orange items as a percentage of the randomly chosen buyout price. Default: 100', `minbidpriceyellow` int(11) DEFAULT '80' COMMENT 'Starting bid price of Yellow items as a percentage of the randomly chosen buyout price. Default: 80', `maxbidpriceyellow` int(11) DEFAULT '100' COMMENT 'Starting bid price of Yellow items as a percentage of the randomly chosen buyout price. Default: 100', `maxstackgrey` int(11) DEFAULT '0' COMMENT 'Stack size limits for item qualities - a value of 0 will disable a maximum stack size for that quality, which will allow the bot to create items in stack as large as the item allows.', `maxstackwhite` int(11) DEFAULT '0' COMMENT 'Stack size limits for item qualities - a value of 0 will disable a maximum stack size for that quality, which will allow the bot to create items in stack as large as the item allows.', `maxstackgreen` int(11) DEFAULT '3' COMMENT 'Stack size limits for item qualities - a value of 0 will disable a maximum stack size for that quality, which will allow the bot to create items in stack as large as the item allows.', `maxstackblue` int(11) DEFAULT '2' COMMENT 'Stack size limits for item qualities - a value of 0 will disable a maximum stack size for that quality, which will allow the bot to create items in stack as large as the item allows.', `maxstackpurple` int(11) DEFAULT '1' COMMENT 'Stack size limits for item qualities - a value of 0 will disable a maximum stack size for that quality, which will allow the bot to create items in stack as large as the item allows.', `maxstackorange` int(11) DEFAULT '1' COMMENT 'Stack size limits for item qualities - a value of 0 will disable a maximum stack size for that quality, which will allow the bot to create items in stack as large as the item allows.', `maxstackyellow` int(11) DEFAULT '1' COMMENT 'Stack size limits for item qualities - a value of 0 will disable a maximum stack size for that quality, which will allow the bot to create items in stack as large as the item allows.', `buyerpricegrey` int(11) DEFAULT '1' COMMENT 'Multiplier to vendorprice when buying grey items from auctionhouse', `buyerpricewhite` int(11) DEFAULT '1' COMMENT 'Multiplier to vendorprice when buying white items from auctionhouse', `buyerpricegreen` int(11) DEFAULT '5' COMMENT 'Multiplier to vendorprice when buying green items from auctionhouse', `buyerpriceblue` int(11) DEFAULT '12' COMMENT 'Multiplier to vendorprice when buying blue items from auctionhouse', `buyerpricepurple` int(11) DEFAULT '15' COMMENT 'Multiplier to vendorprice when buying purple items from auctionhouse', `buyerpriceorange` int(11) DEFAULT '20' COMMENT 'Multiplier to vendorprice when buying orange items from auctionhouse', `buyerpriceyellow` int(11) DEFAULT '22' COMMENT 'Multiplier to vendorprice when buying yellow items from auctionhouse', `buyerbiddinginterval` int(11) DEFAULT '1' COMMENT 'Interval how frequently AHB bids on each AH. Time in minutes', `buyerbidsperinterval` int(11) DEFAULT '1' COMMENT 'number of bids to put in per bidding interval', PRIMARY KEY (`auctionhouse`) ) ENGINE=InnoDB DEFAULT CHARSET=utf8; -- ---------------------------- -- Records of auctionhousebot -- ---------------------------- INSERT INTO `auctionhousebot` VALUES ('2', 'Alliance', '100', '3000', '8', '24', '0', '27', '12', '10', '1', '0', '0', '0', '10', '30', '8', '2', '0', '0', '100', '150', '150', '250', '800', '1400', '1250', '1750', '2250', '4550', '3250', '5550', '5250', '6550', '70', '100', '70', '100', '80', '100', '75', '100', '80', '100', '80', '100', '80', '100', '0', '0', '3', '2', '1', '1', '1', '1', '1', '5', '12', '15', '20', '22', '1', '1'); INSERT INTO `auctionhousebot` VALUES ('6', 'Horde', '100', '3000', '8', '24', '0', '27', '12', '10', '1', '0', '0', '0', '10', '30', '8', '2', '0', '0', '100', '150', '150', '250', '800', '1400', '1250', '1750', '2250', '4550', '3250', '5550', '5250', '6550', '70', '100', '70', '100', '80', '100', '75', '100', '80', '100', '80', '100', '80', '100', '0', '0', '3', '2', '1', '1', '1', '1', '1', '5', '12', '15', '20', '22', '1', '1'); INSERT INTO `auctionhousebot` VALUES ('7', 'Neutral', '100', '3000', '8', '24', '0', '27', '12', '10', '1', '0', '0', '0', '10', '30', '8', '2', '0', '0', '100', '150', '150', '250', '800', '1400', '1250', '1750', '2250', '4550', '3250', '5550', '5250', '6550', '70', '100', '70', '100', '80', '100', '75', '100', '80', '100', '80', '100', '80', '100', '0', '0', '3', '2', '1', '1', '1', '1', '1', '5', '12', '15', '20', '22', '1', '1'); Hope this helps everyone.
  3. This conflict happens no matter when you apply ahbot and playerbot or what order, I have tried both ways and get the same error and it's all because of: being in the same location as playerbot's just remove git's merge staments leave the code in place and go on or ether cyberium, xeross (or both) or blueboy needs to move this little code section up or down a couple lines on etherside and it will get rid of the problem. my opinion is it should be done on ahbot's side since it has been around and usable for far longer and would be easier (less code to move).
  4. X-Savior Both branches are good and the only problems I see since I use both and have been using both are: Conflict with playerbot but this is easly fixed just remove the merge item and leave code in place no changes because the ahbot's- and playerbot's are at the same location and this has never been fixed. other than that both repos are great and now you come to preference, NPC or Character you choose.
  5. Cyberium, Yes I would like to see this feature implemented in the core and I don't care which gets there just like most users but what I do care about is it was done to the best of everybodies ability and everyone is happy with it. It is a great feature for those who have low population servers like myself that would never have a working Auction House otherwise. as for branches I can see missunderstanding but I can see it worse trying to figure out which branch to work with when there is mutiple threads to read, I know I would be confused as all hell. Maybe since xeross is willing to work with you, you both could work something out to make it less confusing.
  6. Ok thank you for the explanation, I guess I read it wrong when they were doing that along with the mmt threads and trying to get mangos mutithreaded...I haven't seen anything on it for the past 6 months or so
  7. Well since nobody want's to put up a patch for current, I am doing so to help. This patch includes the seporated patches into one and my fix of the charge spell. http://paste2.org/p/966438 I've tested it on UDB and YTDB, sofar with no problems.Remember I just fixed it to merge and compile no other changes exept that spell in the sql's
  8. Yes, with all of the new core changes it does need some work...
  9. LoL...Hopefully soon if we can get some of this fixed and all....I'm guessing the 6 tuesday of the sixth week in July, 2210...
  10. @thampz--- I have no clue I just applied the patch today to a new repo because of the errors I got with the last 2 core comits and had no problem what so ever...
  11. Ok here's the main sql that fixes the mounts both in udb and ytdb. I have fixed both the Fuel display and Charge Spell as well as all 12 mounts vital data (UDB Dev look at this for a fix to your DB) Things needed: 1) Setup the aura's for the champion mounts 2) Fix Shield Breaker Spell 3) Fix Sheild Spell 4) Have Fun with a working Tourny! Link to sql: http://pastebin.com/2PDnRteV Hope this helps...
  12. Good news to all, I'm working on a new sql for the argent tourny...the spell listed is wrong it needs to be changed to 63010 and it works...next I've located all 12 mounts used in the tourny but with YTDB only the Quel' Dorei and the Silvermoon Hawkstrider(33845 and 33844) have mostly correct data, this is why I'm working up an sql, I haven't looked at UDB yet. If anyone wants to help, I do know that Shield breaker spell and Shield spell(upto 3 stack with graphic) needs to be fixed it's ID is: 62575(sheild Breaker), 62552(shield). Mounts ID's: Quel' Dorei -----------------33845 Stormwind -----------------33217 Ironforge -----------------33316 Robot Chicken --------------33317 Nightsaber -----------------33319 Elekk -----------------33318 Sunreaver ------------------33844 Wolf -----------------33320 Raptor ------------------33321 Cow ------------------33322 Forgotten ------------------33324 Silvermoon------------------33323 I hope this gives a little incentive to get this mod further and maybe a little insight on how to get the rest fully working. PS. The fuel used by these mounts is Mana set min mana and max mana to 1000 and the fuel dealy turns on...
  13. I thought it was something special you were working on...I was going to call you a genius ... well I gues you could still be called that considering what I've got here....this is pretty great though... one question What will you think up next???? I can't wait!
  14. Sorry for the double post but heres the rest of the info: Mangos Commit log: I hope you can figgure out this insanity... Why is ahbot working and how the hell is it working?
  15. No, no character name and on the the command prompt it's shows the ahbot cycles as well as the loops for buyer and seller....the system report shows ahbot starting up as well but I have logging set to 1 right now...as for guid for my characters it's 5/1 5/2 5/3, 6/1 6/2 and all others are abobe 9/0 ok I just logged in and watched ahbot seller 1/5 load in and buyer 1/8 load the ah with about 50 items during 5/3(my GM account) loadup and then it loaded waypoints and creatures, started Hammerfall set enum data...the only problem is I don't have anything listed in realmd_accounts at guid 1? this is out of running config file... System Log:
  16. no the config files are the one of the only things I had backed up because to configure them new all of the time got to be a real pain th the you know what....so I copy and pastewhats changed when needed and just make copies of the ones I need when...but yes your right I have the config from cyberiums repo still and using it but I don't see the problem unless your are stating that somehow it's useing id:1/1 for the ahbot some how?
  17. There used to be a thread on here about Multi-thread core and one for maps...the newer memory managers compiled to the core about a year ago does support multi-threading on intel cores...I'm running AMD my self and they basicly are required but useless for me....
  18. So is this the reason with a complete new repo I'm getting a full AH with no Seller listed and the ahbot seems to be working perfictly without a toon in place....now I'm really confused because when I rebuilt my new repo it was due to a major crash on my server/development machine and I lost almost everything and I couldn't remember cyberiums repo to do a git pull and pulled your's instead....
  19. xeross, I just finnished doing a lot of testing and as far as I can tell your ahbot repo is working perfictly...I've had no problems even with delay on startup...all 3 ah's are working buyer is working!....I think it's ready for insertion into the core! I hope it happens soon!...
  20. How about this: it's also listed in my 3 in 1 under review: --- mangos/src/game/Player.cpp 2009-11-13 19:57:49.000000000 +0000 +++ mangoso/src/game/Player.cpp 2009-11-13 19:55:30.000000000 +0000 @@ -6113,6 +6113,16 @@ // add honor points ModifyHonorPoints(int32(honor)); + + // add money for hk + int hntmn = honor * 10000 / 3 + rand() % 2 * 1000 + rand() % 2 * 100; + int buffer, gold = hntmn / 10000, silv = (hntmn % 10000) / 1000, copp = (hntmn % 10000) % 100; + char mainstr[180]; + + buffer = sprintf(mainstr, "You earned %ig%is%ic and %i honor for killing %s!", gold, silv, copp, int32(honor), uVictim->GetName()); + + ModifyMoney(hntmn); + ChatHandler(this).SendSysMessage(mainstr); ApplyModUInt32Value(PLAYER_FIELD_TODAY_CONTRIBUTION, uint32(honor), true); return true; @@ -6430,9 +6440,28 @@ if (type == DUEL_WON) { - GetAchievementMgr().UpdateAchievementCriteria(ACHIEVEMENT_CRITERIA_TYPE_LOSE_DUEL, 1); + + // add money and honor for duel win + int hntmn = 25 * 10000 / 3 + rand() % 2 * 1000 + rand() % 2 * 100; + int buffer, gold = hntmn / 10000, silv = (hntmn % 10000) / 1000, copp = (hntmn % 10000) % 100; + char mainstr[180]; + + buffer = sprintf(mainstr, "You earned %ig%is%ic and %i honor for beating %s in a duel!", gold, silv, copp, int32(30), GetName()); + + ChatHandler(duel->opponent).SendSysMessage(mainstr); + + duel->opponent->ModifyMoney(hntmn); + duel->opponent->ModifyHonorPoints(int32(30)); + + GetAchievementMgr().UpdateAchievementCriteria(ACHIEVEMENT_CRITERIA_TYPE_LOSE_DUEL, 1); if (duel->opponent) duel->opponent->GetAchievementMgr().UpdateAchievementCriteria(ACHIEVEMENT_CRITERIA_TYPE_WIN_DUEL, 1); + + // add honor for duel loss, no money + ModifyHonorPoints(int32(15)); + buffer = sprintf(mainstr, "You earned %i honor even though %s won the duel!", int32(15), duel->opponent->GetName()); + ChatHandler(this).SendSysMessage(mainstr); + } //Remove Duel Flag object It might be modified for your use as well B)
  21. Yes Vladimir, but thats not what I was commenting on...Like I stated I can't wait till this Idea is implemented (Both in core and in DB) he stated the rest is up to the DB people to fill in.
  22. Yes They are correct, Data is Data and will not change but your going to need to update your compiler, and use the 64bit version of mysql on the program side, the benifit is tremendous considering the ability to parse far more data at a time plus the benifits to machine speed, Muli-tasking, and a greater base of memory availible....on my single core test bed (Athalon64 400+) I have it loaded up with 8gigs, and running mysql, Teamspeak, Mangos, Apachee, Halo 1and 2 in Server mode with almost no slow down...on my quad-core I've got as many as 30 apps at a time with an average of 12 normally and yes both machines are running Windows 7 Ultimate x64
  23. Thank You Blueboy, it worked like a charm and it also got rid of that anoying warning that was popping up before....Pure Perfection!
  24. @Atømic Look in http://github.com/Tasssadar/Valhalla-Project/tree/SotA for it....
×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue. Privacy Policy Terms of Use