RuneScape Wiki


15,924 Edits since joining this wiki
February 4, 2011

2011-12-14 - 2012-03-28
2012-03-30 - 2012-10-18
2012-10-18 - 2012-11-24
2012-11-26 - 2013-05-31
2013-06-02 - 2013-12-19
2013-12-26 - 2014-09-25
2014-09-27 - 2015-02-13
Page size: 18,563 bytes
Archive at: 50,000 bytes

Infobox itemEdit

Remember this for whenever you begin a serious rework of infobox item. I know that I said the other day there were a couple things to discuss, and they're fresh in my head:

  • Multiple parameter values
    • Particularly:
    • default (stuff like quest) could maybe use a list template like {{plist|1|2|3}} to spit out a ul with all the items. Mainly to keep things consistent with how multiple values are handled
    • value/high/low; For these, I'm thinking a template that would be like {{Vallist|1|2|3}}, and the first 2 params would automatically add "coins" after them, the last one wouldn't (because it's added by the infobox).
    • Weights (AFAIK this is just for items that reduce weight when equipped); Thinking similar to above, it would be {{Ekg|1|2}}, and it would spit out like '''Equipped:''' -1{{kg}}<br>'''Inventory:''' 2 (remember "kg" is added by infobox)
  • Make "noalch" a single param instead of "high=no" and "low=no"
  • I know we discussed value as just 1 param, and maybe pulling it from exchange pages for some items (discussed with cook too); we won't forget it, but might as well bring it up

None of this is important now, but I just wanted it to be somewhere because it's fresh in my head. You might see this message being edited a couple times if some things pop into my head that I forgot. MolMan 13:19, February 21, 2015 (UTC)

2015 RSW Family Photo Edit

Yo, I notice you haven't submitted a photo yet. You have until March 1st. Please try to get it in. Remember the dimensions should be 150x250px. Thanks, 22px-Logo.svg.png24px-TyA-pony.png 16:24, February 22, 2015 (UTC)


  • frame:getTitle() <3 (I have DPL plans with this, please tell me when you get this ticket done; no real rush though)
  • Coins 10000 for Module:Coins
  • Charm logs:
    • I'd really like to see the exact numbers added in some way
    • Not all vandalism is actually statistically unsound
    • Examples
      • 69/69/69/69 for all values
      • Obvious bluffing (i.e. extremely high numbers matching ours exactly)
      • IP doing several attempts with bad random numbers then getting a legit looking one through
        • Because of this, I'd really like to keep the CVU page, just as an easy way to see what gets blocked. I don't really want to have to check the abuse log after every charm log edit when it's much easier to see that they've done several bad edits already without even leaving recent changes
    • A point for random discussion would be removing /Charm log pages. If we put all the numbers in the summary (e.g. Script submission: 100K 30Go/2Gr/20Cr/0Bl; /* Possible vandalism */), we may have no use for subpages if everything can be merged.
      • It might even be of benefit to have a project page that tracks *all* charm log edits; i dunno

MolMan 16:19, March 6, 2015 (UTC)

RE: HiscorecountEdit

I just went to the Hiscores page and looked for the last maxed person. Guthix symbol Salix of Prifddinas Farming-icon 09:17, March 18, 2015 (UTC)

I just now realised I looked at the last person with 2595 and not actually the last maxed person >.< Guthix symbol Salix of Prifddinas Farming-icon 02:27, March 21, 2015 (UTC)

JS code reviewEdit


Would you check over/code review User:Gaz Lloyd/rev.js? I'd like to get an it imported in common.js eventually. I'm not super familiar with JS best practices, or what we want on the wiki in terms of JS structure, so let me know if there's anything that needs changing, major or minor. You can test and see documentation on User:Gaz Lloyd/Sandbox 3 (though currently missing the implementation section). Between the docs and the liberal comments, you should be able to understand what's going on, but let me know if you need something explained.

I'm away until ~late UTC on Sunday, so I probably won't respond until then if you have any issues with understanding it or whatever.

At some point I'll probably get a YG thread up for feedback/rubber stamping too.

Cheers, Quest Gaz Lloyd AwesomeEvents!99s 02:46, March 21, 2015 (UTC)

I took the close hover icon from Invalid cursor, since it was closer to the size of the ability tab things. The extras one looks best like this (in comparison to current and extras centered), but I still think it looks a bit weird. Probably should still go with it though.
I assumed there isn't a mediawiki/wikia/simple method to convert imagename.png -> full URL needed for src; if there is, that'd be better (since the ability images aren't thumbnails).
I don't think our coverage of the data used is that great (particularly of minimum/average hits). Doesn't necessarily matter too much.
I'll probably shove it though JSHint again at some point.
Thanks much! Quest Gaz Lloyd AwesomeEvents!99s 21:59, March 22, 2015 (UTC)

JS Calculators CSSEdit

Just wanted to let you know that the image used as a background in MediaWiki:Common.css/calc.css is broken. IP83.101.44.209 (talk) 14:36, March 21, 2015 (UTC)

Calculator Hiscores Edit

The last I heard from Jagex on adding CORS headers was the initial reply just before RuneFest, that it was being forwarded to the web team, so I imagine it fell through the cracks and might be worth pursuing again. Between college and a catpocalypse (cats multiply) I've been too busy to work on the calculators. That said, for my final project in Java I am writing a RS calculator, so I hope to use that experience for better wiki calculators. Have you had any luck with getting RSHiscores updated or is CORS the only feasible option going forward? - TehKittyCatTalk Wikian-Book 21:36, March 28, 2015 (UTC)

RSHiscores is a kluge, so hopefully bringing up CORS at the meeting works out and we won't need to pursue it any further. Awesome news, hopefully the meeting works out. The meeting does sound like a good opportunity for bringing up CORS headers. The change is simple on their part, makes hiscores support much easier on our part and benefits all the fansites calculator-wise going foward by removing the need for the server-side hiscores lookups on the fansites, because even Flash requires a CORS-like mechanism now. - TehKittyCatTalk Wikian-Book 22:23, March 28, 2015 (UTC)
I like the idea of an API module, originally it was avoided I think because having self-updating hiscores on user pages was popular, but using the parser function rather than Q's bot or a user script never caught on. As an update to my previous work, I ended up not completing an RS calculator as the final project, but I did learn a lot in the process. Luckily, Cook wrote the Lua in the meantime that I never got around to writing, which I think I could modify for my calculator template design if I get back to that. However, my project at the moment while AFKing for thalers is fixing up both Stewbasic and Quarenon calculators. Locally, I have working hiscores support for CORS (I wrote a Chrome extension that injects the CORS headers in the response for testing) if/when Jagex adds support, YQL, RSHS3 and RSHS2 (I regenerate the skills portion of the CSV, which turns out is still less expensive than any wiki page now that Lua is used everywhere). I plan to try YQL, then fallback to RSHS2 when YQL fails and leave CORS/RSHS3 commented out until useful to reduce size after minifying. Locally, I have also fixed autocomplete and search suggestions. My next step is better use of local storage for a proper hiscores cache including stats, autocomplete for past player names and possibly defaulting to wiki user name (when logged-in and it is a valid RS name) if no player name is known. - TehKittyCatTalk Wikian-Book 05:50, May 23, 2015 (UTC)

Jagex MeetingEdit


I'm just letting you know that sometime after Sunday 5 April, 2015, we will have a meeting over Skype with Mod Matthe and the Community Team about our future relationship.

I was about to email you on a similar matter though – we are excited about the greater flexibility this change gives us with regards to how we work together. As part of this therefore we’re really keen to chat to yourselves about how we can better support you and work with your team much more closely.
— Mod Matthe

What I'd like to do first is have a meeting over IRC, Chat, or Skype about what we want out of this. During the meeting with Jagex, I'd want to explore what Jagex wants and what problems exist. Sincerely, Ryan PM 10:40, March 30, 2015 (UTC)

It has not occurred yet. Nor has a date been set for it. I know that they, based on previous discussions from Mod Boko, were not willing to make more public APIs. Whenever it gets a date I'll let everyone know. Ryan PM 21:30, April 11, 2015 (UTC)
Okay, might have made a slight mistake, here is the quote from Fansite Staff:
Hey guys!

We introduced the API’s to help reduce load on out servers and to limit the possibility of the brute-forcing of restricted information. We would acknowledge that it is probably more restricted than it would be ideally, but it was added as a nice extra and was never intended to be developed as a mature, fully featured API feature. The restrictions that are in place are there because of load concerns which are still very active, with about half a million hits for itemdb requests in less than 48 hours and a total number of 112 million page hits in that same period.

We are going to be looking at APIs, including retrieving more statistics on usage and developing an understanding of how it is being used, with an eye to shaping future development and building more appropriate tools.

The seasonal hiscores were developed with a deeper understanding of the design requirements and the importance of API support is an underpinning of new systems or reworks going forward. Some of the restrictions will remain severe though given the continual load that is placed on our systems through the API, itemdb being the most constant example.

— Mod Boko 13 June 2014
I'll ask and attempt to invite you to join the meeting whenever it happens. Ryan PM 22:22, April 11, 2015 (UTC)

Site anniversaryEdit

Hi, Cqm!

We were wondering if there's anything you guys were planning to do to celebrate your upcoming 10-year anniversary? If so, we'd love to support whatever you might be doing, even if it's just spreading the word. In either case, congratulations!!!

Best regards,

Raylan13@Wikia (talk) 23:38, March 31, 2015 (UTC)

I wrote up a blog I'd love to post here, if that's permissible ;) We would also link to it from the main page of our Games Hub. Note that there's an anniversary wordmark I included it that you are more than welcome to use if you'd like for the anniversary. If you'd like, I can request we mention the in-game celebration via our social media accounts. Raylan13@Wikia (talk) 20:36, April 6, 2015 (UTC)
Sounds good - I posted the blog here and will pass along a request for social media mentions for this week. Let me know if there's anything else you might need us to do! And congrats again :) Raylan13@Wikia (talk) 21:34, April 6, 2015 (UTC)

How does adding items to exchange workEdit

Exchange:Fletch logs Exchange:Fletch & burn logs

Script error

Help please. --Jlun2 (talk) 03:31, April 9, 2015 (UTC)


I have two questions about this module:

  1. Why do the 'kills'/"Enemies to defeat" bulletpoints appear like instead of being an actual unordered list as generated by the wiki syntax? (E.g. at Plague's End).
  2. I don't think 'args.recommended' is working as intended. yesno(...) seems to return true only if the value is something like "Yes", as opposed to if the variable's value is actual/not-nil. But is this parameter actually really used anywhere? Iirc, generally recommended items are listed explicitly in the 'items' parameter anyhow.

Thanks, IP83.101.44.209 (talk) 09:56, April 12, 2015 (UTC)

Thanks for having taken a look and fixed it. The odd bulletpoints now seem to appear in the required items sections, though... Mountain Daughter. IP83.101.44.209 (talk) 03:50, April 13, 2015 (UTC)
One more, it seems the "recommended" parameter has the same issue, as seen on Heart of Stone; then again, not sure why we have this parameter if it's usually part of the "items" parameter. IP83.101.44.209 (talk) 12:46, May 2, 2015 (UTC)

GE smallchartsEdit

works in oasis, but not in monobook. thought u shud know.   az talk   13:23, April 19, 2015 (UTC)


'lo Cam, if you get the chance to send me on a link to the audio from the Jagex meeting it would be great. No worries if you're busy. Ronan Talk 17:33, May 1, 2015 (UTC)


Standard deviations should be better than percentages. I only used percentages as a quick solution and never really got around to updating it. Amaurice talk 01:01, May 4, 2015 (UTC)

Let me know when your script is ready to take over and I will stop AmauriceBot from processing the logs. Smile Amaurice talk 07:17, May 6, 2015 (UTC)

efficacy i mean efficiencyEdit

Since price and certain other commands of Module:Exchange are used fairly often, would it be more efficient to create a separate module consisting only of those functions for when other modules need prices? Or is the actual size of the module relatively negligent in calculating the lodestone load time? MolMan 13:10, May 4, 2015 (UTC)

GE price and roundingEdit

Any chance you could take a look at getting rounding to work properly? This is mostly relevant in cases where non-whole amounts are being used (the MMGs). IP83.101.44.209 (talk) 06:54, May 8, 2015 (UTC)

GECharts fixesEdit

Cross-posted to Joey

Dunno if you saw my irc tell before now, but I did manage to actually fix it. Here is the js in its glorious userscript form. The fixes are:

  • Properly support multiple charts with multiple items each (this is what I set out to fix, following a report in s:c; the other things were byproducts)
    • eg [1] - notice that while its supposed to be 3 charts, each with a main-hand drygore and its corresponding off-hand, its actually showing all three offhands on the first chart (the mace)
    • This was down to a combination of issues
      • The data was being added to chart id 0 only, not the relevant chart
      • The chart tracking was being stored in a window variable, so (with the async get request) it ended up being added to the last chart
      • The loadChartsQueueComplete method only reloaded one specific chart rather than them all, when loading was finished, and...
      • The loadChartsQueueComplete method didn't know which chart in the AIData/AIQueue array the item belongs to, so would add everything to the specified chart
        • Fixing this incurred a duplication - if the method is passed a number it (re)loads every chart, otherwise it loads just the chart with the id passed (always 'popup', as far as I can tell)
  • If you added an item to the popup then closed the popup, the item would not have a line on the chart but would persist in the background, prevent adding the same item again; this also applied to opening the popup for one chart, adding an item, closing the popup, then opening the popup for a different chart
    • I changed it to remove all items when the popup was hidden, since this was simplest - the other option is to properly keep track of it somehow, which would also involve making sure it worked with multiple charts on the same page like above
  • Fix averages
    • Can't really remember what was wrong with them, but I know at one point it jQuery's the wrong id (#GEpopupchart instead of the correct #GEchartpopup); between that and everything else it just started working
  • Added a lot of console.log, which can be removed now
    • They give a nicer link to click in Chrome dev console than mw.log

I dunno if you want me to just add it to the js or if you wanna check it over first (the diff is actually pretty good for once). Quest Gaz Lloyd AwesomeEvents!99s 01:02, May 10, 2015 (UTC)

Mobile style around Module:NavboxEdit

Hey there fellow neighbours!

An admin from Elite: Dangerous here. We've recently taken the work of Module:Navbox over to our site, amongst other Templates and Modules, and I'm wondering how MediaWiki:Wk-style-navbox and MediaWiki:Wk-style-divclose works. I cannot get it to work nor figure out how it works, it just displays as text before and after the navboxes. I've since the issues commented out the code within our Module:Navbox to take on at a later date.

We don't have many mobile users at all, mainly desktop and tablet, but I'm curious if you could help us with the hack to get the navboxes to look better on those who do use mobile. Cheers. - SpyTec (talk) 19:55, May 25, 2015 (UTC)

This issue had to do with Wk-style-navbox and Wk-style-divclose being created after Module:Navbox and as such verbatim didn't work due to caching. It's fixed now and I feel a bit silly. Thanks for the help The Mol Man! - SpyTec (talk) 20:30, May 25, 2015 (UTC)

Around Wikia's network

Random Wiki