User talk:Cqm

Infobox item
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 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, 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, and it would spit out like Equipped: -1 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. 13:19, February 21, 2015 (UTC)

2015 RSW Family Photo
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, 16:24, February 22, 2015 (UTC)

stuff

 * frame:getTitle <3 (I have DPL plans with this, please tell me when you get this ticket done; no real rush though)
 * [[File:Coins 10000.png]] 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

16:19, March 6, 2015 (UTC)

RE: Hiscorecount
I just went to the Hiscores page and looked for the last maxed person. 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 >.< 02:27, March 21, 2015 (UTC)

JS code review
Hey,

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, 02:46, March 21, 2015 (UTC)
 * I took the close hover icon from [[File:Invalid cursor.png]], 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! 21:59, March 22, 2015 (UTC)

JS Calculators CSS
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
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? - 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. -  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. - 05:50, May 23, 2015 (UTC)

Jagex Meeting
Hi,

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.

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, 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. 21:30, April 11, 2015 (UTC)
 * Okay, might have made a slight mistake, here is the quote from Fansite Staff:


 * I'll ask and attempt to invite you to join the meeting whenever it happens. 22:22, April 11, 2015 (UTC)

Site anniversary
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 ( 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 ( 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 ( talk ) 21:34, April 6, 2015 (UTC)

How does adding items to exchange work
Exchange:Fletch logs Exchange:Fletch & burn logs

http://services.runescape.com/m=itemdb_rs/Fletch_logs/viewitem.ws?obj=34529

http://services.runescape.com/m=itemdb_rs/Fletch_&_burn_logs/viewitem.ws?obj=34531

Script error

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

Module:QuestDetails
I have two questions about this module: Thanks, IP83.101.44.209 (talk) 09:56, April 12, 2015 (UTC)
 * 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 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 smallcharts
http://runescape.wikia.com/index.php?title=Talk%3AGrand_Exchange_Market_Watch&diff=13356728&oldid=12491637


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

Skype
'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. 17:33, May 1, 2015 (UTC)

RE:Charms
Standard deviations should be better than percentages. I only used percentages as a quick solution and never really got around to updating it. 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.  07:17, May 6, 2015 (UTC)

efficacy i mean efficiency
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? 13:10, May 4, 2015 (UTC)

GE price and rounding
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 fixes

 * 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 - 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). 01:02, May 10, 2015 (UTC)

Mobile style around Module:Navbox
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)

butts
I'd probably do rollback/custodian+ simply because of who I can see actually using the script.

As with anything, if you want to prevent editing those fields, leave room for users with certain rights to edit them. Just as an example reason, I would find it easier to manually update a set of pages that were all listed as 0 in the API. Rather than having to use the script each time and wait for it to fail to prompt me for a price. 11:49, May 28, 2015 (UTC)

Charm log problem
This edit somehow got allowed, it didn't get pwned by RuneScape:Counter-Vandalism Unit/Charms. [ VSTF ] 01:35, June 1, 2015 (UTC)

RE: icon and item parameters
just checked: there are plenty of items (about 450+ items) which have different "icon" values compared to than their item name. these include arrows/bolts/seeds/etc (for which we already have redirects) and also construction flatpacks ( 207 82 items).

see Grand Exchange Market Watch/Construction flatpacks. the icons are messed up in this page btw.

fyi, flatpack items (example: Module:Exchange/Gilded cape rack) has 2 icons, one from the GE (File:Gilded cape rack flatpack.png ) and one from the construction interface (File:Gilded cape rack.png ). if you removed the icon parameter for these flatpack items, they would show the interface icons... this I don't mind actually since they're nicer, but we would lose the need for the GE icons.

so, maybe we can keep it optional and not use the "icon" parameter only if they're the same? like the "alchable" parameter. 05:06, June 5, 2015 (UTC)


 * please, no... and we already have a naming convention for construction, see RS:IMG.
 * flatpack suffix: for flatpack icons.
 * built suffix: for large images for built construction items.
 * no suffix: all construction icons.
 * it makes no sense to rename it specifically like you mentioned... firstly, there are more construction items without flatpack icons compared to those with. only 82 flatpacks compared to about all construction items, with may exceed 1000 items. secondly, the flatpack icons are pointless to be used other than in the GE/GEMW pages (since they look almost the same for all items). the normal icons are (and should be) used more extensively in pages/infoboxes/navboxes/etc.
 * so, please, please, please... keep the icon parameter, if only for the 82 flatpack items. and fix the templates to use the icon parameter if required.
 * or, another idea would be to check the "category" parameter. all flatpack items have the same category value called "Construction products". so maybe check the category, and add the "flatpack" suffix?
 * 23:35, June 5, 2015 (UTC)


 * i think i was the one who came up with those naming conventions... and did alot of work renaming those filenames, moving the images, and fixing the links. now you just reversed all the changes i made? (i abandoned this project halfway when it became too much work! i did about 5 rooms i think). Category:Construction_icons has 400+ icons. as you had observed, nobody actually worked on it since September 2013.
 * the change you did in Parlour and in Template:Parlour, that is not the correct icon? the correct icon should be the interface icon not the flatpack icon (flatpack icons are only visible in GE and when you actually make a flatpack for that furniture). the interface icons are more recognisable and easier to identify compared to the GE icons, so it makes no sense in those particular instances.
 * built icons are in Category:Construction built images.
 * please, stop! what you are doing is not beneficial to the wiki... and we can make an exception for these flatpacks.
 * the flatpack icons doesn't really benefit us! it is only used in the Flatpack article, and in the Exchange/Calculator pages. sure, we shud use the flatpack icons in those pages, but what's the point of having flatpack icons which look almost the same in navboxes and in articles? come on, make an exception for flatpacks, please!
 * 08:23, June 7, 2015 (UTC)


 * the full list is here: http://runescape.wikia.com/wiki/RuneScape:Sandbox?oldid=13783614
 * 08:37, June 7, 2015 (UTC)


 * yeah, probably saw a cached version...
 * basically, i want consistency for all construction icons... so that all items have the same naming convention. now with the name change, we will have two types: (a) tradeable items with "icon" suffix for the interface icons and no suffix for the GE icons, and (b) non-tradeable items with no suffix for the interface icons. earlier we only had one type: no suffix for the interface icons, and "flatpack" suffix for the GE icons.
 * and yeah, i get it that you want consistency for GEIcon.
 * what im saying now is that we just ignore the flatpack icons altogether. we will only use it in the Flatpack article, and in individual articles, but not for GEIcon or for Module/Exchange pages. that way we can: (a) provide readers with the more useful icon compared to the boring flatpack icon. (b) keep the naming convention for all construction icons, tradeable or not. (c) not complicate the plink-ing thingy...
 * i know inventory icons use the item name in almost every case. but i think we can make an exception for flatpacks... i wouldn't be making a big fuss over this if the flatpack icons are pretty and distinguishable from each other, but the fact is the flatpack icons are terrible and not helpful at all.
 * and i don't think we need a forum for this, nobody really cares. but if we can reach some sort of understanding/compromise, it would be great. 13:10, June 8, 2015 (UTC)


 * i don't think you get what i'm suggesting... i'm saying we use the interface icons for GEIcon. no suffix. ignore the flatpack icons. we don't fix anything, and we don't have to change anything. we will be using non-inventory images for these 80+ exchange items. get it? 11:44, June 9, 2015 (UTC)

Dragon platelegs/skirt ornament kit (or), Dragon platelegs/skirt ornament kit (sp)
i've updated AzBot to handle "/" in item names, previously it couldn't... so thanks for letting me know :)


 * < Module:Exchange | Dragon platelegs | skirt ornament kit (or)

could you do something about the redirects in the header? that was one of the reasons why we didn't use the "/" in item names. trivial, i know. but pretty please? 05:25, June 5, 2015 (UTC)

Unlucky
Hey. Sorry to bother you with this, but your username is short. :P Anyway, this happened (AGAIN) and I'm not going to explain to him how 3RR works at this point. 07:58, June 9, 2015 (UTC)
 * Well, that, and what was in the edit summary, i.e. that it's not even true in the first place. A postbag confirms Zanik has no feelings for the player, and real sources override JMod comments, naturally. 08:53, June 9, 2015 (UTC)
 * It was Mod Raven who said it, not John A though. And it wasn't that old. :P But either way, it was yet another breach of 3RR and he's been blocked for that already. 09:34, June 9, 2015 (UTC)

Zanik
Why not? 09:24, June 9, 2015 (UTC)