5,290 Edits since joining this wiki
August 27, 2005

Foxbot rampage

I'm seeing a lot of foxbot usage that stomps on pages and then has to be reverted. Recent examples: Copper Bar, Khorium Scope. It kinda looks like the bot assumes the page is a stub, but is being used on existing pages.

The Foxbot user page doesn't describe its function - or requirements - sufficiently that I would risk using it. (It describes how to operate it well enough, but that's useless without the functional spec.)

Would you please expand on the function of the bot, and the requirements for a good first-pass result? -Eirik Ratcatcher 22:41, 26 June 2007 (UTC)

At this point, it should not be used directly against pages that already include significant content unsupervised - it simply regenerates the entire page from armory data, ignoring any previous content. So far, it can be used as an easy way to add new items to the wiki (but not replace {{tooltipcss}}-style tooltips on pages with signficant content). One of the sore points at the moment is how it handles crafting products and reagents (while this works for some pages, like [Deathwing Brood Cloak], it's still not quite perfect).
So, general guidelines: avoid existing pages with content that you'd rather merge; avoid crafting and spell-created items. Foxbot isn't yet at a point where it can be used without supervision, so people requesting item pages should also check up on what it actually generated. There's always #doitem to save the page in the sandbox to inspect or steal {{tooltip}} code without doing anything to the real page. :) -- Starlightblunder 00:12, 27 June 2007 (UTC)
Sad thing is, I discovered Foxbot by finding that it had stomped on a page I had contributed to... The person who invoked it (Gryphen, I think) has no user page, and has not directly contributed recently (if memory serves), making it a bit harder to communicate with him. Ah, well. As long as it isn't often.
... I see that foxbot creates a link to/from some page (category?) to point out pages it has edited to make oversight easier. ... but I could not identify exactly which page or category it was. There is the category Bot editing requests, but I thought there was one specific for Foxbot? --Eirik Ratcatcher 17:22, 27 June 2007 (UTC)
There's no Foxbot-specific fix category - it just dumps pages it knows it may have messed up into Bot editing requests (only thing doing so atm, I believe); you could use the individual fix templates (linked on User:Foxbot/FixPlease) to see which pages need which fixes. Gryphen is relatively active on IRC, so he is not entirely gone either. -- Starlightblunder 19:44, 27 June 2007 (UTC)
Eirik, I am Gryphen on IRC. Some of those reverts are either me testing, or, in past there was a spelling error in an article so it showed the item didn't exist and then I spelled it correctly causing a duplicate overwrite. I always check over what the bot adds when I request an item addition. A couple of reverts I wouldn't call a "rampage", the bot does very well. --GRYPHONtc 03:33, 3 July 2007 (UTC)
I noticed that Foxbot came in and pretty much overwrote Band of Anguish which I de-stubbed today. I did noticed that it actually removed data (like who gives the quest for which its a reward and the Quest Rewards category). Might want to be careful with the bot so its not wiping out info. - ClydeJr - talk - contrib 02:26, 30 June 2007 (UTC)
I went through the first few items on Category:Item stubs and requested some of those to be updated -- unfortunately, you got in 45 seconds before the queued bot edit (which is probably about 2 minutes after I checked page content), so it ended up overwriting. I'm still working on a reasonable merge mechanic so this could be avoided in the future. -- Starlightblunder 09:15, 30 June 2007 (UTC)
Cool, figured it would be something silly like that. No worries. - ClydeJr - talk - contrib 02:50, 1 July 2007 (UTC)

More for Foxbot

For the Things To Do...

  • add [[Category:Quest items]] if a quest item
  • add [[Category:Quest rewards]] if a quest reward (I've seen it mention quests...)
  • add item commonality category. (e.g. [[Category:Common Items]]

And no idea how it did it (parameters when invoked?) but it got the quest right and the zone wrong for a couple items (Sturdy Leather Belt, for instance) --Eirik Ratcatcher 23:25, 29 June 2007 (UTC)

Item data is pulled from the Armory, which seems to believe the NPC is in Bloodmyst Isles; I'll see what I can do about adding the categories. -- Starlightblunder 23:27, 29 June 2007 (UTC)
Keen. Think you and I just barely avoided stepping on each other's edits re Chief(tain) Oomooroo ... :) Does Foxbot also do NPCs? --Eirik Ratcatcher 23:34, 29 June 2007 (UTC)
Nope, since there's no easy way to search for those and pull up related information; armory really isn't a complete database of everything. As for the categories: Category:Quest items would be added already; Category:World of Warcraft common items should be added from now on, and Category:Quest rewards some time in the future. -- Starlightblunder 23:43, 29 June 2007 (UTC)
I created a Perl script that does something similiar to Foxbot (although I'm sure not as completely) that implements a few things that Foxbot may not. If you know perl, feel free to have a look and drop me a line if you have any questions about the script. -- Cisox (talk - contrib - scripts) 03:23, 3 July 2007 (UTC)
I've also been pointed to KasoBot which does something like this as well. Perhaps there is some collaboration that can be done. -- Cisox (talk - contrib - scripts) 03:27, 3 July 2007 (UTC)


Nice work on {{gallery}}. You know that <gallery> supports captions? They are displayed below the image, not sure if you were specifically avoiding that. --GRYPHONtc 00:37, 8 July 2007 (UTC)

Yeah, but aligning those gets a bit difficult when you don't know the amount of space you have to work with in advance. We could probably plug a similar mechanism in at a later date (since the template accounts for captions using alt=""), but it'd have to be rather crafty to avoid uglyness when combined with long captions and wrapping. -- Starlightblunder 00:42, 8 July 2007 (UTC)
Ok, I just wasn't sure if you knew of existing functionality. --GRYPHONtc 00:44, 8 July 2007 (UTC)
There doesn't seem to be the same margin below the images with {{gallery}} as with <gallery>;

==Next Section==

Does not leave the same space between the images and Next Section as does


==Next Section==

--GRYPHONtc 01:08, 8 July 2007 (UTC)

booboo with {{quality}}

Not sure how to fix, but uncommon quality items are showing up as poor quality items ({{tooltip}} pulls from quality, which is why i noticed.) See here. --Sky (t · c · w) 07:22, 11 July 2007 (UTC)

I fixed it, Starlight turned Uncommon into Incommon.
 ∙ Zurr  TalkContr 07:55, 11 July 2007 (UTC)
More reasons I shouldn't be editing templates past midnight. --Starlightblunder 08:53, 11 July 2007 (UTC)


When foxbot populates an item and uses {{questlong}}, is it using the quest level or the minimum level required for the number? I noticed when it populated Kodohide Drum, it used 65 as the level which is the minimum level required and not the actual quest level. Shouldn't it use the actual quest level? - ClydeJr - talk - contrib 20:16, 11 July 2007 (UTC)

The bot only uses data from the Armory, the Armory doesn't say actual level. Template that sig :( --GRYPHONtc 20:41, 11 July 2007 (UTC)
Good point, actually - I currently use the minimum character level rather than the quest level for questlong; I'll have a look at what I can do about it. Update: bot should now use the quest level, rather than the required min level. -- Starlightblunder 21:06, 11 July 2007 (UTC)
Ah ya I see they do include that info. --GRYPHONtc 21:46, 11 July 2007 (UTC)
Cool, thanks Starlightblunder. - ClydeJr - talk - contrib 02:59, 12 July 2007 (UTC)

foxbot issues

i've ran foxbot updates some the past days (mostly updating lowlvl items when i'm adding lootboxes to the lowlvl dungeons), and have encoutnered a few issues. lazy git as i am, i didn't write them down, but here's some that come to mind atm;

  • items that start quests have their quest being linked to Quest:id instead of Quest:name, e.g An Unsent Letter
  • spelllink isn't used properly, but instead just a plain text line is added. i can however see this being "intentional" due to not all spelllinks existing, and it'd be better to create plain text than a dead link. however, either a check could be done, or it could perhaps generate spell pages too? .. unless that information isn't existing on the armory, that i do not know.
  • perhaps add a [[Category:Instance:<instancename>]] to the items found only in specific instance?

all in all, this bot is quite useful. but perhaps create a seperate sandbox for it instead of using the /sandbox/1 one? Taurmindo | talk contr  13:43, 13 July 2007 (UTC)

At the time of writing foxbot, {{tooltip}} documentation was lacking, so I assumed starts quest parameter just has to be speficied; providing the ID was a bonus feature; I'll see what I can do about using the quest name instead. Spelllink isn't used intentionally - armory does not expose spellids, and they're unobtainable except by datamining wow's cache files. Instance drop detection is rather tricky, so that'll probably have to be added manually. -- Starlightblunder 23:34, 15 July 2007 (UTC)

Foxbot's enter key is sticky

I draw your attention to this diff. See them 3 newlines after the tooltip? BAD BOT! NO! There shouldn't be any whitespace between the tooltip and the intro text, just a single newline.

Edit: I win! I hate how these diffs show up... nevermind the enter issue, but please read the next two requests as they are valid!

There are also remnant {{clrl}} calls at the end of the intro sections from the days of icons being on the left side. These should get removed if they are seen, we have no reason to clear floats at the start of an item page anymore.

Also, side note, the noTOC magic word shouldn't be used on item pages... they are generally short enough that auto-TOCs won't show up. if they're long enough for a TOC to show up, it should be placed there to aide nav. The bot should remove these when it finds them in item pages. TeжubԎ Ҩ Ѡ 08:03, 16 July 2007 (UTC)

I don't think there's anything wrong with your original issue either - Foxbot in tiponly mode (only replacing the tooltip/old set inclusion mechanism) is prone to creating excessive whitespace. I've added code to counteract this now, so it should be fine from here on forward. NOTOC and {{clrl}} will also be removed automatically -- Starlightblunder 23:20, 16 July 2007 (UTC)


Looks like this bot might be creating content with a spelling error: "This item can be aquired by ....". Should be acquired. Eg Deathwing Brood Cloak. Harveydrone 18:20, 23 July 2007 (UTC)

Someone brought that up in IRC earlier; fixed it a bit before you posted. -- Starlightblunder 20:45, 29 July 2007 (UTC)
Cool. I gotta try that IRC thang. Harveydrone ( talk | work ) 00:35, 31 July 2007 (UTC)

Offline queue?

So you don't stay on IRC at all times (bastard)... could you maybe create a wiki page we can edit to queue up tooltips? Heck it could use the same commands as IRC even. When you launch up the bot first thing it does is grab that page, edit the pages requested, and empty the queue page (or flag each completed item maybe). Would be really handy since I never see you on IRC :P TeжubԎ Ҩ Ѡ 08:19, 24 July 2007 (UTC)

This would also be really nice for people who don't go on irc... like me. --Jiyambi t || c 18:56, 24 July 2007 (UTC)
That's actually a nice idea - I'll look into it. -- Starlightblunder 20:45, 29 July 2007 (UTC)

bot isn't parsing

"%" correctly. Not sure if this is global, or only reclusive to settip, but this is the relevant edit. Have a look? --Sky (t · c · w) 07:51, 28 July 2007 (UTC)


How about having only one bot up on IRC? Set up a SVN for it and share code beetween foxbot, kasobot, laurlybot and grab some ideas from newsbot (!jobqueue for one). Yes/No ? --Adys 06:26, 29 July 2007 (UTC)

Could be interesting - but most of those are written for different environments / in different languages, so we're probably talking about rewriting the functionality of all of those against a common base. This would eventually be a fun thing to do, but I'd want to get Foxbot's core cleaned up for reuse before we go about rewriting it or other bots. -- Starlightblunder 20:45, 29 July 2007 (UTC)
That'd be the main idea aye. I thought laurlybot was coded in lua so scrap that, but can always get the core ideas into the bot. I suck at coding and got no idea how much it takes to set up a svn but I might be able to provide a stable server for it, I'll look into that today. As for cleaning the code up, that's probably the occasion to do so. --Adys 23:40, 29 July 2007 (UTC)

Random item enchants

Please update how the bot styles this table... see this change. I've updated a number of these. Also, how about sorting the list by the enchant suffix (drop 'of' and 'the' from the sort text, of course), it would make the tables a tad nicer to read. Keep up the great bottink! TeжubԎ Ҩ Ѡ 04:54, 30 July 2007 (UTC)

"Marked Patrolled"

Who does the patrolling? How do you determine which are patrolled? Educate me! :) --Eirik Ratcatcher 17:29, 3 August 2007 (UTC)

Internal within WoWWiki:RC Patrol community group - edits that have been patrolled will not be marked with red exclamation marks on the recent changes list for people who can patrol pages. -- Starlightblunder 00:22, 5 August 2007 (UTC)

foxbot quirk

I recently stumbled upon Black Whelp Scale, foxbot overwrote it but did not include all information. It was long ago so perhaps this bug is already fixed, but want to notify you. --Hurax 08:36, 27 August 2007 (UTC)

Not a bug as such - just people that request those pages request them to be replaced entirely, rather than simply have the tooltip code replaced. I am still working on more graceful merge feature, but so far it's up to the people requesting edits to figure out what they want to be done to the article, and fix issues afterwards. -- Starlightblunder 22:36, 3 September 2007 (UTC)

Where are you?

You've gone all quiet recently :P Hope all is well! I suddenly thought of you due to ... Illidari Cloak. ;) Kirkburn talk contr 16:02, 8 September 2007 (UTC)

why is it

User:foxlit but user talk:starlightblunder? :| --Sky (t · c · w) 04:35, 11 September 2007 (UTC)

To facilitate endless confusion! (new messages notification does not check whether the page you redirect your talk page to is modified) -- Starlightblunder 16:50, 12 September 2007 (UTC)

Foxbot still running?

I haven't tried to trigger it lately, but wondering if it will still work. -- Gengar orange 22x22  Fandyllic (talk · contr) 5:50 PM PST 5 Nov 2007

Yes; I intend to do a large pass when 2.3 changes hit the armory. -- Starlightblunder 21:13, 9 November 2007 (UTC)


Yeah, I'm guessing this is the right place to comment... I'd already mentioned my dislike of Reagentbox on the template page. Was there general agreement to use it? (A pointer to the discussion would be welcome.) I'll admit - it's not comfortable being a lone dissenter. Grumbling here to avoid grumbling about a previously decided topic in the more public Village Pump. --Eirik Ratcatcher 22:58, 28 November 2007 (UTC)

I think the end result of the last time this was brought up was that no one cares enough, and there aren't really any interesting alternatives. --Starlightblunder 11:37, 30 November 2007 (UTC)

Bonusarmor changes to Tooltip

Your changes broke how regular armor appears in the tooltip. See General's Lamellar Greaves. --Pcj (TC) 16:20, 7 December 2007 (UTC)

Kirkburn's reverted it for now...I think you missed some brackets or something. --Pcj (TC) 16:45, 7 December 2007 (UTC)


I am a very unhappy little Sky as I write this. I was hoping to deprecate the entire series of these templates (other qual-color[s], through the use of css classes) when I stumbled upon this. When your bot runs, it uses it for <Random Enchantment>... Is there anyway to fix those other than by hand? :( I can change the template so it uses the class (which it doesn't need to...)... Sigh. --Sky (talk | con | wh) 09:13, 23 December 2007 (UTC)

It'll use a class from here on forward, but there's no good way to change existing articles - that would be a candidate for botting along with changes in tooltip syntax, but there is no good way to do that yet either. -- Starlightblunder 13:18, 23 December 2007 (UTC)

Zul'Aman timed event items

I just noticed that Foxbot updated all the Zul'Aman items -- very cool. The default "source" text for items from the timed event states "item can be looted from the reward chest after successfully doing the timed events on Zul'Aman". This is a bit of a personal request, but in the future would it be possible to say "item can be looted from a reward chest after successfully doing the timed event in Zul'Aman", or something similar? -- Adonran 06:30, 25 December 2007 (UTC)

I don't have a good way of doing that at the moment, unfortunately. The text you're referring to was likely contributed by other editors, while Foxbot item updates were likely technical changes to tooltip code. Foxbot doesn't really get into that much detail in the source section. -- Starlightblunder 00:13, 3 January 2008 (UTC)

Set problems

With the set of [Gloves of the Corruptor]. --PcjWoWWiki admin (TDrop me a line!C62,301 contributions and counting) 03:11, 29 December 2007 (UTC)

No {{elinks-set}} on set page -> no automatic {{settip}} update -> old settip box formatting; just fix settip usage on that set page according to Template talk:Settip. -- Starlightblunder 19:30, 29 December 2007 (UTC)


Can you help me seperate the npcboxes on my Gladiator Teams please?Also get rid of the [[]] on the race part of the npcbox on Gyff?Thank you very much! Airiph/T/C/B 21:49, 2 January 2008 (UTC)

Use |races= instead of |race= as part of the npcbox to fix your ]] problem; not sure what you want splitting on your gladiator teams page. -- Starlightblunder 21:54, 2 January 2008 (UTC)

Ok thank you! Airiph/T/C/B 21:58, 2 January 2008 (UTC)

Try line breaks to separate the npcboxes, such as "clr" in double curly braces. We're getting a bit off-topic, so if you wish let's continue this on your talk page or mine. -- Adonran 04:55, 3 January 2008 (UTC)

Thanks for foxbot!

Just wanted to say thanks, in particular for fixing the "droped" spelling thing. -- Harveydrone 00:57, 3 January 2008 (UTC)

Was this foxbot?

I'm still learning how to read these history logs... Arcane Armor Kit is messed up. And the last change was made by Foxbot. I'm hesitant to revert any changes, especially since when I go into history and click on the date of the Foxbot edit, it looks correct. Why does it show up as a bunch of nonsense on the actual page? -- Mordsith - (talk|contr) 16:27, 3 January 2008 (UTC)

I'm assuming you're referring to a bunch of code appearing on the linked page; that would be a wiki glitch from a few hours ago and is unrelated to the edit history. It should go away without user intervention -- at least, it's no longer appearing that way for me (you may be able to purge the page cache to force it, but I can't currently see any pages messed up in that fashion to test). -- Starlightblunder 17:25, 3 January 2008 (UTC)
That must have been it. It looks fine now for me too. Thanks for the quick response. =) -- Mordsith - (talk|contr) 17:29, 3 January 2008 (UTC)

Pages not being updated

Why are certain pages not being updated that have been tagged for a while? Examples include Cyclone Shoulderplates and Cyclone Helm. Is it because their date is December 2007? --Tiwuno 14:21, 9 January 2008 (EST)

Queue sweeps aren't a very regular process, so items may occasionally stay tagged for a longer period. -- Foxlit 00:52, 12 January 2008 (UTC)

Errors in Season 2 and 3 items

Every piece of armor with the Merciless or Vengeful prefix is lacking the corresponding prefix in the set= line of the tooltip. The result is 170 erroneous tooltips, such as that on Merciless Gladiator's Wyrmhide Tunic. --Tiwuno 03:19, 25 January 2008 (UTC)

The sets you are referring to do not exist. -- Foxlit 14:48, 25 January 2008 (UTC)
Huh. Funny how the sets exist in Wowhead but not the Armory. Ah well, guess I'll have a blast updating them all by hand. Tongueout --Tiwuno 22:07, 25 January 2008 (UTC)

Merciless Gladiator's Battlegear

Merciless Gladiator's Battlegear refers to the Onslaught armor set later on. The author who added that bit hasn't contributed since. Don't suppose you know what the proper text should be?

And ... I disagree that displaying the item tooltips instead of tabulating the data provides more information to the user. However, since I expect that the armor sets were looking for 'regularization', that was the solution chosen. Regularization is good. I've got enough other things to do, this doesn't even flicker my "I gotta change it" meter. Just thought you *might* have some use for the feedback. --Eirik Ratcatcher 23:01, 13 February 2008 (UTC)

User Editcount

Was wondering, what would happen if I put the template on one page, which I then transcluded to my page? Would Foxbot attempt to edit both, or only the one with the template? I ask this, because I don't want the bot editing my page directly, if possible. --Sky (t | c | w) 10:05, 18 February 2008 (UTC)

I Think an error occurred during the site changes... seems I was credited for double what I had actually done... This might be the case with everyone using the template. Without myself actually going through and counting all the edits, what do you think would be the solution? User:Coobra/Sig3 04:39, 29 March 2008 (UTC)

Possible; I ended up changing the key used to produce the state hash - problem takes care of itself after that (Foxbot refuses to recognize saved state and counts from scratch). [Not that initial recount went smoothly, but it's all fixed now.] -- foxlit 03:04, 30 March 2008 (UTC)


Thanks for unscrewing my user page... --Azaram 23:45, 21 February 2008 (UTC)

Description of questbox changes

Could you put a description of the level display changes you made to {{Questbox}} in Template talk:Questbox? When you make a major change you should try to describe it in the discussion area.

Also, I'd like to request you add back the actual level of the quest and perhaps have the colored level info come after the levelreq info. Please also add a small bit in the help area called Template:Questbox#Required_fields -- Gengar orange 22x22  Fandyllic (talk · contr) 2:03 PM PST 24 Mar 2008

It's only a display change - there are no actual changes to the template syntax or required parameters, so there's no real additional documentation to add to the help area.
I lost track of the fact that I ended up removing quest level from the strip - I can't think of where to put it in just now without things becoming confusing. Any suggestions on formatting there? -- foxlit 00:42, 25 March 2008 (UTC)

Foxbot erroneously removing <onlyinclude> tags

Hiya. Foxbot seems to be erroneously removing <onlyinclude> tags around tooltips, eg on Darnarian's Scroll of Teleportation. The result was the whole of that article being included on Shattered Sun Offensive, making the quest table for the Sun's Reach daily quests look quite ugly. As far as I can see, the <onlyinclude> tags should always be there in that type of article, going by Help:Tooltips, so I have re-instated them in that particular case - I'll leave it up to a bot to fix any other instances of the problem. --Murph (talk · contr) 03:46, 5 April 2008 (UTC)

Template:Userbox parser problem

Template:Userbox is partially broken by the new parser. Kirkburn  talk  contr 15:58, 28 April 2008 (UTC)

Questbox levelreq faulty

Your addition to questbox fails to properly observe level required to obtain the quest. Could you either correct it, or revert your change until you can? It misleads the reader. (For what it is worth, I don't find the color display that useful to me. But that's a different issue.) --Eirik Ratcatcher (talk) 17:15, 21 May 2008 (UTC)

Considering the required level is shown in parenthesis after the color strip, I don't quite think there's a lot of misleading going on. Is the output on Template talk:Levelrule acceptable to you? -- foxlit (talk) 22:07, 21 May 2008 (UTC)
yep. --Eirik Ratcatcher (talk) 00:14, 23 May 2008 (UTC)
Changed questbox to use that instead. -- foxlit (talk) 23:09, 30 May 2008 (UTC)

sandbox edit history

Were it me, friend, I'd have changed the link I'd already put in the pump to point to the history item. Or something like that. You know what I mean. :) --Eirik Ratcatcher (talk) 18:55, 6 June 2008 (UTC)

Foxbot problem

I'm not sure if this is still a problem, but when it overwrote the categories in this edit, it reverted to the old category scheme with armor associated items. It has placed more than a few items in similar straits, as seen at Special:Wantedcategories.

Has that been fixed since then?... --Sky (t · c · w) 07:53, 24 June 2008 (UTC)

It was asked to replace the page entirely, which it did; the new category structure doesn't easily lend itself to auto-generation. I could remove categories altogether, but that seems to be a bigger disservice than the current situation. -- foxlit (talk) 13:11, 24 June 2008 (UTC)
I would be in favor of removal if this keeps occurring; completely regenerating the page, and then going back and fixing the categories is against the idea of a bot generating the page in the first place. I would much rather have the pages show up in Special:Uncategorizedpages rather than Special:Wantedcategories. --Sky (t · c · w) 21:22, 26 June 2008 (UTC)
The old/new categories do map, just not always one-to-one. IE gloves + leather --> WoW leather hand items... --Eirik Ratcatcher (talk) 19:27, 27 June 2008 (UTC)

Thanks for help

Noticed that you fixed my problem. Thanks for the help!
Hewbie (talk) 10:55, 9 July 2008 (UTC)

Me too! Template:Achievement Much obliged. -Howbizr (talk) 14:57, 19 October 2008 (UTC)
Check out Template_talk:Achievement#Bullets_break_Points.


I think Foxbot is reversing the attributes when creating item pages. Rolandius Paladin (talk - contr) 02:44, 3 December 2008 (UTC)

Field Duty

I have altered the Vote description on [[Talk:Quest:Field Duty|Field Duty]] to better reflect what I intended. Unsure of protocol in this situation, in lieu of wiping the voting box, I am asking each current voter to consider whether his/her vote reflects the new description. --Eirik Ratcatcher (talk) 22:57, 4 March 2009 (UTC)

Includeonly WTFing

You added numerous instances of <includeonly></includeonly> to various templates and help pages (see: Help:Item articles/Preload). Before I dismiss them out of hand, would you please explain just what they accomplish?

  • There is no text between the tags, so nothing gets included/excluded.
  • If they are there to break up other tags, that would be useful primarily if the page was being "displayed-as-code" (for cut-and-paste). Which on my computer it isn't. 'pre' tags may be more useful in this case.

So what am I missing? --Eirik Ratcatcher (talk) 22:12, 11 March 2009 (UTC)

The page is used as preload content; it is intended to render correctly in one place only: the create new article editbox. -- foxlit (talk) 23:03, 11 March 2009 (UTC)
I find it awkward that when you encounter an exiting article that is marked for boilerplating, your best option for getting that boilerplate is via a new article of that type. Yes, I do want to both have and eat my data-cake. --Eirik Ratcatcher (talk) 16:24, 12 March 2009 (UTC)

Edit count

Star, your bot keeps editing the edit count template on my user page so that it no longer updates automatically. Please get it to stop, because it's getting annoying having to keep reverting changes twice a day. Jormungand IconSmall Rogue  talk · contribs 07:52, 17 March 2009 (UTC)

At the time of its introduction, {{Special:Editcount}} triggered problems with the page cache / job queue, perhaps compounded by being transcluded in a signature over a large number of pages. {{User Editcount}} was designed under the assumption that someone would manually update the |contribs= argument rather than using {{Special:Editcount}}. I'm not prepared to assert that this is still a problem; you can add |ignore= to the template tag to force Foxbot to not alter that particular instance of the template -- or you could just let it be, and settle for some update granularity. -- foxlit (talk) 10:03, 17 March 2009 (UTC)
Ah, OK. Thanks for that. Jormungand IconSmall Rogue  talk · contribs 16:12, 17 March 2009 (UTC)

Itembox is causing discontent.

The Template:Itembox is a big problem for me. And consequently, it is a problem for Gourra. As in, I make an edit, Gourra follows behind and undoes it, and there begins an edit war.

As I stated to him, my single biggest problem with the template is the humongous icons it generates. I look in Template:Itembox/Row and I see evidence that some portion of the Template:Item template had been tried, and perhaps discarded. My own experiments to produce an Itembox/Row template that yields reduced sized icons has so far met with failure.

As the most recent editor of the Itembox template, I ask you: can we reduce the icon size to where I can put up with it being in a page? There are other issues I have with itembox, but those can be taken up after this one.

If there is no hope of reducing the icon to the size used by Template:Item, is Itembox a required part of the item page standard? (And for that matter, the quest reward page standard, where the same template causes the same problems.) --Eirik Ratcatcher (talk) 20:25, 31 March 2009 (UTC)

There is a line starting with |{{Icon| and ending with 3}} in that template. The 3 is the size argument passed to {{Icon}}; you could change that to one of the other values get a smaller icon. An alternative solution is to just avoid using {{Icon}} altogether, and simply plug the image name return value into a standard image tag which can then be sized as usual.
I don't share the opinion that the current icon size is humongous -- it is just large enough to display the icon without much distortion, and the vertical space it consumes is offset by having two columns in that table (because itembox also doubles for some vendor / materials costs tables, the icon is about as large as two lines of text that may end up being adjacent to it). While the cell padding may be excessive (and that can be adjusted), I don't think replacing itembox with an unordered list of item links in an article would actually make them take significantly less space.
I do not believe that there is any up-to-date policy governing what formatting should and shouldn't be used on an item/quest page. My advise would be to establish some form of consensus before changing them from the current format, which seems to favor using the box templates. -- foxlit (talk) 21:46, 31 March 2009 (UTC)
Of course, it is the "size of two lines of text" bit, and the "two columns" bit that I find most unpleasant about the current template. Our arguments are thus equivalent. Under what circumstances is comment text (one or two lines) being used? And could that be moved to a separate template? If so, I would ask for that separation. See also my comments under Template:Itembox and on Geenia Sunshadow.
The next biggest barrier to making an up-to-date policy on such formatting is apathy. How many votes languish for weeks or months? --Eirik Ratcatcher (talk) 21:01, 13 April 2009 (UTC)

thanks for the thought

Foxlit, feel free to take a pass at a slightly different color scheme on this mockup I'm working on. I appreciate the suggestions and help! Gil (talk)@Wikia 01:26, 13 April 2009 (UTC)


Hey man, thanks for cleaning up so much junk on the Wiki. Macros that people post tend to have a limited shelf life... roughly ever patch sees some changes to the way macros work, or which spells are on or off the GCD. To this end I proposed we add a version number to each macro, but you took out my edits. Please come up with an alternative way to get people to list the version of WoW the macro was designed for so that we can better clean up old macros in the future. Thanks! —The preceding unsigned comment was added by Shotgirl (talk · contr).

I have several issues with the {{macronav}} edits I reverted:
  1. You were editing a widely used navigation template, thus prefixing your "label macros like so!" note to pages that do not contain macro listings. Navigation templates aren't meant to provide anything other than navigation; adding content to them would break articles that you did not intend to alter.
  2. I believe that the scope of changes made to the macro system in patches since 2.0 is greatly exaggerated; most slash commands are stable and maintain their meaning.
  3. I'm not convinced that widespread stamping of "Validated: x.y" labels on macros would be more helpful, then, say, employing a single section marked with {{ood|May need an update for x.y}}.
Ultimately, only (1) is significant: I'm not opposed to your idea, I just think you're applying it to the wrong page. Feel free to either create another template to contain your foreword, and add the template to relevant pages, or just add the suggestion to relevant pages directly. -- foxlit (talk) 16:31, 26 April 2009 (UTC)

You know more about the Wiki than I do. I trust your judgment. I would like to see an example format macro on every page that has example macros. Does this make sense to you? I would also like to see a link to the "Useful Macros" page from the "Useful Class Macros" nav bar. It's got a link to making a macro, the macro API, it makes sense to have a link to example macros in the same place. I agree that I exadgerated many of the issues with 3.1... but only in that a lot of the changes happened in 3.0 (or before) and people never updated their macros. Still using /use for mounts and pets for instance... ha. Stuff like that all needs to go. With a Validated version on each macro at least we know how old they are and when they can safely be ignored. Please give me a hand cleaning up these pages. Thanks!

RE: "Increases 21"

I blame CTRL+V for breaking down on me. --User:Gourra/Sig2 15:53, 25 May 2009 (UTC)

Item template

Some change, perhaps to Item, perhaps to Tooltip, perhaps to Itembox has caused some new and novel problems. Prior to whatever this change was, {{itembox}} would display a generic icon and a redlink for pages that did not exist. Now, it omits them. Can you discover what has changed? --Eirik Ratcatcher (talk) 21:58, 18 June 2009 (UTC)

Personally I'm not sure what has changed, or why, when and how. All I can see though is that items that doesn't exist aren't transcluded in text, but if you use the preview first when editing, you can see at the bottom under "Templates used in this preview" that it is used. Again, I have no idea why this is the case. --User:Gourra/Sig2 22:39, 18 June 2009 (UTC)
It used to generate a "redlink" but now renders null, we will probably have to do something like:
{{#if:{{:ASDF}}|show tooltip|show generic}}: show tooltip --PcjWoWWiki admin (TDrop me a line!C62,301 contributions and counting) 22:49, 18 June 2009 (UTC)
{{Item}} fixed (for now) by using #ifexist:. --User:Gourra/Sig2 22:54, 18 June 2009 (UTC)
...which I was going to change to #if: but pcj got there before me. --User:Gourra/Sig2 22:55, 18 June 2009 (UTC)

Thanks, folks. --Eirik Ratcatcher (talk) 21:39, 19 June 2009 (UTC)

Around Wikia's network

Random Wiki