GrepoSuite Wiki — User Guide

The Auto Build module is an automatic construction queue manager that keeps your cities building around the clock. Create building queues per city or apply preset templates, and the engine handles resource checks, dependency validation, and build commands every cycle. GrepoSuite ships with six preset templates: Land Offense, Naval Offense, Defensive, Max Resources, Quick Start, and New World.

Interface

• Build Queues
• Templates
• Overview
• History
• Settings

The Build Queues tab is the main workspace where you add, reorder, and remove buildings for each city. Templates provides preset and custom templates you can apply with one click. Overview gives an at-a-glance summary of all cities (queue size, next building, slots, status). History logs completed builds. Settings controls cycle timing.

Settings Reference

Setting	Description	Default
Min interval	Minimum minutes between build cycles (randomized with max)	5 min
Max interval	Maximum minutes between build cycles	10 min
Auto-complete free buildings	Automatically finishes buildings with less than 5 minutes remaining (free, no gold cost). Checks every 30 seconds across all cities	On
Template	Preset or custom building template assigned to a city	None
Per-city enabled	Toggle building automation per individual city	On
Global enabled	Master toggle for all cities	Off

⚡ Auto-Complete Free Buildings

In Grepolis, when a building has less than 5 minutes remaining in its construction timer, you can complete it instantly for free (no gold cost). GrepoSuite automates this:

• Every 30 seconds, the module scans all active building orders across all your cities
• If any building has ≤5 minutes remaining, it sends the free completion command automatically
• This works for all cities simultaneously — no town switching needed
• The feature is enabled by default and can be toggled in the Settings tab
• Only completes when the cost is 0 (free) — will never spend gold accidentally

This speeds up construction significantly, especially in the early game where build times are short and many buildings fall under the 5-minute threshold.

The Auto Farm module automates resource collection from farming villages. It runs on a configurable timer, cycling through all your cities and claiming resources from their assigned villages. This is one of the most essential modules — consistent farming is the foundation of resource income in Grepolis. The interface is a single panel with status indicator, countdown timer, power button, time selector, loot type selector, statistics, and settings checkboxes.

Interface

Single panel (no tabs). Contains a status indicator with pulsing dot, a countdown timer showing time until next claim, a power button to start/stop, time interval buttons, loot type selector, session and lifetime statistics, and settings checkboxes for auto-start and skip behavior.

Settings Reference

Setting	Description	Default
Time interval	Farming cycle timing (4 preset options)	5/10 min
Loot type	Normal (safe) or Demand (more resources, worse mood)	Normal
Auto-start	Start farming automatically on game load	Off
Skip 30%	Randomly skip ~30% of cycles for human-like patterns	Off

The Auto Timing module is a precision attack coordination tool that helps you land attacks at the exact same second. Essential for organized alliance strikes where multiple players need simultaneous arrivals at a target city. You set target arrival times, and the module automatically cancels and resends attacks until they land within your acceptance window — handling the tedious retry loop for you.

Interface

Single modal window (380px wide). Opens via Ctrl+Shift+T or the toolbar button. Contains input fields for target times, margin, max retries, acceptance range, and start/stop controls.

Settings Reference

Setting	Description	Default
Target time(s)	Desired arrival time(s) in HH:MM:SS format, comma-separated	—
Margin	Tolerance window for timing (0–60 seconds)	5s
Max retries	Maximum cancel-and-resend attempts (1–999)	50
Acceptance before	Seconds early that is still acceptable (0–60)	5s
Acceptance after	Seconds late that is still acceptable (0–60)	5s

The Cave Storage module automatically stores excess silver in the cave (hide) to protect it from enemy raids. Silver is the most vulnerable resource in Grepolis — enemies can steal it in attacks. This module monitors your silver levels and moves surplus into the cave where it cannot be raided, triggering when warehouse silver reaches 95% capacity.

Interface

• Overview
• Settings ⚙
• Cities
• History 📋

The Overview tab shows warehouse and cave status for all cities with color-coded indicators. Settings controls the module toggle, storage amount, and interval. Cities lets you include or exclude specific cities. History logs all storage actions.

Settings Reference

Setting	Description	Default
Enabled	Master toggle for the module	Off
Amount per cycle	Silver to store each time the module runs (100+)	500
Check interval	Minutes between storage checks (1–120)	5 min
Excluded cities	List of cities excluded from automatic storage	None

The Auto-Recruit module handles automatic troop recruitment across all your cities. It monitors barracks and harbor queues and fills empty slots based on your configuration. Each city can have its own independent recruitment queue for land and naval units, and you can set spells and continuous repeat recruitment to keep your armies growing non-stop.

Interface

• Queues
• Settings
• Cities
• Logs

The Queues tab is where you configure barracks and harbor unit queues per city, set spells, and toggle repeat mode. Settings controls the global check interval. Cities lets you toggle cities active or excluded. Logs shows recruitment actions taken by the module.

Settings Reference

Setting	Description	Default
Check interval	Minutes between recruitment checks (1–120)	5 min
Barracks queue	Per-city list of land units to recruit	Empty
Harbor queue	Per-city list of naval units to recruit	Empty
Spells	One or more god spells to cast before recruiting (per city). You can activate Population Growth and Spartan Training simultaneously.	None
Wait for all spells	If enabled, the module will not recruit until there is enough favor for all selected spells. If disabled, it casts whichever spells it can afford and recruits anyway.	Off
Repeat (∞)	Continuous recruitment toggle per unit entry	Off
Excluded cities	Cities excluded from automatic recruitment	None

The Auto-Culture module automates cultural event management to help you expand your city count faster. Culture points are required to found or conquer new cities, and the primary way to earn them is by running celebrations. This module monitors your resources, battle points, and gold, then automatically starts the appropriate celebrations in each city based on your configuration.

Interface

• Overview 📊
• Cities 🏙
• Settings ⚙
• History 📋

The Overview tab shows status per city with color-coded indicators (🟢 Active, ⚡ Ready, ⏳ Waiting). Cities lets you toggle specific celebration types per city via colored badges. Settings controls interval, battle point reserve, and gold reserve. History logs all celebrations started.

Settings Reference

Setting	Description	Default
Check interval	Minutes between checks (1–120)	10 min
Min BP reserve	Minimum battle points to keep (won't spend below this)	0
Min gold reserve	Minimum gold to keep (won't spend below this)	0
Per-city events	Which celebration types are enabled per city	All enabled
Excluded cities	Cities fully excluded from culture automation	None
Orpheus auto-move	Automatically move Orpheus hero to cities with active celebrations	Enabled
If another hero is assigned	What to do when target city has another hero: Replace or Skip	Replace hero
Stagger celebrations for Orpheus	Launch celebrations one at a time in a chain so Orpheus visits every city before each celebration finishes (see below)	Disabled

🎵 Orpheus Hero Auto-Movement

Orpheus is a special hero with a chance to double the culture points earned when a celebration finishes while he is assigned to that city. The Auto-Culture module can automatically move Orpheus between your cities to maximize this bonus.

How It Works

1. Each cycle, the module checks all active celebrations and their finish times.
2. It uses the hero travel time reported by the game (a flat value, same to any city) to determine if Orpheus can arrive before a celebration finishes.
3. It picks the soonest-finishing celebration that Orpheus can reach before it finishes (with a 2-minute safety margin).
4. If Orpheus is already assigned to another city, the module unassigns him first, then sends him to the target.
5. If Orpheus is already traveling, the module waits for him to arrive — heroes cannot be reassigned mid-transit.
6. Once the celebration finishes, the next cycle moves Orpheus to the next best target.

Hero Conflict Resolution

When Orpheus needs to move to a city that already has another hero assigned, you have two options:

Option	Behavior
Replace hero (default)	The other hero is unassigned first, then Orpheus is sent. Use this for maximum culture output.
Skip city	The city is skipped and Orpheus is sent to the next viable target. Use this if you have heroes in strategic positions you don't want to disturb.

🔄 Celebration Staggering

By default, Auto-Culture launches all celebrations at once. This means they all finish at the same time, and Orpheus can only be in one city when they complete. With Stagger celebrations for Orpheus enabled, the module launches celebrations one at a time in a chain, timed so each one finishes just after Orpheus has traveled from the previous city.

Stagger Example (world speed ×5)

Step	What happens
1	Festival started in City A. Orpheus is assigned to City A.
2	~3h 36min later: Festival started in City B (timed so it finishes 72min after City A's festival).
3	City A's festival finishes — Orpheus doubles the culture points. Module moves Orpheus to City B.
4	City B's festival finishes — Orpheus doubles again. Module moves to City C.
...	Chain continues for all cities.

Result: instead of doubling culture in 1 out of 7 cities, Orpheus doubles all 7. The total cycle takes slightly longer but produces significantly more culture points.

Note: Celebration durations are automatically detected from the game and adapt to world speed. Travel time is also read directly from the game API.

Orpheus Settings

Setting	Description	Default
Orpheus auto-move	Enable or disable automatic hero movement	Enabled
If another hero is assigned	Replace hero (unassign other) or Skip city (find next target)	Replace hero
Stagger celebrations	Chain celebrations so Orpheus visits every city (see above)	Disabled

Requirements

• You must have the Orpheus hero unlocked in your account.
• Works with all celebration types: Festivals, Olympics, Triumphal Processions, Theater plays.
• Travel time is automatically read from the game (flat value, same to any city, adapts to world speed).

The Auto-Research module automates technology research across your cities. Create research queues per city or apply preset templates, and the engine handles academy level checks, research point validation, resource costs, and dependency verification. Five preset templates are available: Land Offense, Naval Offense, Economy, Defense, and Conquest.

Interface

• Overview
• Queues
• Templates
• Cities
• Settings
• History

The Overview shows all cities with academy level, research points, slots, and queue status. Queues is the main configuration area for per-city research order. Templates provides 5 presets plus custom templates. Cities toggles active/excluded. Settings controls timing. History logs completed research.

Settings Reference

Setting	Description	Default
Cycle interval	Minutes between research checks (1–120)	2 min
Research queue	Per-city ordered list of technologies to research	Empty
Template	Preset or custom template (5 presets available)	None
Excluded cities	Cities excluded from research automation	None

The Auto-Trade module manages automatic resource trading between your cities using a Provider/Consumer role system. Provider cities send their excess resources to Consumer cities that need them. The module calculates trade routes, respects market capacity and merchant availability, and handles all logistics automatically. Essential for larger empires where manually balancing 20+ cities is impractical.

Interface

• Overview
• Cities
• In Transit
• Settings
• Logs

The Overview shows resource levels and trade capacity per city. Cities is the main configuration area where you assign roles. In Transit shows active shipments with real-time countdowns. Settings controls cycle timing and trade parameters. Logs records all trade actions.

Settings Reference

Setting	Description	Default
Cycle interval	Minutes between trade checks (1–120)	5 min
Provider reserve	Resources to keep in Provider cities (per resource type)	2000
Min shipment	Minimum resources per trade (avoids tiny shipments)	100
Per-city role	Provider, Consumer, or Ignore for each city	Ignore
Consumer limits	Max resources a Consumer city will accept (per type)	Unlimited

The Auto-Village module handles automatic unlocking and upgrading of farming villages. It uses battle points to unlock locked villages and upgrade them to maximum level (6), ensuring your villages always yield the best possible resources. Works hand-in-hand with Auto Farm: Auto-Village upgrades the villages while Auto Farm collects from them.

Interface

Single panel (no tabs). Contains 3 stat boxes showing Available BP, Max Level Progress (X/Y at level 6), and Locked Villages count. Below the stats: a BP reserve input field, start/pause/force controls, and an activity log.

Settings Reference

Setting	Description	Default
BP Reserve	Minimum battle points to keep (won't spend below this)	0

The Auto-Dodge module is the most powerful defensive system in GrepoSuite. It detects incoming attacks, analyzes unit composition from travel time signatures, and automatically executes a multi-step defense sequence: sending your troops to a safe city, activating militia, and cancelling the support so troops return after the attack passes. It also supports Telegram notifications and colony ship detection with special handling.

Interface

• Overview
• Settings
• History

The Overview tab shows detected attacks grouped by city, with origin info, attacker name, arrival time, unit analysis, and per-attack configuration. Settings controls check interval, safety margin, spy check, and Telegram integration. History provides color-coded logs of all dodge actions.

Settings Reference

Setting	Description	Default
Check interval	Seconds between attack scans (1–120)	5s
Safety margin	Seconds before impact to send troops (20–300)	30s
Spy check	Verify target city is not on vacation by sending and cancelling a spy. Disable this if you experience issues with uncancelled spies	On
Telegram Chat ID	Chat ID for real-time attack notifications via @grepoattack_bot	None
Per-city dodge	Enable/disable dodge per attacked city	On
Target city	Where to send troops for each city (auto-selected to nearest same-island city)	Nearest
Militia	Activate defensive militia before impact	On
Militia offset	Seconds before impact to activate militia (1–5). Increase if militia activates too late due to timer imprecision	1s
Arrival offset	When troops return relative to attack impact	+1s

🔎 Spy Check (Target Verification)

Before sending troops to a safe city, the module can verify the target is actually available (not on vacation or beginner protection) by sending a spy and immediately cancelling it. Here is how it works:

• A spy is sent from your attacked city to the target city
• If the game returns a vacation/protection error, the target is marked as unavailable and the module automatically tries the next nearest city
• If the spy sends successfully, it is cancelled within seconds — your spy returns home
• Results are cached for 5 minutes, so repeated attacks don't trigger multiple spy missions to the same target
• For your own cities as targets, no spy is needed (they can't be on vacation)

If the spy check causes problems (e.g., not enough silver in the cave, or spies not being cancelled properly), you can disable it in Settings. The dodge will still work — it just won't verify the target city's availability beforehand.

🛠 How the Dodge Sequence Works

When an attack is detected, the module executes this precise sequence:

1. Detection — scans for incoming attacks every N seconds (configurable)
2. Analysis — identifies the slowest unit in the attack based on travel time signatures, checking all possible speed bonus combinations including research (meteorology, cartography), buildings (lighthouse), items (speed boots), and siren speed bonuses (+2% per siren, up to 100%)
3. Target selection — automatically selects the best dodge target (own city on same island > other player's city on same island > nearby cities)
4. Send troops — at (impact − safety margin) seconds, sends all troops as support to the safe city. Land and naval units are sent separately to avoid transport capacity issues
5. Activate militia — activates the defensive militia before impact (configurable offset, default 1 second)
6. Cancel support — at the calculated midpoint, cancels the support command so troops turn around and return home after the attack has passed. If cancellation fails, it retries up to 5 times
7. Troops return — troops arrive back at your city after the attack, ready to defend against follow-up waves

The Night Sleep module automatically pauses all module activity during your configured sleeping hours to simulate natural human behavior. It picks a random time within your configured window each day, so your "sleep" never starts or ends at the exact same minute. During sleep, all modules pause except Auto-Dodge which continues protecting your cities. Essential for long-term account safety.

Interface

• Status 📊
• Settings ⚙
• History 📋

The Status tab shows today's and tomorrow's scheduled sleep/wake times. Settings controls the sleep and wake time windows. History logs all sleep/wake cycles. A floating indicator is always visible showing current state.

Settings Reference

Setting	Description	Default
Sleep start (from)	Earliest time sleep can begin	22:00
Sleep start (to)	Latest time sleep can begin	00:00
Wake start (from)	Earliest time wake can begin	06:00
Wake start (to)	Latest time wake can begin	08:00

The Bandit Camp module automates attacks against bandit camp events in Grepolis. These recurring events require military attacks to clear and reward resources, battle points, and event prizes. The module detects active events, checks your troop population, sends attacks automatically, and collects rewards — saving you from tediously clicking through 100+ bandit camp levels.

Interface

• Overview
• Settings ⚙
• Logs 📋

The Overview shows troop counts, population values, and current module status. Settings controls the minimum population threshold and check interval. Logs records all attacks and rewards.

Settings Reference

Setting	Description	Default
Min population	Minimum total offensive unit population to attack	50
Check interval	Minutes between event checks (1–30)	2 min

The Gold Market module monitors the premium gold-to-resource exchange capacity across all seas in your game world. It tracks available exchange capacity in real time and alerts you via Telegram when favorable conditions are detected. Whether you are an active gold trader or simply want to know when it is a good time to sell resources, this module ensures you never miss an opportunity.

Interface

• Overview
• Settings ⚙
• Logs 📋

The Overview shows premium exchange availability per sea with progress bars for wood, stone, and iron (green = available capacity, red = full). Settings controls Telegram integration, capacity threshold, and check interval. Logs records all alerts sent.

Settings Reference

Setting	Description	Default
Telegram Chat ID	Your Telegram chat ID for notifications (@grepoattack_bot)	None
Min capacity	Minimum exchange capacity per resource to trigger alert	1000
Check interval	Minutes between exchange checks (1–60)	5 min

The Anti Gold module prevents enemy players from using premium gold to instantly buy troops (Militia, Divine Envoys, etc.) by keeping their cities under constant attack. In Grepolis, a player cannot use gold to purchase troops if an attack is arriving within 5 minutes. By sending a small attack (e.g., 1 Fire Ship) every 4–5 minutes, this module effectively locks the enemy out of premium features for as long as the routes are active.

How it Works

1. You define attack routes: origin city → target city + unit type + quantity
2. Each active route sends an attack every 4:00 to 4:59 (randomized interval)
3. Since attacks always arrive within 5 minutes, the enemy cannot use gold the entire time
4. Multiple routes can run simultaneously against different (or the same) targets
5. When started, the first attack is sent immediately; subsequent attacks follow the randomized interval

Interface

• Route configuration form
• Active routes list with live countdown
• Logs

The route form lets you select an origin city (your own), enter a target city ID (enemy), choose a unit type, and set the quantity. The routes list shows all configured routes with their status (active/paused), attacks sent counter, and a live countdown to the next attack. Logs record every attack sent and any errors.

Editing a Route

Click the ✎ edit button on any route to change the unit type or quantity. If the route was active, it will be automatically stopped, updated, and restarted with an immediate first attack.

Settings Reference

Parameter	Description	Default
Origin city	Your city that sends the attack	—
Target city ID	Enemy city ID to attack	—
Unit type	Which unit to send (Fire Ship, Slinger, etc.)	sword
Quantity	Number of units per attack	1
Interval	Randomized between 4:00 and 4:59 (not configurable)	~4:30

Scan any island on the map to view detailed information about farm towns, player cities, resources, and free colonization spots — without needing a city on that island. Perfect for planning expansions and scouting enemy positions.

Interface

• Coordinate Input — Enter island X and Y coordinates
• Island Header — Shows coordinates, island ID, type, resources, and free spots
• Villages Table — All farm towns with name, expansion level, offered and demanded resources
• Cities Table — Player cities with name, player, alliance, and points

Automatically trade resources with farm villages when the exchange ratio is favorable. Each farm village offers one resource and demands another. When you trade, you send the demanded resource and receive the offered one, multiplied by the current trade ratio. The ratio degrades after each trade and recovers over time.

How It Works

1. The module checks all your farm village relations and their current trade ratios.
2. For each village where the ratio meets your minimum threshold, it checks trade capacity.
3. If your city has enough of the demanded resource (above your reserve minimum), a trade is executed.
4. The amount is automatically clamped so received resources never overflow your storage — no resources are wasted.

Interface

• Settings Tab — Configure minimum ratio, resource reserve, check interval, and engine on/off
• Cities Tab — Enable or disable trading per city
• Logs Tab — Trade history showing what was sent, received, and the ratio used

Settings Reference

Setting	Description	Default
Min Ratio	Minimum trade ratio to accept. 1.0 = even exchange, 1.25 = profit, 0.65 = loss. Only trades at or above this ratio.	1.0
Reserve	Don’t send a resource if the city would have less than this amount remaining.	500
Interval	Minutes between trade cycles. Lower = more frequent checks.	10 min
Excluded Cities	Per-city toggle to disable trading from specific cities.	None

The centralized settings panel groups all global preferences in one place. Instead of configuring language, Telegram, and other global options across multiple modules, everything is accessible from a single panel.

Interface

• License — View your license key, status (Active / Trial / Suspended), tier, expiration date, bound player, and a button to buy or upgrade your plan.
• Language — Change the interface language for all modules. Supports: Spanish, English, French, German, Italian, Portuguese, and Dutch.
• Smart Pause — Toggle the human activity detection system on/off and adjust the idle delay (how long after your last mouse/keyboard activity before modules resume).
• Telegram — Enter your Telegram Chat ID once here and it will be used by Auto-Dodge and Gold Market for notifications. Includes a test button to verify your setup.
• Contact — Quick links to Discord, Telegram support bot, and email.

Settings Reference

Setting	Description	Default
Language	Interface language for all modules	Auto-detected from game URL
Smart Pause	Pause modules when mouse/keyboard activity is detected	On
Idle delay	Seconds of inactivity before modules resume after Smart Pause triggers	3 seconds
Telegram Chat ID	Global Chat ID used by Auto-Dodge and Gold Market for Telegram alerts	Empty