Template talk:Familiar

From A KoL Wiki
  • I would like to suggest quite strongly that we remove the 'Combat Messages' section from the template. The reason for this is because if you try to go to any wiki page and click 'edit' on the combat messages section, you get an error about it being locked. I do not believe that this is what the desired intention is. --Shagie 20:30, 3 December 2005 (Central Standard Time)
  • ...why is this template locked? none of the others are, plus the lack of section header editing and like is disorientating compared to when I'm on/editing other pages.--Dehstil 16:18, 6 May 2006 (CDT)
  • People would hit "edit section" on a familiar page and would edit the template, and most of the time would never even notice they screwed up every familiar page, so the template was locked. I guess the 'combat messages' section could be removed, it was just added in the first place because all pages had it, so it was faactored out into the template, but that's 51 pages that need to be changed along with it ;-) --JRSiebz (|§|) 17:03, 6 May 2006 (CDT)

It would be nice if we could add the Familiars category to the template itself, so as to not require manually adding the category to the bottom of every page which uses it. Unfortunately, 4 pages (Sandbox, Established Standards: Familiar Pages, User:Phelyan, and User:Stik guy) which are unrelated to familiars also include this template, making the idea useless. Is there any way to block the inclusion of categories on specific pages to get around this problem (and possibly do the same for other templates as well, such as Adventures)? --Quietust 20:33, 7 June 2006 (CDT)

  • I know it's been a really, really long time since you asked this, but the answer now is: yes. I've essentially made this modification already, and am currently removing the manual categorization from the pages. Although I will note that the current listing of the established standards page is a happy coincidence of one auto-cat overriding the other. I've intentionally had the standards pages categorized in the category they carry standards for, and have them listed at the top of the category. But I hadn't noticed this particular standards page directly called the template, so it was being categorized twice, and it seems the one later on in the page is trumping the familiar template's categorization. I could fix that, too. Could be done by throwing in more #if and #ifeq statements into the templates to recognize the special cases. Or subst'ing the template on the established standards page and then manually deleting the categorizations. Any particular preference? --Flargen 10:00, 9 December 2008 (UTC)

We could use {{head}} to fix the section header issue now.--Dehstil (t|c) 19:48, 23 June 2006 (CDT)

  • Also, not sure if it's supposed to be this way, but it says "Return to Main Page" at the bottom of the View Source page. Is that the way locked pages are supposed to be or should is it possible to say "Return to Template:Familiar"?--Dehstil (t|c) 20:53, 23 June 2006 (CDT)
    • That's a problem with the entire wiki. I figure we could go ahead and report that to the section for things that are broken....if Mag even checked it anymore =/.--SomeStranger (t|c) 22:04, 23 June 2006 (CDT)

Equipment

The code for the equipment field assumes that it will receive exactly one item. This breaks slightly on the Pet Rock page and others of it's ilk, as mentioned at Talk:Bulky Buddy Box (familiar). --Starwed 16:26, 13 December 2007 (CST)

  • It used to work with {{!!}} which acts acts as ]], [[ so when [[{{{variable}}}]] was given equip1{{!!}}equip2 it would render as [[equip1]], [[equip 2]], but this template was just changed to take the variable and lookup its data page to get it's item name, so using {{!!}} no longer works. --JRSiebz (|§|) 21:59, 13 December 2007 (CST)
    • Dare wuz a prawblum, but I eats it! I mean. I fixed it, using {{!!}} in this case was an old-school, pre-parser function, pre default/optional parameter wiki way of faking it with a template to be included in another template, i made {{!!}} over a year and a half ago! Remember using {{p1}}, anyone? You people are so spoiled with being able to use these things called "if"s and "ifeq" on the wiki, ;-) heh --JRSiebz (|§|) 22:29, 13 December 2007 (CST)

Arena specs

I'd like to see this template edited in some way so as to completely list a familiar's arena specs. "Strength" and "Weakness" omit the other two possibilities, which are good to know if (for some strange reason) you are trying to level your familiar without using some sort of script to do it for you (or at least tell you what choices to make at what weight). It's also just a little strange that all of this information is out there and fairly easily obtainable, yet the wiki does not contain it except when it happens to appear on chat pages. I could certainly do the editing myself, but I'm not sure what would be a good format. --Flargen 09:55, 9 December 2008 (UTC)

  • Now that you mention it, I think it's kind of weird we don't list the other two possibilities. We should probably add them. However, I don't think it would be all that easy to present the Arena mechanics on every page so the reader can easily choose the optimum path for each opponent/event combination. The image I have in my head is replicating something like the table in that section--at that point, we may as well just link "Strength"/"Weakness"/"Average"/"Handicapped" to that explanatory section in the arena article. --BagatelleT/C 03:09, 10 December 2008 (UTC)
    • How about something like
The Cake-Shaped Arena Ultimate Cage Match Strong
Obstacle Course Average
Hide and Seek Weak
Scavenger Hunt Unable to perform

I'm not too happy with the "unable to perform" thing, but I'll stick with it for now since that's what the event pages use. --Flargen 03:25, 10 December 2008 (UTC)

  • Here's a wiki history lesson. Originally, familiars were only Strong, Weak, or Average in Area events. So events were mentioned under Strength: for strong events, and Weaknesses: for weak events. All other events not explicitly mentioned were assumed average. We mentioned strength and weakness, and we didn't feel the need to mention average ones, since (it used to be that) familiars always had one strength, one weakness, and were average in all the others. But now familiars can be good or bad in multiple events and sometimes refuse to compete in certain events, so this section probably should be updated to be more specific. Maybe some of you found this interesting, or not, but this is how the display originated, and just was never updated. It just ended up being show good, show bad, else assume just average, check notes for no-competes. Wiley, old wiki-veteran out. Holy crap, the wiki started May 6, 2005 and I've been an admin since July 25, 2005... and don't get me started on wiki editing with a whole 5 templates and no parser functions, uphill in the snow both ways, barefoot. --JRSiebz (|§|) 04:45, 10 December 2008 (UTC)
    • And just for fun, around the time I became wiki admin, the front page of the wiki looked like this! Oh, nostalgia, heh. --JRSiebz (|§|) 04:49, 10 December 2008 (UTC)

The Cake-Shaped Arena:

Ultimate Cage Match Obstacle Course Hide and Seek Scavenger Hunt
          

The Cake-Shaped Arena:

Ultimate Cage Match Obstacle Course Hide and Seek Scavenger Hunt
          

The Cake-Shaped Arena:

Ultimate Cage Match Obstacle Course Hide and Seek Scavenger Hunt
          

I'm not entirely happy with the color, formatting, or the symbol chosen (martini guy olives ;-) ), maybe hearts  , or Jick eggs  , or a happy, sad, neutral face thing like  ,  , insert the smiley with the straight mouth that i can't remember the name of here. Then the template could take variable like cage=3, course=2, hide=1, hunt=0, all defaulting to 2 (average) if not mentioned and autogen it. The more different ideas the better. Or maybe a random symbol of a chosen set, HAH! One day, be rated 3   , the next 3   or  , or just ignore that. :-D --JRSiebz (|§|) 05:24, 10 December 2008 (UTC)

  • Ooh, I really like that style. I say we go with this one. Yes, JRS. That includes the olives. --TechSmurf 05:50, 10 December 2008 (UTC)
  • I don't think the border will go well on familiar pages. Maybe borderless like this:
 
Fighting, dancing sprite
Dinnae try tae cross his path
Ye'll get yer heid broke.

Ability: Acts as a Fairy, attacks and drops up to five tiny bottles of absinthe a day.

Hatchling: bottled green pixie

Familiar-Specific Equipment: green pixie spog

The Cake-Shaped Arena: Ultimate Cage Match Obstacle Course Hide and Seek Scavenger Hunt
           
  • Whatcha think? --Flargen 06:25, 10 December 2008 (UTC)
  • Oh, and for auto-gen'ing it in the template, we probably shouldn't go with a default value. We should probably just have it spit out "unknown" and have the template auto-cat the page in [[Category:Incomplete]]. --Flargen 08:28, 10 December 2008 (UTC)

Another possible format:

 
Fighting, dancing sprite
Dinnae try tae cross his path
Ye'll get yer heid broke.

Ability: Acts as a Fairy, attacks and drops up to five tiny bottles of absinthe a day.

Hatchling:   bottled green pixie

Familiar-Specific Equipment:   green pixie spog

  Ultimate Cage Match Obstacle Course Hide and Seek Scavenger Hunt
           

There's a barely visible border on the right side of the image. This is to attempt to "trick" the mind into automatically associating the arena with the events and pictures beneath the events, without it being terribly obvious visually. But maybe I'm trying too hard to do that and it could just be omitted. Any thoughts on this or any of the other possibilities? Anyone? Anyone? Bueller? --Flargen 08:07, 12 December 2008 (UTC)

One Implementation

Currently at Template:Test, I've coded up the changes using one of my proposed styles, and added in a few examples to show how it will behave under various inputs for each event. This should give a decent idea of how it would look on real familiar pages. Thoughts? Issues? Likes? Dislikes? The meaning to life, the universe, and everything? --Flargen 13:43, 12 December 2008 (UTC)

  • I don't really like the olives (they don't make much sense in context) and I don't think it's immediately clear what all of the images mean. I would much prefer a modified image of the cake arena (perhaps shrunk) with a numerical representation of each area with a small link to a page explaining what all of the numbers mean.--SomeStranger (t|c) 19:26, 19 December 2008 (UTC)
    • Well, you can blame JRSiebz and Techsmurf for the olives. I'm not married to them. It's a fairly trivial change to the code to switch the image. But, seeing as how there was little input on anything, I went with what we had so far. As far as the images being unclear, it was a risk I took to remove meaningless image clicks. I hate it when an image is clickable but all it leads to is the image page, especially when that image is not "native" to that page's content (olive having a clickable olive image, for example, is something I'm okay with). And, according to Template Talk:Click, adding in alt text for click isn't possible. Though I don't know if that is still true. As such, I'm not terribly happy with the current question marks; was debating going with candy_question.gif instead. --Flargen 23:15, 19 December 2008 (UTC)
    • Oh, and as for explaining what things mean, that's basically the role of the event pages themselves. Ultimate Cage Match, for example. I think it should be pretty intuitively clear that "more olives = more better". --Flargen 23:17, 19 December 2008 (UTC)
    • Like the other arena resources I was planning on just using stars, but kol stars and starfish don't really look like good stars, and   is a tattoo image so it is larger than most other images. The olives do kinda look likes eyes/boobs/balls sometimes. --JRSiebz (|§|) 04:47, 20 December 2008 (UTC)
    • I've now added some spans with titles to the template. These will help explain what the number of olives (or whatever image that gets replaced with) under an event listing means. I found something of a loophole around the "useless image clicks for the question marks" thing, by using the exact wiki URL for the 30 pixel thumbnail. It's lacking in grace, but that's how much I dislike pointless image clicks. --Flargen 15:59, 23 December 2008 (UTC)

I don't like how the text "Ultimate Cage Match Obstacle Course Hide and Seek Scavenger Hunt" looks all run together. I like it better with borders between them, or at least more space. --ManaUser 21:07, 1 January 2009 (UTC)

  • You're going to have to provide a picture and an indication of your browser and relevant settings. There's quite a lot of space inbetween them. --Flargen 21:12, 1 January 2009 (UTC)
  • I finally saw what you meant. Should be fixed/better now. --Flargen 06:39, 15 February 2009 (UTC)

Breathes Underwater

  • any chance of a new parameter (BreathesUnderwater?) that not only adds relevantly to the notes section, but also inserts the category if necessary? i'd do it myself only i don't have the time to learn how to update templates right now. sorry. --Evilkolbot 11:34, 8 October 2009 (UTC)

Should there be fields for the enchantment/combat effect of the Crown?--Toffile 16:54, 4 May 2010 (UTC)

  • It's a variable kind of thing is the problem. Exactly what it displays depends on what the user's done with it. So I've no idea. This is clearly just Jick upping the ante on the ways in which he tries to completely screw over the wiki. The fiend. --Flargen 16:57, 4 May 2010 (UTC)
I don't think it's just Jick trying to fuck with the wiki templates. It seems like every item of the month is now a New Mechanic. No mere lucky wax maypoles that add ten pounds of this or that, or familiar husbandry projects that give weird hybrids. Now we get spooky putty, which can copy monsters. Stinky cheese which needs a daily usage counter. We get BRICKOs that build fightable toys that drop new combat items that need to be used to fight other fightable toys. We get mirrors that give potions that give maps that give items that can be traded for equipment that gives buffs. We get that complex beast that comes from a panicked kernel. It used to be such things were once every couple of months, now it seems to be every time. --Club (#66669) (Talk) 17:28, 4 May 2010 (UTC)
This is similar to Jingle Jangle skill: a single thing (item, in this case) affects familiar behavior. The suggestion to add a note - whether or not a given familiar benefits from Jingle Jangle - and relevant combat message didn't stick, and people decided that the skill/effect page was enough.
I think that for the sake of consistency information about familiar on-the-throne bonuses should be confined to the crown of thrones page. --Gadaree 17:47, 4 May 2010 (UTC)

Proposed changes (equipment's effect, image-based fam effect)

  1. How about a slot to put the familiar's equipment effect in?
  2. See content familiar. How about using something like that? So we can have, for Cuddlefish
function={{feff|fam=potato|75%}}{{feff|fam=whelp|75%}}, or {{feff|fam=potato|100%}}{{feff|fam=whelp|150%}} ([[underwater]])
where "feff" is a template with a list of several common familiar types. It would show an image of that familiar, plus a tooltip specific to each familiar type explaining the effect (possibly the formula). --Raijinili 17:11, 6 July 2011 (CEST)
  • I'd probably say no to the familiar equipment. Enchantment data isn't kept as metadata, so it'd have to be manually entered (or rework the item template)...and for like 80% of the time, it's just +5 lbs.
As for the effect suggestion...eh. The template would be a bit of a resource hog, and it wouldn't really serve any better purpose than what's already in use. There's already a few pages that explain different familiar attributes in relation to one another.--Toffile 18:44, 6 July 2011 (CEST)
    • If eqeffect is empty, defaults to +5. Simple for that.
    • And using images in "effect" would just be to make it quicker to parse. Makes it more compact and standardized for regular readers, with a title text for newer players. --Raijinili 15:37, 9 July 2011 (CEST)

Leap Year update

February 29, 2012 - Pop-up familiar descriptions now have blue text describing the familiar's function. Conjunction Junction.--Toffile 04:21, 1 March 2012 (CET)

Familiar/Mumming Attributes


Mumming Trunk Abilities

Additional ability
Upgraded power

  •  

    +30% Meat Drop
    Delevel 25% at start of combat
  •  

    4-5 MP
  •  

    +3 Muscle
  •  

    +15% Item Drop
  •  
    Helps you get the jump on enemies

    +3 Mysticality
  •  

    18-20HP
  •  

    +2 Moxie

Can breathe underwater

 

Additional ability
Upgraded power

  •  

    +30% Meat Drop
    Delevel 25% at start of combat
  •  

    4-5 MP
  •  

    +3 Muscle
  •  

    +15% Item Drop
  •  

    +3 Mysticality
  •  

    18-20HP
  •  

    +2 Moxie

  • Would it be a good idea to add familiar attributes to the template? Namely the ones that determine the effects given by mumming trunk. I like how the first looks, but I think the second might be better. On the Myst attribute of the first one it shows the extra attribute if you hover over the image. The first one would go under the arena, it also has info about whether or not it can breathe underwater. The parameter can be something like this:
   attributes=hands,animal,eyes,underwater

Or maybe i'm overdoing it and it should just be in the {{Template:Preload/Familiar}} page as a list.--Icon315♕ (|) 08:53, 1 August 2018 (UTC)

    • I think it would be nice, I don't think there's an existing list for this. It would be nice to have it autocat as well.
    • I think it should be one parameter per attribute with a 1 or 0. If it's given as one string, I can't see a way to get around the implementation having to explode the entire string around comma repeatedly, then check every possible split against a fixed string to see which way it's going to format each mummer costume (as the attributes are unordered). See e.g. what {{Template:PartsCat}} does, and that's a lot simpler than this -- it just wants to make a set of categories. It would be possible to do a single string using a language that actually has variables, like Lua, but I don't think that's enabled here.--Ryo_Sangnoir (talk) 19:46, 1 August 2018 (UTC)