Template talk:Infobox Monster new

From the RuneScape Wiki, the wiki for all things RuneScape
Jump to: navigation, search
This talk page is for discussing the Template:Infobox Monster new page.

Untitled[edit source]

This infobox is huge. Can't something be done about its length? I'd go for removing all the accuracy stuff; I doubt the average player is interested in that anyway... User_talk:Fswe1 Fswe1 Brassica Prime symbol.png 20:14, October 31, 2015 (UTC)

No, go away. All the information is important. MolMan 20:18, October 31, 2015 (UTC)
No. ʞooɔ 20:32, October 31, 2015 (UTC)
Echo. — Jr Mime (talk) [VSTF] 20:33, October 31, 2015 (UTC)
I can't think of a single reason why anyone would need that. But whatever, keep it; can the infobox be made more compact (making it a bit wider would be fine if that can help reduce length). User_talk:Fswe1 Fswe1 Brassica Prime symbol.png 20:33, October 31, 2015 (UTC)
Edit: Egh edit conflict. >.> User_talk:Fswe1 Fswe1 Brassica Prime symbol.png 20:34, October 31, 2015 (UTC)
Making it wider is a very bad idea. Page length isn't a scarce resource; width is. ʞooɔ 20:35, October 31, 2015 (UTC)
Not saying we should, but it's an option. It used to be wider after all. :) That said, however much length we have available, it's ridiculously long at the moment, which becomes especially noticeable on pages that don't really have much on them (e.g. Crondis (monster)). I reckon some rows can probably be merged. User_talk:Fswe1 Fswe1 Brassica Prime symbol.png 20:37, October 31, 2015 (UTC)
It actually didn't used to be wider. It used to be 33% of your screen width, which is very large for certain types (like Monobook users) but very small for most people. ʞooɔ 21:13, October 31, 2015 (UTC)
Ah, very well. Anyway...any fresh ideas? User_talk:Fswe1 Fswe1 Brassica Prime symbol.png 08:15, November 1, 2015 (UTC)
Fresh ideas for what? It's not changing. MolMan 10:38, November 1, 2015 (UTC)
Look at it. The size is ridiculous. >.> User_talk:Fswe1 Fswe1 Brassica Prime symbol.png 11:46, November 1, 2015 (UTC)
If you have suggestions for condensing it without losing information, I'm listening. But we're not going to remove data from the page to fit an aesthetic. In fact, we're more than likely to make it even longer. ʞooɔ 11:49, November 1, 2015 (UTC)
That's the thing; I don't. Otherwise I'd've been bold and tried something. I maintain stuff like 'accuracy' is about as useful as 'eye colour', but I reckon it wasn't added for fun, i.e. someone, somewhere might possibly find it useful. That said, perhaps the accuracy values could be added in parentheses to the max hits (unless the max hit is 0), provided that won't cause clutter. I'd also swap the rows for max hits and style/speed. As for immunities, I'm not sure images are the best idea. I, for one, could not figure out what the shield icon meant, and thought the stat drain one was deflect. But maybe that's just me? :P User_talk:Fswe1 Fswe1 Brassica Prime symbol.png 12:02, November 1, 2015 (UTC)
Maybe you should learn to hover your mouse over things. Also, no. Those merge ideas are dumb. MolMan 12:07, November 1, 2015 (UTC)

Poisonous[edit source]

It's currently broken and always shows as non-poisonous. Dsctatom (talk) 22:45, November 2, 2015 (UTC)

You need to put a number, not just "Yes". MolMan 22:47, November 2, 2015 (UTC)
I noticed it on the Wyvern page and that is indeed the problem. Just to test them, I ran down and got hit by their poison: 603. I'm not sure if poison values vary the way hits do, but should I put that value for now so it at least displays as poisonous? Dsctatom (talk) 04:54, November 3, 2015 (UTC)
Put the base value of a poison hit. Further damage change should be noted in the article. MolMan 04:57, November 3, 2015 (UTC)
In response to this though, I've added some functionality to support use of just "Yes", which informs users that they need to use the number instead. MolMan 05:07, November 3, 2015 (UTC)

Some minor switching issues[edit source]

Hey I stumbled on a couple of potential issues when getting my trying to implement switched infoboxes, so thought I'd report them.

  • slayercat doesn't default properly
    • If the slayercat for a specific version is omitted (e.g. slayercat1=Xyz), it defaults to "N/A" instead of defaulting to the non-versioned slayercat. An example of this is here: Slayer category is N/A despite |slayercat=Dagannoth being set.
  • name defaults to page name first
    • This is only an issue when the monsters name differs from the pagename. Omitting a versioned name will default to the pagename instead of the non-versioned name. (e.g. on this page, the name starts as Dagannoth but when you switch versions, it becomes Dagannoth (Waterbirth Island) despite |name=Dagannoth being set.)

A solution to these issues is to set each version individually (e.g. |slayercat1=Xyz|slayercat2=Xyz|slayercat3=Xyz ...) but it seems inconsistent with other parameters which default properly.

Also, the aka tag is a bit broken on switching (example) but its not listed in the FAQ so I assume it isn't intended for use. Lmnt (talk) 14:00, April 21, 2016 (UTC)

Noted thanks. I'll look into these when I have time. MolMan 14:05, April 21, 2016 (UTC)
Alright I've managed to find and fix these errors. MolMan 17:21, April 21, 2016 (UTC)

Script error?[edit source]

All instances of this template show a script error. :S Farming-icon.png Salix of Prifddinas (Talk) Prifddinas lodestone icon.png 20:38, July 21, 2016 (UTC)

Wrong documentation[edit source]

The Doc link at the bottom of the template leads to that of the old version. Jampolo 03:37, December 14, 2016 (UTC)

Item experience[edit source]

Item experience is sometimes inaccurate, presumably due to rounding errors (e.g. Corpse Spiders show 1/1/0, they actually give 0/0/0). Bio (talk) 04:46, 17 April 2019 (UTC)