Thanks for the bug report, will be fixed.

We have bug tracking system here: Pogamut Mantis

Login: pogamut
Password: pogamut

I'll put information on our pages - thanks for the question.

Best,
michal

Nice

I was poking around deeper into the architecture*.

Anyway, I stumbled upon POGAMUT_UT2004_OBSERVER_HOST("pogamut.ut2004.server.host") in PogamutProperty, line 35. Don't know if this is intentional, could be.

I realize this is, in any case, trivial, although it could lead to frustration in some cases.
Do you want us to report bugs of this kind, if encountered, on the Mantis? I suppose the 'trivial' severity category fits this kind of issue.

In any case, thanks for Pogamut. I'm starting to appreciate the complexity of what you're trying to achieve

• (I was trying to find more info on logging and the incredible number of default loggers instances. I was trying to disable console handling. It seems like the addDefaultConsoleHandler is called twice, both in SingleUT2004BotRunner.startAgent() and UT2004ServerFactory.newAgent(). Seems like every LogCategory has two handlers associated with them as standard but I haven't delved into whether this affects anything..)

Cheers,
Simon

Hi Simon!

Thanks for pointing that out! Nifty bug in case of observer

Will be fixed in the future release (probably this week)

Best, Jakub aka Jimmy

Yes, loggers are troubling the Pogamut.

Put it simply - the problem lies in the Pogamut team as not everybody is keen on properties.
The CORRECT way to deal with logging lies inside 'property' file. As you can see, people from
Pogamut team does not obey that (sorry comrades, but that's true...).

The best is to call bot.getLogger().setLevel(Level....); inside prepareBot() (for now).

I hope to resolve this issue around summer (there are currently more problematic things
we must attend to like 'agent modules').

I'm sorry for the inconveniences.

Best,
Jakub aka Jimmy