Ahbot enabling?

rename the file from .conf.dist to .conf

sorry I misread that, you say that you have enabled both.... in the conf ?

1 minute ago, antz said:

sorry I misread that, you say that you have enabled both.... in the conf ?

yes. In the etc directory now I have an "ahbot.conf" file, where I have 

AuctionHouseBot.Seller.Enabled = 1

and

AuctionHouseBot.Buyer.Enabled = 1

Btw, I also left 

AuctionHouseBot.CharacterName  = ""

as the comments, above, say

#    Default "" (No owner)

Ciao

U

world-server.log tells me 

2017-05-21 18:25:59 Initialize AuctionHouseBot...
2017-05-21 18:25:59 AHBOT is Disabled. Unable to open configuration file ../etc/ahbot.conf. 
 

But the conf file is there, and with the right privileges...

Without me changing anything else, ahbot started working. Meaning, mangosd now "can" read ahbot.conf.

I must conclude that, previously, the conf file appeared busy by whatever other process.

Anyhow, solved (by itself) now

I got the problem again.

Yesterday I rebuilt the whole Zero thing to include playerbots.

After the rebuild, again I have

AHBOT is Disabled. Unable to open configuration file ../etc/ahbot.conf. 

in the world-server.log file

Needless to say, ahbot.conf staid there since before, nothing changed, no permissions changed etc etc

There seems to be no other process tampering with it.

Where's the catch??

Thanks

U

I think I found where the issue stays. Didn't solve it yet though.

After rebuilding, 

if I launch mangosd as a normal binary (./mangosd), ahbot.conf is properly read-in and all works

If I launch mangosd as a service (as I configured it earlier as per wiki instructions) ahbot.conf is NOT read-in !

Any clue how to fix this?

Thanks ciao

U

Maybe related to the -c option which gives only mangosd.conf.

There should be extra options for ahbot conf file.

Tal'

Sounds logical.

Yet, I am positive this *did* work, without -c option for ahbot.conf, as a service at least once before. Odd i'ni?

I'll try and add the -c opt and feedback here

ciao

U

And by the way, aiplayerbot.conf *is* loaded (in service-mode) without specifying it inside the service file, only ahbot.conf is not...

That sounds... even more weird.

Tal'

For now I suspended research on this. I'm launching realmd and mangosd as ordinary deamons, each one on its own Screen instance. 

This bug report has been copied over from your topic @iltuocapo

Quote

 

I tested the above and this also proved to be the solution to my problem of launching ahbot/aiplayerbot with mangosd as a service

WorkingDirectory=/home/mangos/zero/zero_server/bin

 

I have the same problem as you and do not seem to have a solution or a type of support for the creators ...

I found something but I do not know if it works.

https://github.com/ike3/mangosbot/issues/45

I took a look at this old problem: https://bitbucket.org/lordpsyan/trinitycore-patches/issues/313/ike3-playerbots-playerbot-system-is
Open my configuration file and code my complete path within /Users/username/server-directory/bin/aiplayerbot.conf
And now it seems to work. My world server is processing the robots at this moment ...

If you build playerbot module, the ahbot will not work. The reason is playerbot module also contains a buggy ahbot submodule, which interferes with the actual ahbot. So the ideea is simple: if you want ahbot, disable playerbots from building.