xeross155

Why do you need a patch it has been added to MaNGOS now.

So far I've finished cleaning up and modifying (Still needs a character), I will push it to my branch tomorrow (GitHub isn't configured on my workstation at the moment and it's 11:23PM). ~Xeross

Congratulations on making it into the master branch

I am currently cleaning up the AHBot, moving config settings to the global config parser, etc. After this I will look into making it work without a real player.

Currently you need to set a GUID on the seller part of the auction, so we'd need to add some kind of special value to that for the AHBot, let me finish my adaptions and improvements and we'll move on after that.

They need to be related to something, else the client doesn't know how to display them, so best would be a virtual character called AHBot or something.

Hmm well trying to implement the normal LoadFromDB into the ahbot but it's complaining about the queryholder. Edit: Currently optimizing the MinimalLoadFromDB, to see if there's anything we can rip out.

Whadya change ?

Hmm I wonder how we can make auction work without a player behind them, that's practically impossible as it's implemented around players

I think the client connects to the voice server on a seperate port (Or the worldd pipes everything to the voice server and back), the old ascent voice chat code should hold some info.

The problem with a vehicle is that your character is "entering" the vehicle, and with the eye you Possess the eye you do not enter it.

People tend to say once you know C++ you'll be able to program in any of the most-used languages.

I'll give it a go on my server, does it work with AHBot ?

Ok, but still wondering what would be proper implementation that would be added to master

We should just use the existing database load function over the MinimalLoad one.

Seems this is still not working properly, any idea what's causing it, some kind of aura not being parsed or something ?

These kinds of patches really make the future of MaNGOS look a lot brighter, I will add it to my server on the next patching run.

Perhaps you can add some kind of trick on the map restart to release the mutexes, there must be a way to release them.

There must be some ScriptDev2 call to force the objective update

Again a big thanks for creating this patch and gathering the data, it's working perfectly

As said before I will attempt to fix it, just have a little patience here I also have a real life.

If it's a query holder you should be able to get the uint32 value from it, but I'll look into it as promised.

Once my test server is back online I'll try fixing it

I think they removed it because nothing used MinimalLoadFromDB anymore, can't be too hard to use the normal loadFromDB in ahbot. Oh yes and my ahbot table is INSERT INTO `auctionhousebot` (`auctionhouse`, `name`, `minitems`, `maxitems`, `mintime`, `maxtime`, `percentgreytradegoods`, `percentwhitetradegoods`, `percentgreentradegoods`, `percentbluetradegoods`, `percentpurpletradegoods`, `percentorangetradegoods`, `percentyellowtradegoods`, `percentgreyitems`, `percentwhiteitems`, `percentgreenitems`, `percentblueitems`, `percentpurpleitems`, `percentorangeitems`, `percentyellowitems`, `minpricegrey`, `maxpricegrey`, `minpricewhite`, `maxpricewhite`, `minpricegreen`, `maxpricegreen`, `minpriceblue`, `maxpriceblue`, `minpricepurple`, `maxpricepurple`, `minpriceorange`, `maxpriceorange`, `minpriceyellow`, `maxpriceyellow`, `minbidpricegrey`, `maxbidpricegrey`, `minbidpricewhite`, `maxbidpricewhite`, `minbidpricegreen`, `maxbidpricegreen`, `minbidpriceblue`, `maxbidpriceblue`, `minbidpricepurple`, `maxbidpricepurple`, `minbidpriceorange`, `maxbidpriceorange`, `minbidpriceyellow`, `maxbidpriceyellow`, `maxstackgrey`, `maxstackwhite`, `maxstackgreen`, `maxstackblue`, `maxstackpurple`, `maxstackorange`, `maxstackyellow`, `buyerpricegrey`, `buyerpricewhite`, `buyerpricegreen`, `buyerpriceblue`, `buyerpricepurple`, `buyerpriceorange`, `buyerpriceyellow`, `buyerbiddinginterval`, `buyerbidsperinterval`) VALUES (2, 'Alliance', 1000, 2000, 8, 48, 0, 27, 12, 10, 1, 0, 0, 0, 10, 30, 8, 2, 0, 0, 100, 150, 150, 250, 800, 1400, 2250, 2750, 3250, 5550, 6250, 8550, 9250, 11550, 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), (6, 'Horde', 1100, 2200, 8, 48, 0, 27, 12, 10, 1, 0, 0, 0, 10, 30, 8, 2, 0, 0, 100, 150, 150, 250, 800, 1400, 2250, 2750, 3250, 5550, 6250, 8550, 9250, 11550, 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), (7, 'Neutral', 100, 200, 8, 24, 0, 27, 12, 10, 1, 0, 0, 0, 10, 30, 8, 2, 0, 0, 100, 150, 150, 250, 800, 1400, 2250, 2750, 3250, 5550, 6250, 8550, 9250, 11550, 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); Seems fine

Perhaps storing the achievement data in the database would be an improvement ?