Skip to content
Grepobot

Beyond automation

Commander

Two things: a planner that gets the timing right, and the overview the game charges an advisor for.

Landing on the second

You choose the arrival time. Grepobot works backwards to the departure, and — this is the part that matters — recomputes it from live travel speed every time it reads, rather than once when you planned it. A number calculated at planning time is wrong by the time it is used, because the things that feed it move.

The overview the game gates

Grepolis puts its command overview behind the Administrator advisor. The Commander window rebuilds it — in the game's own visual language — for everybody: movements with filter chips for incoming and outgoing attacks, support in and out, returns, spies, sieges and revolts; where every army on the account actually is; and your own towns sorted by the next hostile arrival, with hack, pierce, distance and naval defence shown raw rather than averaged into a single misleading number.

Planned attacks appear as rows in it, so what you intend and what is already moving are one picture rather than two.

On the map

Red swords and minutes-to-impact on your towns under attack, blue swords on towns you are attacking, shields where you have support standing. The same classifier decides all of it, so a command cannot be one thing in the list and another on the map.

What it does not do

  • The planner does not enforce the game's own warning about attacking an alliance member. Check who you are pointing at.
  • It plans and it shows. Deciding to attack is yours: nothing here picks a target for you.