Forum: PogamutUT2004

Problems with Responsive Bot

Posted by aiden on Sun 13 of Jun, 2010 19:11 CEST
Hi,

I have a problem with the Responsive Bot. It doesn't act as it should. It only greet sometimes a new player in his field of view and when it is injured, it never tries to run away.

It seems as the messages are being lost. I'm working with a comercial version of UT.Before I was working with Pogamut 2 and i had no problem to receiving messages. By the way, is there any 'In' Log as in Pogamut 2 where i can control the messages from the plataform?

Thank you.
Reads: 26565
Link
Posted by rudolf.kadlec on Mon 14 of Jun, 2010 13:31 CEST
Strange ... Have you applied the Unreal Tournament patch 3369? (it is included in the installer)
Link
Posted by aiden on Mon 14 of Jun, 2010 14:16 CEST
yes, i have applied the patch, i couldn't conect to private servers without him and i do. In fact, the responsive bot works fine sometimes.

I got this log yesterday, maybe it helps:

(ResponsiveBot1) WARNING 22:09:32.078 State MSG_DAM unprocessed: H
(ResponsiveBot1) WARNING 22:09:32.078 State MSG_DAM unprocessed: i
(ResponsiveBot1) WARNING 22:09:32.078 State MSG_DAM unprocessed: t
(ResponsiveBot1) WARNING 22:09:32.078 State MSG_DAM unprocessed: F
(ResponsiveBot1) WARNING 22:09:32.078 State MSG_DAM unprocessed: a
(ResponsiveBot1) WARNING 22:09:32.078 State MSG_DAM unprocessed: l
(ResponsiveBot1) WARNING 22:09:32.078 State MSG_DAM unprocessed: s
(ResponsiveBot1) WARNING 22:09:32.078 State MSG_DAM unprocessed: o
(ResponsiveBot1) WARNING 22:09:32.078 State MSG_DAM unprocessed: }
(ResponsiveBot1) SEVERE 22:09:32.093 UT2004Parser: Can't parse next message: 65533 (caused by: 65533)
ParserExceptionUT2004Parser: Can't parse next message: 65533 (caused by: 65533)
at cz.cuni.amis.pogamut.base.communication.parser.impl.yylex.YylexParser.parse(YylexParser.java:88)
at cz.cuni.amis.pogamut.base.communication.translator.impl.WorldMessageTranslator.getEvent(WorldMessageTranslator.java:109)
at cz.cuni.amis.pogamut.base.communication.mediator.impl.Mediator$Worker.run(Mediator.java:287)
at java.lang.Thread.run(Thread.java:619)

I always receive these warning messages, that notify about unprocessed messages, is it normal?
Link
Posted by michal.bida on Mon 14 of Jun, 2010 14:36 CEST
Hi,
first can you send whole log? This seems to be just a part of it. Second - what Pogamut version are you using? Latest? What OS ? Win XP? This bug is really weird. Seems that something is exported from GameBots but it is not parsed correctly in client - this should never happen.
Link
Posted by aiden on Mon 14 of Jun, 2010 14:48 CEST
Hi,
I am sorry, but i do not have the complete log. I had only copied the different part, the rest has only more warning messages about unprocessed messages.
I am using the last version on Win XP.

Thanks for your interest
Link
Posted by michal.bida on Mon 14 of Jun, 2010 15:02 CEST
Last = 3.0.11, right?

Have you updated GameBots as well (it is enough to have them checked in 3.0.11 installer).

michal
Link
Posted by michal.bida on Mon 14 of Jun, 2010 15:09 CEST
Another question regarding your concrete version of UT2004.

Is your UT2004 localized? Or it is plain ENG(lish) version?

We've been wondering about "Falso" which is not correct word for the boolean state "false", it seems like 'false' has been rewritten by UnrealScript into "Falso" which (we believe) is not possible for ENG version of UT2004 we're (in Prague) working with.

Best,
Michal
Link
Posted by aiden on Mon 14 of Jun, 2010 15:17 CEST
Yes, I have cheked that my version is the 3.0.11. The version of GameBots, i don't know how to check it, but i have installed them with the 3.0.11 installer.
Anything else that i can check?


You have right, my version is spanish version, could that make the messages change?
I will try to change, and i will tell you. But it is weard because i have worked before with this version and Pogamut 2 and havent got any problem.
Link
Posted by michal.bida on Mon 14 of Jun, 2010 15:32 CEST
Ok, we've caught the bug ... strange is that it was working for Pogamut 2! Wow!

It would be the best to reinstall your UT2004 to ENG version,
we've been unable to localize where UT2004 is hiding these consts :-(
and it would be currently problematic to start support all UT2004 localizations :-)

Best,
Michal
Link
Posted by aiden on Mon 14 of Jun, 2010 17:38 CEST
Great!
I have changed into the ENG version and now everything goes fine.
Thanks a lot.
Link