Talk:Main Page/archive3

From TheKolWiki
Jump to: navigation, search


  • Shouldn't the date on the main page switch at the same time as the game rolls over? Seems like the wiki is one hour west of the game. Just change time zones to Eastern and it should work right.--Jef 22:08, 24 July 2006 (PDT)
  • Can someone take a look at the "discussion" page on Mick's IcyVapoHotness Rub? Thanks!--Mick 15:34, 11 June 2006 (CDT)
    • In case you haven't noticed already, I already did. It is NOT a reference to you.--Kiltan 20:35, 11 June 2006 (CDT)
      • it's not, huh? why dont you ask mr. skullhead about that. --Mick 12:47, 12 June 2006 (CDT)
      • So, can someone change it please?--Mick 19:30, 14 June 2006 (CDT)
  • I suggest changing the text 'SPLAT! WHACK! BOOF!' to something like 'SPLAT! WHACK! BARF!' Let's face it: barf is funny. Not only is it funny on its own considerable merits - it's also a reference to the inimitable River City Ransom. Or at least, that's what I prefer to think. Also - is there any place to list this kind of 'general reference?' Maybe on game mechanics somewhere...? -- Shadowless
    • This has been changed, until further notice. Further notice being until somebody objects. --Alpaca 13:38, 2 Nov 2005 (MST)
  • Today's featured article isn't changed daily. Renaming it to "featured article" would be nice. Furthermore it would be nice if that article follows actuality. So right now it should be either about the rift either about the plague. --Twopeak 09:06, 2 Nov 2005 (MST)
    • Write some! I can add featured articles to the rotation as soon as they're written. I'll take a look at your first request later to-day. --Alpaca 13:38, 2 Nov 2005 (MST)
    • Okay, I see what you're saying. It's true that the featured article isn't different every day, but follows a rotation. This is primarily because we lack featured articles. As for renaming the front page title to "Featured Article" from "Today's Featured Article," I really don't see the necessity. --Alpaca 20:17, 2 Nov 2005 (MST)
  • Dear Hermit, the Collection Collection page has nothing about the Decent Docent. Don't you think it should be updated? --Cfbandit 13:44, 8 Nov 2005 (CST)
    • Well, there are a variety of things you can do. You could insert this tag {{NeedsContent|comment=Replace this text with an actual comment on what needs to be done}} into the page at the top. Or, if you have something to say about the Decent Docent, go ahead and edit it in! The wiki is a community for everybody to edit, and you need no approval to insert some minor bit of text into a page. (On the other hand, when dealing with larger issues like category or template creation and implementation, discussion is a good thing.) Good luck! --Alpaca 17:30, 8 Nov 2005 (MST)
  • Two questions: 1) What MediaWiki version are we currently on? I tried using a template feature that requires version 1.6 (default value for argument) and it didn't seem to work, so I'm guessing we're on 1.5 or earlier. 2) Also, the Special:Templates page seems to have disappeared; was that intentional, or an unexpected consequence of the server move, or what? -- Old Ned 23:59, 24 November 2005 (Central Standard Time)
    • We're currently running 1.5.2. We don't do dev/beta releases. As for your second question, Jinya and I worked on that some yesterday. The special page mod the wiki was using previously was wierd, in that it didn't follow the special page format wherein an extension was made to intialize it, but the page somehow got initialized directly. So, while we have the actual file, we're stil figuring out how to make it tick. --Alpaca 07:39, 25 November 2005 (Central Standard Time)
      • For making special pages, have you seen the Media Wiki Meta Wiki's Writing a new special page? --JRSiebz (|§) 18:09, 25 November 2005 (Central Standard Time)
      • /me dances in place cursing in jubilation. I got a Special:Templates plugin to work, error/warning free! It was one of the most frustrating things I've ever written ;-) --JRSiebz (|§) 22:25, 25 November 2005 (Central Standard Time)
        • That page doesn't seem to work for me, giving the standard "no such page" message. Did you just get it working on your own wiki, and Jinya is yet to initialize it here? --Alpaca 08:02, 26 November 2005 (Central Standard Time)
          • I get the same error: "No Such Special Page -- You have requested a special page that is not recognized by the wiki." Any further progress on this? -- Old Ned 00:59, 5 December 2005 (Central Standard Time)
          • I emailed it to Jinya over a week ago along with a version of the moons plugin which doesn't generate a php 5 warning, maybe it was lost in the mail, harhar. --JRSiebz (|§|) 15:08, 5 December 2005 (Central Standard Time)
            • Whoops. Sorry about that. It didn't get lost in the mail, as I had it tagged as important... It just got lost in the moment. I couldn't do it at the time I got it and so it just sat there. I was also blithely unaware that it also contained the SpecialTemplates stuff. Sorry about the delay, but it's uploaded to the right place and included and should be working now. --jin 20:19, 5 December 2005 (Central Standard Time)
            • No worries, I often set things aside to do them later and then forget about them entirely. So um..... say what now? ;-) --JRSiebz (|§|) 20:22, 5 December 2005 (Central Standard Time)
    • Also, version info see Special:Version, and for an alternate to Special:Templates you can go to Special:Allpages, choose "Template" in the namespace dropdown, and press go. EDIT: you can also just directly go to Special:Allpages/Template --JRSiebz (|§) 18:02, 25 November 2005 (Central Standard Time)
      • That doesn't quite work. The link gives all pages in the main namespace, alphabetically after "Template." I'm too dumb to figure out a wikilink for it, but this link works well enough. --Alpaca 20:04, 25 November 2005 (Central Standard Time)
  • We should add a link to with instructins to go there for spoilers when the wiki is down / when you don't need the wiki's picture/adventure/text goodness to save bandwith? --D0om 13:04, 27 December 2005 (Central Standard Time)
    • Well, if the wiki's down, and you can't access its front page in the first place, putting a link there to another page wouldn't do much good... As far as bandwidth saving goes, there's not much chance of it happening voluntarily, from the userbase. A few concerned citizens might try elsewhere, but the vast majority will keep hammering the wiki. And turning off functionality might save bandwidth, but it also would stop the wiki from being what it is. It might, however, be possible to do some html caching of fairly static pages and put the result on another server, but this is fairly complex, and by no means going on right now. --Alpaca 21:19, 27 December 2005 (Central Standard Time)

  • I suggest a firefox (or any other program) RSS feed for the wiki.
    • There's an RSS feed of the updates from Coldfront. What else is there to feed? --CountD 09:14, 6 June 2006 (CDT)

  • 1. All the text in the wiki has shrunk and is harder to read. 2. The older "the kol wiki - at - kol coldfront" box with all the colors is overlapping the newer "kingdom of loathing - the kol wiki" box. The bottom of the latter box (the black and white one) is lined up with the top of the blue box containing the advertisements, leaving a blank white area to the left of that blue box and a blank white area above the blue box. Other than that I love the new wiki.  :) --Grampamoses 14:36, 30 May 2006 (CDT)
  • I'm used to the new wiki's layout by now, but one thing is still annoying me. It's extremely hard to tell regular text from a link without rolling over it. Would you make links underlined? Pleasey? --CountD 09:14, 6 June 2006 (CDT)
  • I suggest we put something on the pages to indicate when varius locations/items/recipes/whatever were implemented. It wouldn't have to be particuarly exact, month and year would be fine. This would help historians and spades alike as they attempt to discern where the Kingdom is heading. We also have just about every other piece of information on the wiki for the items... I'm treating the lack of response as an affirmation... will get started on this as soon as possible.--Soupersalad 19:54, 30 may, 2006(PST DS)

  • Ugh! I hope that the red and black is just special for 06/06/06 and isn't permanent. It's poorly contrasted and looks horrible. --Ithanox 10:28, 6 June 2006 (EDT)
    • I agree - it gives me a horrible headache. Thankfully, it will be gone by tomorrow. --Quietust 09:52, 6 June 2006 (CDT)
      • i prefer the red. dont know why but i am strangely attracted to it. but that is just me Rburp 11:05, 6 June 2006 (CDT)
        • I like the red and black. Please keep it, or give us the choice. It's groovy. --Rai 16:21, 6 June 2006 (CDT)

  • Shouldnt the LAAAAME Observatory be a link to The Grim Grimacite Site? It does have something to do with the comet and all.~steveO 12:28 AM 6/8/06 (EST)
    • No. Though they are related, they are not the same. If anything, the observatory page should redirect to the memorial. --Nathew 23:17, 8 June 2006 (CDT)
  • there should be a meatpaste index (This comment added by Gando at 16:28, 11 July 2006 --Jonrock 15:49, 10 August 2006 (CDT))

Moon Images

  • I think the moon images appearing on the front page should be updated to reflect the new minimoon. --Nathew 23:19, 8 June 2006 (CDT)
  • Well, duh, but we haven't even gone through a whole set of phases yet (2 kol months (32 says) maybe longer depending on how the minimoon will/could move). We need to figure out all the phases, then figure out the new math, than all moon pages everywhere will be updated. The ronald and grimace phases ares till accurate, it's just that goofy minimoon, if it doesn't phase/rotate in a repeating 16 or 32 day cycle, that increases the total amount of possible phases alot. --JRSiebz (|§|) 23:29, 8 June 2006 (CDT)
    • Just an update, I have the new moon sextension basically done (locally), there are just a few dates where the minimoon will be in the middle and can't tell whether it will be full (like it has been when in the middle of ronald and grimace) or not. Boozember 3 is the first one. I almost have all the new moon images converted to tranparent .gifs too. We just need to wait long enough to confirm that what we think the moon phases will be, are. So just be patient, if Jick throws a half full minimoon at us, everyone is gonna be all screewed up. --JRSiebz (|§|) 23:13, 13 June 2006 (CDT)
    • So far so good, Boozember 3 was a full minimoon, the next trouble phase is when the minimoon is in the center is on June 30, (Dougtember 6), if it's full like it has been when in the exact middle, I should have the moons plugin updated that day, else we'll all have to figure out what dictates the minimoon's phase when its located there. --JRSiebz (|§|) 23:27, 18 June 2006 (CDT)

Images Being Blocked

I've noticed that some non-ad images, like the Malevolent Tofurkey, are being blocked by my Adblock extension on firefox. I think it's because the path is "thekolwiki/images/a/ad/Tofurkey.gif" which has /ad/ in it. Is there any way to change this in the wiki? --flatluigi 21:26, 23 June 2006 (CDT)

  • How is this the wiki's fault? The wiki didn't make your adblock filter set over-sensitive. The adblock filterset G? is it now? often filters out too much. Either disable adblock or use a custom (smarter) set of rules. Maybe a whitelist? --JRSiebz (|§|) 21:32, 23 June 2006 (CDT)
  1. I fixed this by adding "@@*" to the filter, so nevermind. :) --flatluigi 21:31, 23 June 2006 (CDT)

Hanging on Moon Pages

I am unable to access the Moons page, or Jekyllin hide belt or anything else with Template:Moonrow. Furthermore, after trying to do so I can't access anything else on the wiki until I clear cookies. Maybe it's just me, but the problem is repeatable and occurs in both firefox and explorer. Anyone else?--DirkDiggler 15:38, 24 June 2006 (CDT)

  • It's a matter of extreme server lag due to the way the moonrow template is implemented. If you wait a few minutes, it will eventually load. The moonrow template really needs to be rewritten to be more efficient. --Quietust 15:40, 24 June 2006 (CDT)
    • Well, in theory, it should be pulling the page from the parser cache... it should only be re-parsing it if someone edits the page (or once a day after rollover when someone clicks the purge link)... in practice it doesn't seem to be doing this as much as it could be. I'll take a look into making it more efficient, but no guarantees, the parser isn't particularly clever about caching stuff... each row needs the current date in about 15 places, but instead of caching it, the parser ends up parsing {{moonrow/today}} about 15 times... and that == slowdown. If all else fails we can think of something else clever to do with the Moons page, maybe splitting off a page with a complete table with all 176 rows, and linking to that, just leave the algorithmic explanation on the Moons page... In the meantime, I'm removing the table from the pages, to help with the lag... Phlip 05:33, 27 June 2006 (CDT)
      • There, the evil template's now unused. Phlip 06:34, 27 June 2006 (CDT)

There are two things we can do.

  1. Ask JRSiebz to modify the old moons extension to work with your new formula.
  2. Think of something really clever.

Of the two options I think the first is much more likely to end up well. Here are some things to think about though....

  • Instead of having it call the template, could we instead have it do the expression inside of itself each time?
  • Does the expression template disabe the cache?

--SomeStranger (t|c) 07:46, 27 June 2006 (CDT)

  • (It's getting late at night here, so this post is mostly stream-of-conciousness...) I agree that updating the custom extension is probably the way to go... the main problem being that I can't play with it if we do that... :-P. Expanding all the expressions would work, but probably still take just as long to parse, and would make the template even more ungainly. The expressions shouldn't be disabling the cache, and after I set it all up I noticed that clicking on the "purge" link definately took longer to run than just loading the page... I think the cache wasn't enough though... either expiring to soon, or something. I think there's no way around the wiki parser's inefficiencies here... some PHP code is going to have to be written... I'm trying to think of a way that it can be written that would still be editable if they change it all again... try to make it more general-purpose... maybe if I write an extension to add some more magic words? Like {{CURRENTKOLDAY}} to match {{CURRENTDAY}}, ditto for month, and so on? And maybe one that does the work of {{moonrow/today}}, being the main bottleneck... Then it could still be manipulated with #expr things, but would be much more efficient, but would still allow the templates to be edited later if necessary... the only thing is to see if it's even possible from the extension API... Phlip 08:07, 27 June 2006 (CDT)
    • This is where I step aside and let you do your thing. I can put together hack job python scripts to make my bot run, but I can't for the life of me code php. If you want to learn the API for the wiki I suggest checking out the api documentation, the list of extensions that have been created already, the list of extensions currently active on the english wikipedia, this howto page for extending wikimarkup and probably all pages that link from and to those pages that I mentioned. I hope this helps =/. Good luck...--SomeStranger (t|c) 08:31, 27 June 2006 (CDT)
      • Well, it seems it's definately possible... all the hooks are indeed avaliable. Though it's not really documented, I have to trace the path through the code to see what gets called when (which is annoying). Anyways, while I was at it, I had a look at the inefficiencies of the parser functions, see if the template could be cleaned up to be lighter... turns out that if you go, eg: {{#ifeq:<something>|<somethingelse>|{{#expr:<horrible expression>}}|{{#expr:<other horrible expression>}}}} both horrible expressions will be parsed and evaluated, and then one will be thrown away... the function for #expr is called before the one for #ifeq is. Which makes sense, since the parser has to be general about it to allow new parser functions to be written, and if one of the #expr's was one of the comparators for the #ifeq then it would have to be evaluated first... but it's still inefficient, and better would be {{#expr:{{#ifeq:<something>|<somethingelse>|<horrible expression>|<other horrible expression>}}}}, which would only evaluate one or the other... I'll have to keep this in mind if I do anything like this in the future. Anyways, I think I've figured out how to get the extension working, I'll come back when I'm done. Phlip 09:15, 27 June 2006 (CDT)
        • OK, so I moved some of the basic stuff into PHP and left the stuff that should be more editable in the wikitext, and it lightened the load a little, but not really all that much (takes about 2/3 as long to load on my test wiki). There's still some heavy calculations, particularly things like {{moonrow/light}} which just aren't written for a functional language (particularly an uncached functional language) and make much more sense procedurally (understandable really, since the game's written in a procedural language). And if I offload any more into the extension then there'll be basically no advantage for it being a wiki page... so it's basically:
          1. Generate the whole page in PHP in an extension, a {{#moonrow:}} parser function or something, and lose the advantages of the wiki... if the moons change again, or a new moon-dependant item is found, few people can edit it.
          2. Just kill the table entirely and link to NO's calendar, which has essentially the same effect, but doesn't put a monolithic un-editable page in the middle of a free and open wiki site.
        • Or, in short, the choice is between "act like a seperate website, but within the wiki," or "actually be a seperate website." Personally I think #2 is the way to go here. I mean, I can write the code if you want to go with #1... but I don't think it's worth it. Perhaps a big static table with 176 rows (on its own page) would be good... but the dynamic table is dead. Phlip 10:27, 27 June 2006 (CDT)
          • Edit to add: There's also a third option, I could write a Special:Calendar page, or something like that, which would at least have the advantage of keeping it all on the same site, but I'm still leaning for option 2. Phlip 10:29, 27 June 2006 (CDT)

Would it be possible and reasonable to add back in some type message under the moons on the front page, like previously that says "______ days till _______ day." I know I personally found that extremely convenient in the past. As of right now the date and moon images alone is ok I can guestimate, but its hardly of practical utility.--Practitioner of Saucy Arts 03:12, 9 July 2006 (CDT)

New Recipes

We NEED a page with all the new recipes on it - LSK

  • I think it's a good idea to make one, if only temporarily at, say, Meatsmithing/New Recipes. Link to it from a happpy frontpagebox, let it sit there for a while until everybody is accustomed to the new stuff, and then delete it. --Alpaca (T/C) 08:00, 2 August 2006 (CDT)
    • I guess we could create a "Tuesday" page and have the update box be shown each weak with a link to that page which would also be updated telling what is new this week. You don't actually need a page with all the new recipes on it because you already have one. Try Items by number (the 1700-1799 one)--SomeStranger (t|c) 08:26, 2 August 2006 (CDT)


Any chance of having a quick link to the Elements page? Or having a link somewhere on the main page? I'm always needing to check and see what trumps what. --Nathew 04:42, 7 August 2006 (CDT)

Done. --SomeStranger (t|c) 18:05, 10 August 2006 (CDT)