Glossary
Every term iCity 2 puts in front of you, grouped by where you meet it. Where the interface and the code disagree on a word — and they do, in about a dozen places — the entry gives you both names and tells you which one is on screen.
How to read this page
Terms are grouped by where you meet them: the shape of the product, then Draft, then Design, then the cloud, then your files, then your account. Every entry is named the way the interface names it.
Several things in iCity 2 answer to two names. The engine, the addon, the website and the log lines were written at different times, and a word that changed on screen did not always change underneath. A Region is still a Block in the mode list. A Road in the status bar is a Segment in the popup that edits it. The website says Team where the addon says Organization.
Where that happens, the entry gives you both, and the name on screen is the one to use when you are talking to somebody. The other name is worth knowing because it is what you will see in a tooltip, a log line or a status message.
The 3D viewport in Draft with exactly one road selected and its right-click popup open, framed so both names read at once: the iCity status bar along the bottom saying 'Road', and the popup titled SEGMENT with its 'Delete Segment' verb visible.
The shape of the product
icity2. All three are the same thing.bin/windows/iCity2App.exe and must be running for any Draft edit. Log lines call it the iCity2 Core. After a crash it restarts itself three times, then gives up with Restart budget exhausted (3 attempts) — engine stopped. See The engine.Blender's editor-type dropdown open on an area inside the iCity 2 workspace, scrolled so the three iCity entries — iCity Editor, iCity Logs and Data Output — are visible together, and no entry named 'iCity Themes' appears in the list.
Drawing: the Draft words
The iCity Editor in Regions mode (Alt+3) on a city with no custom regions drawn yet, framed so the status-bar caption 'Regions (Alt 3)' and the panel's 'No blocks yet' empty state are both readable in the one shot.
Dressing: the Design words
The cloud
iCity-2-dev sidebar tab and is not part of normal use.Job tracking lasts as long as the Blender session. A theme that finishes while Blender is closed cannot be picked back up from the interface — nothing re-downloads its assets on its own.
Your files
Your city lives in the engine, not in your .blend, and the project folder is where it is written down. That split is explained in full on How iCity fits with Blender.
Documents/iCity 2/<name> holding README.md, the saved city state, the theme files and project.json. Registered projects are mirrored on the server. See What a project is.project.json. The dialog offers Upload as new or Use this project.materials/<Category>/<AssetName>/ and props/<Category>/<AssetName>/, one folder per asset. See Using your own assets.Account, plans and sharing
auth.parametra.net and hands the result back to Blender. Everything in Design needs it.The Discord is fastest for anything scene-specific. Email suits licensing, billing and anything needing a file attached.
Contact support →