Template talk:Cargo monster locations

I think the template works not really well out. Because when you put all the monsternames in the monsterlist, the infobox explodes to a no longer good viewable size. Better is it to show the locations where the monsterfamily is OR where the unique monster is listed as inhabitant. Arawn76 (talk) 15:12, 22 December 2018 (UTC)

Profile comment read. Do you have an example? --  -- You talkin' to me? -- cCContributions -- 16:00, 22 December 2018 (UTC)

Take a look here https://pillarsofeternity.gamepedia.com/Searing_Falls_cave => Cail the Silent is an inhabitant, since he starts a dialog. When you click on him, he has the bestiary monsterlist. But the location shows no result.

Why? Because he is listed under inhabitants and the query checks only what is in 'monsters' therefor i think the cargo monster locations query should also check 'inhabitants'.

And next problem is the monsterlist. Example: https://pillarsofeternity.gamepedia.com/Young_Drake The query checks in the monsterlist the name of a single monster. => monsters HOLDS ""

But if you browse through the pages from beginning on the infoboxes have mainly only the family enlisted there. One reason is that the monster on a map varies, depening on which difficulty you play. Another reason is that you have a better overview, if each single monster is under the pagetopic enemies listed. I for example write the complete monsterlist under path on the damn on the page topic Enemies because i can structurize it better with br and * **

Pages like https://pillarsofeternity.gamepedia.com/Endless_Paths_of_Od_Nua or that https://pillarsofeternity.gamepedia.com/Endless_Paths_of_Od_Nua_Level_7 would elsewise really be difficulty to read.

Therefor i think should the query check for the 'family' otherwise we leave this cargo template away and add in the bestiary infobox the locations manually => e.g. locations = Searing Falls; Searing Falls Cave; ...

Hope you see what i mean Arawn76 (talk) 17:48, 22 December 2018 (UTC)