Istanbul Big Box Strategy: Routes, Assistants & Ruby Tempo
Editorial analysis: Istanbul is won by minimizing dead travel. Every extra move spent recovering a misplaced assistant delays the next ruby conversion.
Build short resource-to-ruby loops
Identify two or three locations that feed one another: warehouse, market and ruby source, for example. Repeat efficient loops before redirecting across the bazaar.
Leave assistants where you expect to return
An assistant left on a location is future infrastructure if your route naturally comes back. It is a liability if recovering it requires a dedicated detour.
Mosque upgrades compound
Permanent movement/resource upgrades are strongest early. Buy them when they reduce several future turns, not after most rubies are already claimed.
Watch changing ruby costs
Some ruby sources become more expensive as players claim them. If a cheap ruby is about to disappear, take it before completing a lower-priority efficiency step.
Use expansion modules to shorten—not complicate—the route
Big Box locations are valuable when they connect your resource engine. Avoid visiting new module spaces simply because they are available.
Endgame: count exact turns to the next ruby
When anyone is close to the target, compare routes in actions rather than abstract value. The fastest legal ruby matters more than long-term engine quality.