cyberium

Can you give me an exemple of what yellow item you expect to see? Because i have too this behavior but i can't find any good yellow items to be sellable. Oranges one have same situation except for Elementium Bar. Who know what's BBCODE is used to show wowhead tooltips?

I wish you too have a nice learning time. No it's not necessary finaly. See you.

Thanks for the feedback i will try to correct these little errors. @mrelfire "is their anyway to not make modifications around the same place between ahbot and playerbot?" Yes i will investigate this long time anoying stuff... I still didn't look on the ahbuyer algorithm. I just adapted some of the line. I will do my best when the new_ahbot is enought stable. Please i want you to share with us theses settings AuctionHouseBot.Alliance.Price.Ratio = 50 AuctionHouseBot.Horde.Price.Ratio = 50 AuctionHouseBot.Neutral.Price.Ratio = 50 To make the best default value and have the realist price on the ah. Tell me if you see any mistake... Be free to correct my sentence on the settings explanation. @ Xerross. It's sad day for mangos community... I hope you change your mind. See you bro.

I often code after 18h till 2h. Yes its redundant but i choose to let original method instead adding additional test. Just because i dont know if this method is called often or not to avoid any performence issue. Update On my repo : 1 - Added separate conf file (ahbot.conf) 2 - moved src files into subfolder. GCC brokken iam working on it. Update GCC build restored.

Yes at first stage. Have you applied the change to 2 method on Item.cpp? Look at my repo on items.cpp method SetEnchantmentNoUpdate() and SetItemRandomPropertiesNoUpdate() These 2 method call setstate() normaly who need real gui... update : Implemented Ratio for all Factions. Now you can define differents amounts of items on every faction. Greetings

It's due to recent change on AuctionHouseMgr.h. My repo is updated and olso trailing space are corrected. Here is the patch for 10437 if you prefer.

Build on GCC restored. Comment of new settings added in mangosd.conf.dist.in Just VCPROJ file is modified due to one moved file accidentaly in Visual Studio GUI... Anyway you are right i need to avoid the use of git commit -am directly.... Yes the idea of use a separate conf file is the best. And no i still prefer to edit a file instead of DB. So for the near futur i will work to make all settings in separate files. Greetings.

Thank, updated! What merging do you refer? Anyway try by pulling direcly from my repo. Not yet implemented but started. You simply will be able to modify AuctionHouseBot.FACTION.Ratio to value represente percentage of items in section AuctionHouse.Items.Amount.COLORS If you set AuctionHouseBot.FACTION.Ratio to 0 then ah in FACTION will be disabled. Sorry didn't have time to test it before, i will try to figure out. Erf sory, but has i say is only beta so do not be to fast to porting it. Don't understaind what you are refering. mangosd.conf? I only forget to set correct default value for general use in place of my test value... Until we do not touch configuration value by using method sWorld.setConfig(); we can reload it. I don't think so because editing DB is not so easy, especialy when we have lot of values like in actual ahbot branch. I will upload soon correct mangos.conf.dist.in with settings explanation.

Nice to see that Xeross. So now has i promise my (new_ahbot) is updated. What's new? - No more DB Data needed (all setting is in mangosd.conf) - Amount of all important items class can be now configured separatly. - More than 90% of ahbot core code are rewrited to optimise it. - There is now 2 speed for auction add core. Normal speed is less cpu using than ever. - No ingame command are actualy implemented - Still in beta some feature are in progress like faction ratio. - Of course it's player account free... Need to be tested if you have time.

You are right, this is new thread about little modified AHBOT from Narcissium. But when you will see my code (part of it can be seen on new_ahbot branch) you will find so many difference. Actually just buyer is untouched (will be when i finish seller) Olso there is 3 version for now about this code. Xeross one, my ahbot version and new code. So new people don't know what to do in many case. New thread will be at the start oriented for the new code. Objective will be to integrate it in the core. Xeross and all develloper are welcome to improve it or give their opinions. History : Xeross open this thread with his branch of ahbot. He work on it to implement some new function. He maintain it. He is away. Other posted patch to maintain it. I start by post patch too. I open my branch. I improve ahbot with no player account feature. I start new branch with new core function more optimized and some modifications. Xeross is back and whant to update is repo. But his repo is very outdated and in place to take actual ahbot branch he prefer to wrote his own code. So actualy there is too many difference between our ahbot branch to make easy merge. So i let him implement the "no player account feature" but he can count on my support. I will just update my ahbot branch until he have done his repo. Hope i am not wrong

Thanks for feedback. I will invoke your help soon on testing new revision For the next version you will have some new itemclass tuning feature, i reintroduced tradegood items but not only this class, all "usable" class are now configurable. (done) All settings will be done on mangos.conf instead DB. (in work) Iam trying to make easy the setting of AHBot but there is too much options... The code will probably be pushed on the middle of next week. Because of big changes to the code I think I need to open a new thread, so be aware

Hello Guys. My repo update : Branch ahbot : Merged with 10407. Branch new_ahbot: - Merged with 10407. - Restored Build with GCC (tested on debian 5). Reminder : "ahbot branch" is slightly modified xeross branch to avoid use of player account. "new_ahbot branch" have lot of change and optimisations but still in beta mode. (code will be improved soon and i will give more explanations).

Just tried to merge, and faced too much conflit so i will later try to patch your repo instead to merge. My repo will be adjusted. Anyway i have not lot of time until next week so be patient

Try to add #include "AuctionHouseMgr.h" in AuctionHouseBot.h I will push it soon

Hello, i pushed new tree with new version of ahbot on my repo. I need some beta tester to improve it. What's new : - Completly rewrited addAuction method. - Completly rewrited AHBConfig class. - More selective on what item needed to be added. - Add items by amount instead by percent. - All items selled will be replaced by another one of same quality in next scan. - And some more improvement like new auction speedup. What i need? Some feedback about object in AH. Iam not sure if it was a good idea to group itemsTradeGood with normal items. So i need to know if all usual items are still present and in good percentage. Olso the price of items need to be checked. ( anyway you still can modify de percentage of it in DB ) Warning this version need a new database structure so i rename it to let you keep old one for reversing... The code is probably not cleaned (trailing space, or indent problem) don't be rude it's still in devellopement See you. http://github.com/cyberium/mangos/commits/new_ahbot

Oh! I didn't notice you are trying to compile it from linux. I have not set any linux environnement to test my patch for now. I will try to find why ObjectGuid isn't declared ine your case if i have time tomorrow.

-> SkullDrago : yes it's probably my fault i will try to correct my repo. -> Unkeluke : Thanks for your good explanations -> Ki2007, I can't reproduce your error. Be sure there is nothing wrong with your patching method or with pull/merge.

Why i must use it instead of std::vector? Is for portablility? Optimisation? Olso how to initialise this object with 0? ACE_Vector<uint32, 7> MyVector; Edit Has it's not mandatory to use ACE_Vector... So NVM.

Clear mrelfire you are certainly So you are right that's the price to be more precise. But if i add an multiplicator variable will you be happy? (applyable for all value choosen)

Yes. that what i mean. The difference is in the code actualy between grey and greyTradeGoods items. I do'nt know why for now so if anyone can explain me why i cannot simply merge theses two kind together. (grey is an exemple....) Yes i think too is more conveniant to define how much items of what quality we want.

I dont understaind what period you talk about. To be more clear, greytg = 200 whitetg= 1500 greentg = 2500 bluetg = 500 ... grey = 0 white = 1500 .... orange = 1 So in this exemple AHBot will fill AH with exact items you need. If you buy one , it will be replaced next scan.

Hello guys, For my next rev i wondered if it would be easier to choose the number of objects we wish to see in the AH rather than the percentage. Indeed you will notice that if you want one or two orange objects it's not yet possible. Put 1% for 5000 objects give us 50 oranges ... What do you think? You prefer the percentage system?

Iam afraid it's not that simple, we must send real objectguid now instead of uint32 one. Here is the AHBot patch for rev 10363 Repo is updated. Like always feedback are welcome

Yes Vladimirmangos love to give us work Iam implementing the new way. But will take time due to new objectguid system.

It's ok for me. If Xeross want to integrate my code I have no problem with that. By cons I think modifying the operation of some functions and add some others like Xeross do. We just need to be more organized and have a common repo.