next »

[Smart]

Ok, so I've had some trouble installing B3, but finally I got it to work.
I installed everything on my dedicated server, which is running Windows Server 2003.
I've issued the command 'iamgod' successfully, and am a god admin now.
But the server's having one issue: It doesn't give any welcome messages, nor does it response to any Xlrstats commands.
Is it just something I missed, or something that went wrong?

I can provide any additional data required by mail or PM.

[Courgette]

if anything goes wrong, you should find ERROR messages in your b3.log

[Smart]

Ahh well, I just rechecked everything, and somehow the port changed back to the standard one.
Now everything's working, except for the greet.
Whenever I connect it doesn't pop up any messages, nor does it welcome me back to the server 

I also can't seem to run multiple B3 bots, meaning only our RO server will be streamed, and our AW won't. I tried multiple config files (b3.xml and b3-2.xml) but that didn't work either (made Windows Server go nuts with error messages)

[Courgette]

about the welcome plugin : it won't show you messages meant for newcomers as you are well known on your server.
Look at your b3.log for lines having "WelcomPlugin" in them. This should show you how the bot react upon new user connections.

about running multiple bots, you can specify a différent config file with :
b3_run -c <my other config file>

[Smart]

about the welcome plugin : it won't show you messages meant for newcomers as you are well known on your server.
Look at your b3.log for lines having "WelcomPlugin" in them. This should show you how the bot react upon new user connections.

about running multiple bots, you can specify a différent config file with :
b3_run -c <my other config file>

Well, that doesn't work.
I got two shortcuts on the desktop: both are going to the C:\Python\Lib\Site-packages\B3\run.py and are using the B3_run -c b3-aw.xml for the AW server, and b3-ro.xml for the RO server.
All other things are working fine now, but i can't run multiple b3 bots =/

[Courgette]

you cannot start the bot making shortcut to C:\Python\Lib\Site-packages\B3\run.py
Make shortcuts to

Code:

python.exe b3_run.py -c "some config"

[Smart]

Ok, so i put:

Code:

C:\Python25\python.exe b3_run.py -c b3-aw.xml

as the target
and:

Code:

C:\Python25\

as the directory where the script starts in.
Still it doesn't run. And I bet my question must sound very stupid as well
I tried changing the start directory to

Code:

C:\Python25\Lib\site-packages\b3

But, that doesn't work either. My CoD UO is installed in

Code:

C:\Program Files\Call of Duty

and B3 is located at:

Code:

C:\Python25\Lib\site-packages\b3

I also set up both B3s to connect to another database, the All Weapon connects to B3-aw, and the RO to the normal B3 db. I really suck at Python, so I don't really know how to solve this =/ I can only run one B3 bot, and that one runs fine, so how do I run 2?

What do I need to change?

[Bakes]

try

Code:

C:\Python25\python.exe b3_run.py -c @b3/conf/b3-aw.xml

[Smart]

Well, that doesn't work either.
The DOS screen pops up, for like 1 second, and then immediatly shuts down.

EDIT: does it matter where I put the shortcuts?

I can also run B3 using the 'run.py' file, and then it works fine, but it's only possible to be run on one server  

[Courgette]

what you can do to see what error message is written in the DOS window that popups is :

• open a DOS console (<windows>+R, type 'cmd')
• in the DOS console, type :
  
  • cd C:\Python25\
  • python.exe b3_run.py -c c:\somewhere\b3-aw.xml

Then post the error message you should have when the bot fails to start.

The location of shortcuts does not matter.

running run.py won't allow you to specify other config file that the default one.

[Smart]

Code:

Microsoft Windows [Version 5.2.3790]
(C) Copyright 1985-2003 Microsoft Corp.

C:\Documents and Settings\Administrator.DIRECTCL-AC7B7C>cd C:\Python25\

C:\Python25>python.exe b3_run.py -c C:\Python25\Lib\site-packages\b3\conf\b3-aw.
xml
Starting www.BigBrotherBot.com (b3) v1.2.1 [nt] (Daniel)

Using config file: C:\Python25\Lib\site-packages\b3\conf\b3-aw.xml
Traceback (most recent call last):
  File "b3_run.py", line 8, in <module>
    load_entry_point('b3==1.2.1', 'console_scripts', 'b3_run')()
  File "C:\Python25\Lib\site-packages\b3\run.py", line 121, in main
    run(config=options.config)
  File "C:\Python25\Lib\site-packages\b3\run.py", line 100, in run
    b3.start(config)
  File "C:\Python25\lib\site-packages\b3\__init__.py", line 98, in start
    console = parser(conf)
  File "C:\Python25\lib\site-packages\b3\parser.py", line 161, in __init__
    self.log = b3.output.getInstance(logfile, self.config.getint('b3', 'log_leve
l'))
  File "C:\Python25\Lib\site-packages\b3\output.py", line 120, in getInstance
    handler.doRollover()
  File "C:\Python25\lib\logging\handlers.py", line 131, in doRollover
    os.rename(self.baseFilename, dfn)
WindowsError: [Error 32] The process cannot access the file because it is being
used by another process
Error in atexit._run_exitfuncs:
Traceback (most recent call last):
  File "C:\Python25\lib\atexit.py", line 24, in _run_exitfuncs
    func(*targs, **kargs)
  File "C:\Python25\lib\logging\__init__.py", line 1354, in shutdown
    h.flush()
  File "C:\Python25\lib\logging\__init__.py", line 731, in flush
    self.stream.flush()
ValueError: I/O operation on closed file
Error in sys.exitfunc:
Traceback (most recent call last):
  File "C:\Python25\lib\atexit.py", line 24, in _run_exitfuncs
    func(*targs, **kargs)
  File "C:\Python25\lib\logging\__init__.py", line 1354, in shutdown
    h.flush()
  File "C:\Python25\lib\logging\__init__.py", line 731, in flush
    self.stream.flush()
ValueError: I/O operation on closed file

This is the log file.
It's kinda weird

[Courgette]

I bet you did not set a different bot log file in b3-aw.xml than the one set in b3.xml

2 instances of the bot cannot use the same log file.

example:

Code:

<set name="logfile">b3-aw.log</set>

[Smart]

Ah yes!
Working like a charm now

Thanks for your help/ Bedankt voor je hulp.
Keep on running this great bot, I'm sure everybody likes it