Closed GoogleCodeExporter closed 9 years ago
Original comment by lowerlo...@gmail.com
on 29 Nov 2009 at 5:15
You can already move the screen? I don't understand what this issue is for.
Original comment by AHeinerm
on 30 Nov 2009 at 1:54
Yeah since you can already move the screen via the gui, I think this issue
might mean
support for moving the screen via code, like a Game::setScreenPosition(Position
p)
function. I tried modifying the values read by getScreenX/Y, but that had no
luck.
Anyway I don't see how AIs could benefit from this so its low priority, but it
might
be an interesting feature to add at some point down the road if AIs have some
sort of
location based focus/attention algorithm, and want to show what part of the map
they
are focusing on.
Original comment by lowerlo...@gmail.com
on 30 Nov 2009 at 5:51
Hmm, there is a Center Map View command im UMS, maybe we could immitate that.
Original comment by goo...@teabix.com
on 30 Nov 2009 at 10:04
... This is about moving the screen via code of course ;)
I have started to write a replay watcher that mimics real casters (like
Artosis) -
its using a speaking Library and tries to identify the replay (using a
webservice and
maybe a sequence of actions or the replay itself) to put the game into context.
You
can also ask questions along the way that the ai caster will try to answer
(simple
ones of cause). And I would love it to use existing build order databases or
wiki's
to get information. But for it to be successful i need to be able to move the
screen
to relevant positions where the action takes place :)
Original comment by wizuffeg...@gmail.com
on 30 Nov 2009 at 3:58
Added in r1893.
Original comment by lowerlo...@gmail.com
on 1 Jan 2010 at 5:58
Original issue reported on code.google.com by
wizuffeg...@gmail.com
on 29 Nov 2009 at 4:29