Talk:Vaal side area

Map Fragments

Placing bets on them dropping in cruel+, Couldn't get any to drop in normal southern forest. Ran some in cruel southern forest and started seeing them drop again.

Twilight Strand

Does anybody know if corrupted areas spawn in Normal twilight strand? I assume not, but it would be good to know for sure. Magnanimous2 (talk) 22:54, 16 March 2014 (UTC)

Vaal Side Area Info Out of Sync

This page lists the possible locations for Remote Gulch as:

• Prisoner's Gate (Act 1)
• The Ship Graveyard
• The Coast (Act 6)
• Prisoner's Gate (Act 6)
• The Beacon

The Remote Gulch Page lists possible locations as:

• The Coast
• The Climb
• The Ship Graveyard
• The Beacon

Which page is more accurate?

Additionally, in cases such as The Coast, which appears in multiple acts, could the side area appear in either location unless otherwise specified? It might be clearer to list it as "The Coast (Acts 1 & 7)" if that is the case.

List of Corrupted Areas

Is there any way to optimize this query for insertion?

{{#cargo_query: tables = areas=a, areas=b |fields = a.act=Act, b.main_page=Vaal location, a.main_page=Location, b.boss_monster_ids__full=Boss |join on = a.vaal_area_ids HOLDS b.id |order by=a.act,b.main_page |where=a.vaal_area_ids holds not "" and a.main_page != "" |format=table }}

--Kordloperdlo (talk) 10:25, 25 March 2020 (UTC)

You can group up by the vaal area id and reduce a couple of rows. Looks a bit better.

{{#cargo_query: tables = areas=a, areas=b
|fields = b._pageName, b.main_page=Name, GROUP_CONCAT(DISTINCT a.main_page)=Locations, GROUP_CONCAT(DISTINCT b.act)=Act, GROUP_CONCAT(DISTINCT b.boss_monster_ids__full)=Boss
|join on = a.vaal_area_ids HOLDS b.id
|where = a.vaal_area_ids holds not "" and a.main_page != ""
|group by = b.id
|order by = a.act, b.main_page
}}

--Illviljan (talk) 19:50, 25 March 2020 (UTC)

I have been fiddling a bit with the query and came up with the following:

{{#cargo_query: 
tables=areas=normal,areas=vaal,monsters=bosses,skill
 |join on=normal.vaal_area_ids HOLDS vaal.id,
   vaal.boss_monster_ids HOLDS bosses.metadata_id,
   bosses.skill_ids HOLDS skill.skill_id
 |fields=
   CONCAT('[[', vaal.name, '|', vaal.name,']]')=Name,
   GROUP_CONCAT(DISTINCT
     '*[[', if(normal.main_page != "", normal.main_page, normal.name), '|', if(normal.main_page != "", normal.main_page, normal.name), ']]' 
     ORDER BY normal.act, if(normal.act < 11, normal.area_level, 999), if(normal.main_page != "", normal.main_page, normal.name)
     SEPARATOR "\n")=Area,
   GROUP_CONCAT(DISTINCT '[[', bosses.name, '|', bosses.name, ']]' SEPARATOR ", ")=Boss,
   GROUP_CONCAT(DISTINCT
     '*[[', if(skill.active_skill_name != "", skill.active_skill_name, skill.skill_id), '|', if(skill.active_skill_name != "", skill.active_skill_name, skill.skill_id), ']]: ', if(skill.description != "", skill.description, "")
     ORDER BY skill.active_skill_name
     SEPARATOR "\n")=Abilities
 |where=normal.is_vaal_area="0"
   AND vaal.is_vaal_area="1"
   AND bosses.is_boss="1"
 |group by=vaal.name
 |order by=vaal.name
}}

I do have some issues with it:

1. main_page can't be used everywhere because not all areas have it set correctly (or set at all). For example, Cremated Archives itself is a disambiguation page, but the main_page links to Cremated Archives (Act 5).
2. All the if() statements make it hard to read/maintain. When all the areas have a proper main_page set it would help readability.
3. I couldn't find how to get the actual monster type of the boss (e.g. Dust Scrabbler)
4. The Abilities column is very busy and contains a lot of text. There are also a bunch of abilities which do not have a name, description or page. Perhaps just remove this column?
5. No lore text column :( (and no Entrance Type column)

Dreddie (talk) 11:52, 16 August 2023 (UTC)

Links between areas section

This section is woefully out of date and hard to read. It should either be removed entirely or updated and formatted in a way that can be read as text. —Vini (t|c) 05:05, 7 December 2020 (UTC)

map enchant

Apparently it is fixed so that now the map enchant spawn a random vaal side area, instead of fixed one. Just got Sacred Chambers from Ashen Wood Map T16 Neokowloon (talk) 08:05, 29 April 2022 (UTC)

Alluring Vaal Side Area, For Love of the Queen, "or its preceding"

"[Alluring Vaal Side Area] can only spawn if the player allocates For Love of the Queen Atlas Notable or its preceding atlas passives,"

Is this "or its preceding atlas passives" true? Guaranteed? Which nodes are these? The 3 "Vaal Side Area Chance" near the "For Love of the Queen? (And only these? The other "Vaal Side Area Chance" nodes (near Unimaginable Horrors) are not?)

"Any source which confirms that? Any user who actually have tried and he has got Alluring Vaal Side Areas, just by allocating the 3 "For Love of the Queen"-near "Vaal Side Area Chance" nodes, without allocating the "For Love of the Queen"?

(Why would anyone not allocate the "For Love of the Queen"? - For example because of the Wandering Path node: "Notable Atlas Passive Skills grant nothing". So "For Love of the Queen" grants nothing too.) Nmbaply (talk) 20:18, 24 January 2024 (UTC)