[Pogamut-list] Yylex errors preventing bots from working.

ZL221 pogamut-forum at diana.ms.mff.cuni.cz
Wed Mar 28 21:57:38 CEST 2012


Yylex errors preventing bots from working.

Author: ZL221

Hi all,

I'm one of a group of students trying to work with Pogamut to implement a bot. This bot seeks out a CivilianBot before leading it to a predetermined waypoint.

However on ALL but one of our machines, our code starts returning the following warnings, seemingly when communication begins between bots.

(GuideBot-SPOSH) [ WARNING ] 20:45:28.104   State MSG_PLR unprocessed: {
(GuideBot-SPOSH) [ WARNING ] 20:45:28.172   State MSG_PLR unprocessed: C
(GuideBot-SPOSH) [ WARNING ] 20:45:28.172   State MSG_PLR unprocessed: r
(GuideBot-SPOSH) [ WARNING ] 20:45:28.172   State MSG_PLR unprocessed: o
(GuideBot-SPOSH) [ WARNING ] 20:45:28.172   State MSG_PLR unprocessed: u
(GuideBot-SPOSH) [ WARNING ] 20:45:28.172   State MSG_PLR unprocessed: c
(GuideBot-SPOSH) [ WARNING ] 20:45:28.172   State MSG_PLR unprocessed: h
(GuideBot-SPOSH) [ WARNING ] 20:45:28.173   State MSG_PLR unprocessed: e
(GuideBot-SPOSH) [ WARNING ] 20:45:28.672   State MSG_PLR unprocessed: d
(GuideBot-SPOSH) [ WARNING ] 20:45:28.672   State MSG_PLR unprocessed: F
(GuideBot-SPOSH) [ WARNING ] 20:45:28.672   State MSG_PLR unprocessed: a
(GuideBot-SPOSH) [ WARNING ] 20:45:28.672   State MSG_PLR unprocessed: l
(GuideBot-SPOSH) [ WARNING ] 20:45:28.672   State MSG_PLR unprocessed: s
(GuideBot-SPOSH) [ WARNING  ] 20:45:28.672   State MSG_PLR unprocessed: e
(GuideBot-SPOSH) [ WARNING ] 20:45:28.672   State MSG_PLR unprocessed: }

(The above are not meant to be links, they are inside square brackets)

These clearly spell out {Crouched False} (the parser ignores whitespace), and the only place in the SVN I could find this is in /trunk/project/Main/PogamutUT2004/src/main/java/cz/cuni/amis/pogamut/ut2004/communication/messages/gbinfomessages/Player.java , where {Crouched False} was implemented in revision 4228 on the 26th May 2011.

We are completely at a loss as to what is causing this; we believe we are using up-to-date files, and the machine that is working should be using the same files as the others.

Is there a known workaround here?

Thanks,
Z

-- 
Reply Link: <http://diana.ms.mff.cuni.cz/main/tiki-view_forum_thread.php?forumId=4&comments_parentId=935#form>





More information about the Pogamut-list mailing list