Template talk:Monster

S vs. Z
That is actually the correct spelling (with a z), but for now this hack will catch both - I can fix PeerBot later (haven't used him since 1.4 so I don't know if he'll work) and run him to find/replace 'orginisation' with 'orginization' on all monster pages. But it'll be a while before I find time to debug him. Till then this'll catch both kinds. ` Elliott Cable -  ?+¿  -  ‹·›  03:44, June 19, 2006 (EDT)

Auto-categories
Why are the categories inside includeonly tags? It would really help if these were auto-generated. Corebreach 04:08, November 26, 2009 (EST)
 * The categories are between includeonly tags because, otherwise, this page would show up in Category:Bestiary when it really shouldn't (since it's a template, not an article). What do you mean about auto-generation? --Borror0 03:43, November 27, 2009 (EST)
 * Sometimes an entry shows up automatically in a category based on monster type. Sometimes it doesn't and the category needs to be added manually. Check out Worg versus Zombie. Corebreach 04:04, November 27, 2009 (EST)
 * Okay. I see what is going on here. The monsters are listed by race, which are classified by creature. For example, worgs are listed as wolves (race) which is, itself, categories as an animal race. However, worgs are magical beasts, not animal, so they end up not getting the magical beast category. There are many ways to solve the problem, but that really depends on how we want to display the information to the user. The most obvious way would be to give worgs race "worg" which would be classified as an magical beast race. Is that fine with you, or would you prefer something else? --Borror0 11:49, November 27, 2009 (EST)
 * I'd say don't base the creature type category off race at all. Why make an assumption of what the type is based on race when the type is available directly? Corebreach 05:23, November 29, 2009 (EST)

Category:Bosses now empty
what gives? isnt working. what does this #lc supposed to do? --yoko5000 19:51, May 10, 2011 (EDT)
 * #lc: just transforms the input into Lower Case. Should make no other difference..  I will look into why bosses is empty, I would like to also revamp that a little so that it divides it up into orange, red, and purple name bosses..  ShoeMaker 22:04, May 10, 2011 (EDT)
 * looked into it and it hit me, should have been just lc: not #lc: -- ShoeMaker 22:47, May 10, 2011 (EDT)

Not all purple named bosses are raid bosses
Looks like you set it up so we can only have certain things in the "boss" section now.. Which is ok I guess.. But you set it up so all purple named are called raid bosses - but they are not.

Many are just powerful/challenging bosses found in quests requiring some form of flagging. Like the tor bosses, or the dreaming dark guy.

Was gona edit it myself but id prolly mess something up.. Suggest it work like this:
 * Purple - just say Purple Named Boss. Or Purple Named - Powerful Boss
 * Raid - Raid Boss
 * Red - Boss
 * Orange - Miniboss

Also see you put rare in there.. imo that doesn't belong as thats a different thing entirely.

If a boss is a rare spawn or not should be a seperate section, if present at all. As rare named can be orange or red, or even just regular (Green) Could just be rare=yes/no if you want it in there.

PS: I made a new category for purple named too.. So we auto-cat into that would be cool too. (purples go in purple, raid bosses go in purples and raid bosses) --Shade 22:38, July 26, 2011 (EDT)

Some more details on update
Ok edit complete.. Now supports named monsters that aren't bosses. And all "named" aren't put into a boss category since most of them aren't bosses. Put them into named monsters category instead which makes more sense.

Took out the purple = raid boss. Since really almost every single one of our raid boss pages are too complex to use this simple template, so they dont use it.. And the rest of purple named that may use it are not raid bosses.

One minor issue I see with having both the color= and/or boss= is it kinda leaves a hole I dunno how to fix if neither are filled. Not a huge problem since one or the other should always be filled, but some generalized racial templates dont use it. Tho maybe they should use a new/different template anyways. --Shade 15:58, August 2, 2011 (EDT)

Boss classification
Since more people than just me are working hard to fill the monster list, I think we should create a hard definition of what is a boss and what isn't. Throwing my two cents, I define a boss as any named monster that is required to kill to complete the quest. If you are not required to kill, it can be orange/red/purple-named, but not a boss. Eg, Tor dragons are not bosses, but the named mephits in Purge the Fallen Shrine are minibosses. Nibelung (Contributions • Message) 18:27, February 6, 2013 (EST)


 * I've always wondered why we don't just roll "boss" and "named" in together... I mean, as far as the template is concerned, they are nearly identical. They use the same colors... Bosses are all named... All named are not necessarily bosses. So, I would purpose that we roll boss into named and call it good... Or at very least, change the way that the template distinguishes them... Color is always color.  So, instead of having to declare a mob as boss = red or named = orange why not just color = purple/red/orange/yellow?  Then named and boss could just be yes/no on/of 0/1 type switches removing some of the template confusion.  Just my 2cp on the whole thing.

ShoeMaker (Contributions • Message) 19:31, February 6, 2013 (EST)


 * Not all bosses are named monsters. Some of them use the generic race name and are bosses, like the Ice Flenser on Misery's Peak, or the Gelatinous Cube on Coal Chamber. I agree that those bosses are usually found as common monsters later, and should not be listed as bosses on their main pages.

(Blame on me, forgot about my own discussion) Nibelung (Contributions • Message) 13:13, June 1, 2013 (EDT)


 * It is okay for bosses to be named with the generic name, as long as there isn't more than one boss with that generic name. Also, for the record, that ice flenser is not a boss (the crystal "Mindsunder" is the boss) in Miseries Peak.  It's not really that uncommon for the mini-bosses like that flenser and that cube to have generic names.  They are still named however in my opinion.

ShoeMaker (Contributions • Message) 17:33, June 1, 2013 (EDT)


 * The flenser is not the final boss, but IMO, he is a boss. I define "boss" by being any single mob that is required to kill for quest completion. And I classify "named" as any monster that don't appear anywhere else (or appear and is clearly the same character, like Malicia) and exists only one of them inside the quest (like those two named thieves on HIPS). A boss can be a non-named monster, and a named monster can not be a boss. Nibelung (Contributions • Message) 18:02, June 1, 2013 (EDT)

Race and Sub-race
Just a small nitpick that I think may improve the bestiary organization. Right now, the link on Race and Sub-race send you to the page with that exact name (Eg, every Ogre race monster links to the Ogre page, and every Worg sub-race monster link to the Worg page). Would be possible to add in the code to send the link to the race and  sub-race? Eg, instead of the Ogre linking to the ogre page, it would link to the Ogre race page, where we could centralize racial information, like the wind-up attack and the racial rage. That would help specially with the most complex special attacks, like the Tharaak Hound's Dance of Death. Nibelung (Contributions • Message) 14:08, June 18, 2013 (EDT)


 * I've done something. Is this what you wanted?

--Cru121 (Contributions • Message) 14:29, June 18, 2013 (EDT)


 * The link, yes. But if possible, the name on page do not show up the "race" parte. Like Ogre does.

EDIT: Looking where you did the first change, I fixed it as I wanted. Thanks. Nibelung (Contributions • Message) 14:36, June 18, 2013 (EDT)

Hitpoints?
Just killed the Mother-of-Thousands, and since I have monster manual favour, it showed she had 23,055 hitpoints (heroic elite). Do we care? :) Not sure anybody's interested in that but me. — previous unsigned Please sign posts using ~     comment by 71.125.204.105 (d&thinsp; &#124;&thinsp;r&thinsp; &#124;&thinsp;b&thinsp; ) &#32; at 21:33, September 18, 2019 (UTC)


 * Problem with hit points is that they vary by difficulty and dungeon scaling. You can mention it in the description if you feel it's interesting, but consider adding some reference points (for example, ~23000 hp at Heroic Elite, solo with hireling).--Cru121 (Contributions • Message) 03:52, July 15, 2014 (EDT)


 * Oh right, scaling. Urgh.  So it's not 4-8 variations or so, it's that times party count differences.  Yeah, no thanks. — previous unsignedIcon tooltip.png Please sign posts using ~     comment by 71.125.207.125 (d&thinsp; &#124;&thinsp;r&thinsp; &#124;&thinsp;b&thinsp; ) &#32; at 21:33, September 18, 2019 (UTC)

Edit request November 21, 2018
Added nocat parameter and cleaned up some stuff on what should or shouldn't show if fields are empty. Once this is merged in, I will attempt to make it so it only categorizes in article space (to eliminate accidental categorization in user/template sandboxes for example). &rArr; DDOstream (Contribs • Message • Email ) 10:47, November 21, 2018 (EST)
 * ✅ &#x1f45f;&thinsp;ShoeMaker (Contribs&thinsp;•&thinsp;Message&thinsp;•&thinsp;Email )&thinsp;&#x1f45f; 10:29, December 5, 2018 (EST)

Descriptor
Please copy the "descriptor" field code from the NPC template (sandbox) for monsters too. &rArr; Nom (Contribs • Message • Email ) 09:25, September 10, 2020 (EDT)
 * Please update T:Monster/sandbox to include the changes you would like to see to T:Monster and give examples of use on T:Monster/testcase2 and then uncomment the Er at the top of this section to draw our attention back to it. :)  &#x1f45f;&thinsp;ShoeMaker (Contribs&thinsp;•&thinsp;Message&thinsp;•&thinsp;Email )&thinsp;&#x1f45f; 12:18, September 10, 2020 (EDT)

Monster  Field?
I don't know if the above topic is asking the same thing, but, could a new parameter/field be added to the Monster template that would be the place to insert a monster's under-name chevron-enclosed title, eg. , if it has one? As it is, some monsters that have titles have said tiles being manually added in the "description" field, which is unpleasantly inconsistent and nonstandardized, and many others are missing. Ideally, such a title field would work such that you only put in the title itself, and the template would stick that title wherever appropriate on the page and automatically add enclosing chevrons. So the parameter in template use would be | title = Special Monster and then somewhere on the page, you would see
 * 

I'm not yet familiar enough with wikicode to do this myself, but I intend to watch this closely and if someone else can implement it, I can see what was done and use that as a teaching experience for myself to get more familiar with how wikicode works. Where exactly on the page the title would be put is also an open question that I have little input on, still being a relative newbie myself. Maybe it could go under the image, but above sayings? maybe it could go directly under the monster's name, above even its Type field as a new field like
 * Title: 

or maybe anywhere else that feels right to the veterans of this wiki. Obviously, wherever it is put, the field would not appear on the page at all if nothing is entered into the parameter (or better yet, if "No" is entered into the parameter), unlike things like type/race/subrace/alignment/monstermanual fields. Anyone have any input or suggestions for this? &rArr; TheWarforgedArtificer (Contribs • Message • Email ) 00:42, September 23, 2020 (EDT)
 * Why is that title important to have in a parameter other than the description (and the image)? &rArr; Faltout (Contribs • Message • Email ) 04:40, September 23, 2020 (EDT)
 * I already said. It is currently unpleasantly inconsistent and nonstandardized, in my opinion. I would like it to be more properly standardized. Is there any reason not to have it? &rArr; TheWarforgedArtificer (Contribs • Message • Email ) 10:56, September 23, 2020 (EDT)