Act 2 Dungeon
Every field under this key matches Syndicate Hideout exactly: the same and coordinates, the same (40-50) and level-40 requirement, the same 7-wave room script (Syndicate rank-and-file through waves 1-5, Syndicate Leader at wave 6, Chimera at wave 7), the same boss chest reward table, and the same completion signal- /.
Two top-level dungeon keys sharing identical content this precisely is best read as a renamed or duplicated registry entry: SyndicateHideout is likely the current player-facing key, with surviving as a legacy internal id still wired to the same completion signal. It is documented here as its own entity for extraction completeness (dungeons.json lists 6 top-level keys total), but see Syndicate Hideout for the full wave-by-wave breakdown.
Details
Why two entries exist
dungeons.json has 6 top-level keys:,, SyndicateHideout,, and amphitheatre. SyndicateHideout and are the only pair with fully matching content.
Both share the same internal room id inside their, the same, and the same map coordinates- strong evidence this is one dungeon indexed under two registry keys rather than two separate locations.
For the full wave-by-wave breakdown, boss chest odds and scaling notes, see the Syndicate Hideout page- the content is the same.
FAQ
Is Act 2 Dungeon different from Syndicate Hideout?
No. Every extracted field- waves, enemies, bosses, rewards, coordinates and completion signal- is identical. It is documented separately only because the client data lists it as its own top-level dungeon key.
Which name should I use, Act 2 Dungeon or Syndicate Hideout?
Syndicate Hideout is the more likely player-facing name; reads as an internal/legacy id pointing at the same content.
Other dungeons
Source-checked
Extracted from Mythfall client data; cross-checked field-by-field against Syndicate Hideout, which it duplicates exactly. updated · GuideDex staff. Report a correction.