mrelfire

I suspect we have few ideas why he is looking for a fake players system

I am using still few days xeross155 AH, no problems except this boring message of 0 guid.

looks good, great job.

I recompile this morning with today's xeros155 repo and I have these strange errors

Item::AddToUpdateQueueOf - GetPlayer didn't find a player matching owner's guid

(0)!

Item::AddToUpdateQueueOf - GetPlayer didn't find a player matching owner's guid

(0)!

Item::AddToUpdateQueueOf - GetPlayer didn't find a player matching owner's guid

(0)!

Item::AddToUpdateQueueOf - GetPlayer didn't find a player matching owner's guid

(0)!

Item::AddToUpdateQueueOf - GetPlayer didn't find a player matching owner's guid

(0)!

Item::AddToUpdateQueueOf - GetPlayer didn't find a player matching owner's guid

(0)!

strange isn't it ?

I have now in xeross155 ah these debug output

AHBOT> Running buyer loop

AHBOT> Running seller loop

AHBOT> Running buyer loop

AHBOT> Running seller loop

AHBOT> Running buyer loop

AHBOT> Running seller loop

AHBOT> Running buyer loop

AHBOT> Running seller loop

AHBOT> Running buyer loop

AHBOT> Running seller loop

I was wondering how to remove them please ?

Actually, I think it might be best to borrow an idea from blueboy and have AHBot use its own, separate config file.

By this method, you do not need to worry with changes to mangosd.conf and can allow more room to have all settings moved into a config file instead of the database.

The SQL table was a good idea, today we begin to have :

mangods.conf

scriptdev.conf

realmd.conf

playerbot.conf

and another one for ahbot ?

SQL is your friends

Actually, I think it might be best to borrow an idea from blueboy and have AHBot use its own, separate config file.

By this method, you do not need to worry with changes to mangosd.conf and can allow more room to have all settings moved into a config file instead of the database.

The SQL table was a good idea, today we begin to have :

mangods.conf

scriptdev.conf

realmd.conf

playerbot.conf

and another one for ahbot ?

SQL is your friends

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.

.

The idea is how to have different numbers for neutral or horde house ?

before we had 3 different lines in the sql tables

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.

slight problem with merging in VC100

small question:

how to make different items regarding alliance / neutral for axample ?

I am currently implementing cyber's changes for the non-character ahbot into mine, making some decent progress, will look at the buyer

Edit

Guess what I did

Repository updated and need for a character removed, both buyer and seller are tested on both ally and horde.

Credits added for cyberium and version bumped to x004

I have tryed to create a patch but it seems I received a lot of more code thant expected (more thant 10 times the size of an "auctionhouse.patch")

Did I make a mistake ?

Can anyone confirm that my branch only populates the Alliance AH ?

The last time I used yours, It was only populate the "7". Due to the fact I do not change my config between yours and cyberium, I suspect a litle "glitch" occured.

Now I switch to cyberium repo

I second this statement. No problems with new_ahbot branch so far.

I am also using it, => love it

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).

so the new ahbot will be the reference (after the beta mod)

I have a strange behavior on the xeross155'AH, now I have only the neutral working, and nothing into the 2 other "race" AH, did I miss something ?

Shouldn't we go to under review process ?

It should be now in the "hands" of Vladimir .

xeross, thank you for considering cyberium's code and I hope the two of you will finally make possible the realization of the dream many long-time AHBot fans have had of seeing this most useful project officially added to the core.

Both of you collaborating on AHBot is a chance to set the example for the entire Core Mods community of what can be accomplished when people work together and complement each others' strengths.

I look forward, with much excitement, to what your teamwork will bring!

it is like a dream coming to the reality

Table was renamed to "auction" in this commit

search the core for the query and change auctionhouse to auction

I do agree but 10254 commit is before 10385, it is just to aware than an auctionhouse has been missed

1/

Once the branches are merged than we should get under review, my branch has a lot of new optimizations and stuff, in other words better code quality than it was before.

Updated to 10385

perfect did you implement the generic seller like cyberyum ?

2/ I have compiled

and also I have some strange errors on the console:

AHBOT> Running seller loop

AHBOT> Running buyer loop

AHBOT> Running seller loop

AHBOT> Running buyer loop

AHBOT> Running seller loop

AHBOT> Running buyer loop

AHBOT> Running seller loop

AHBOT> Running buyer loop

SQL: UPDATE auctionhouse SET buyguid = '135',lastbid = '946' WHERE id = '1026094

'

SQL ERROR: Table 'characters_tlk.auctionhouse' doesn't exist

auctionhouse' has been changed do we have to do something ?

are we going to under review for Vladimir ? with which redepository ?

is it under x64 ?

I am not a mathematician

the % is just to quickly increase the "basic" rules to a biggest numbers. the multiplicator is quite a very good idea.

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.

today we have a minimum and maximum amount, and the % of items is related to this range.

It is easier to manage, for example tomorrow if I want to double the items, just to change the maximum.

With your proposal, I will have to go to each items and make the modifications.

Regarding the timeline, I thought the items was introduced after I go below the minimum range chosen (this is what I used the wrong term "period")

I hope I am clear

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?

perhaps first a system when you put a valor (like 0) you have nearly these items (like 0)

your idea will be difficult: is it 50 per which period ?

oh no, an other one :)

I am joking, hope Vladimir will implement ahbot soon in the core system

A crash is not so much important at the beginning, my main concern is the deconnection problem.

Unfortunately I did not see anybody else than me having this problem.

I have forgotten to say I have compiled under VC100 in X64

Is it because I am using a X64 bites compilation ?