User talk:The Mol Man


 * Rules
 * 1) If you neglect to make a new header when you post a new message, I will make one for you and it will be stupid; also, you will have no right to revert it
 * 2) If you post any ordinal, your message will become a subsection of the section "I'm a loser"

__NOWYSIWYG__

Re: Ur maxed?
Yes, albeit not 'true maxed'. I'll get that through dailies before the end of the year. As for the colours, just various shades of yellow. IP83.101.44.209 (talk) 04:22, August 26, 2014 (UTC)
 * For what purpose? IP83.101.44.209 (talk) 04:29, August 26, 2014 (UTC)
 * I'm afraid that doesn't make me want to bother. Besides, I can't get AA without freezing my client; and have no way to properly zoom in. Nor do I have an interest in being in a gallery somewhere. IP83.101.44.209 (talk) 04:40, August 26, 2014 (UTC)

MediaWiki:Geshi.css
I finally got around to sending in a bug ticket for it. It's easy to reproduce with the instructions I sent in, so it should be ticketed in the next couple of days and likely given a low priority so it can sit in the bug tracker for the next decade :)

CSS help
Hi Mol, I need some help with my wikis CSS. It seems not to be global, I mean check this link http://imgur.com/a9mWfcz Could you help me with this, thanks 08:49, September 1, 2014 (UTC)

Ring of Wealth
This. I've already made some corrections to row. 09:17, September 2, 2014 (UTC)

re:asjhasduqdbadcz
Interesting name, thanks for taking a picture of it :D 14:07, September 3, 2014 (UTC)

Killing K'ril
I noticed some issues with the numbers on the Money Making Guide/Killing K'ril Tsutsaroth page. The math simply doesn't add up. I summarised the issue on the talk page, but didn't edit the article sincle I rarely kill K'ril and so wouldn't have accurate data on the drops. I figured since you've got quite some experience, I'd ask you to have a look at it. Tomdiepstrap (talk) 02:51, September 11, 2014 (UTC)

????????????????????
??????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????? 22:23, September 11, 2014 (UTC)
 * I use template yo.  01:18, September 12, 2014 (UTC)

Yes, I know you can...
I just wondered if you would, and if you could be tempted to comment on it. Lighten up! :0) 22:18, September 14, 2014 (UTC)

Re:Hiker boots
>_> policy m8. i can trans and shit if you come to my poh -- 22:11, September 17, 2014 (UTC)

Re: Ads
Thanks, sent off another 5 abuselog entries for investigation.

Debilitate
I added more data on the talk page. I can't figure out how to add rows to the table, so enjoy. Tomdiepstrap (talk) 23:23, September 20, 2014 (UTC)

Ponies
As requested, analysis of Template:DropsLine/qty.

The pseudocode more aptly explains exactly how it works internally - and would be easier to work from to luaify - but the textual might help explain its concept, so have both and use as you will.

Textual
Quantity handles the display of the GEPrice of a drop, which depends quantity dropped. The quantity can be entered in a number of ways:
 * A single number: 5
 * A hyphen-separated range of numbers: 5-15
 * A comma-separated list of numbers: 5,9,15
 * A combination: 5,10,15-23,98,150-600 ...

All of these ways can be appended by (noted) (or anything else in brackets) safely. The template first splits the quantity string by opening bracket, and takes the first element in the resulting array and uses it for the rest of the parsing and calculating.

The template accounts for all variations. It assumes that the input list of numbers/ranges is in ascending order, and all numbers are unformatted (thousands are not separated by commas or spaces or such).

If we continue with this assumption, we can work out the maximum and minimum drop value, which is what is displayed in the column in the table. The template - along with its parent DropsLine - also assume that the item name provided is a valid item name, and makes no attempt to account for an error with it.


 * Single number
 * Applies to: Quantity=5

Obviously just Quantity*GEPrice. However, we make sure that Quantity is error-free first using an #iferror - if there is an error resulting from multiplying those together, just the GEPrice is displayed. This is repeated every time any form of quantity*price action occurs.


 * (Single) Hyphen range
 * Applies to: Quantity=5-15

If there is a hyphen present in the quantity input string - but no comma, so it is a single hyphen range - we split the string by hyphens and take the first and last values of the resulting array (again, the minimum and maximum values), then apply the error-checking Quantity*GEPrice to both, separating with  &ndash  (&ndash).


 * Comma list
 * Applies to: Quantity=5,57,100 or Quantity=5,7-10,23 (notice: first and last without hyphens)

If there is a comma present in the quantity string input, we take split the string by commas and take the first and last values in the resulting array - since the list was in ascending order we know these are the minimum and maximum values - and check for hyphens in each. If there aren't, we apply the error-checking Quantity*GEPrice to both, separating them with  &ndash .


 * Combination
 * Applies to: Quantity=5-10,57,100 or Quantity=5,7-10,23-30</tt> or Quantity=5-10,23-30</tt> etc (notice: first and/or last with hyphens)

Following from the previous section, if one or both of the values chosen from the commas array contain hyphens, we need additional checks:
 * If the first item in the commas array - the minimum element - has hyphens, we split the string by hyphens and take the first value of the resulting array; otherwise
 * If the last item in the commas array - the maximum element - has hyphens, we split the string by hyphens and take the last value of the resulting array

(If only one of them contains a hyphen, we just use the other value as a number as before.)

We then continue as usual with these two elements, using the error-checking Quantity*GEPrice and separating them with  &ndash </tt>.

In reality it doesn't matter what the other values in the quantity string are or their order, as long as the first value is the minimum and the last value the maximum. You could, if you wanted, parse it more thoroughly and ensure the list is always in ascending order when displayed, regardless of input, but I don't know if there's much value to be gained.

Pseudocode
For reference, here's the current wikicode indented more readably (though you'll need a wider window to not have wrapping):

And here's my interpretation in pseudocode, with comments (#</tt>):

PARAMS 1=quantity (default 1), 2=itemname (no default) DEFINE qty = first item of the array resulting by splitting param1 by '('	#remove (noted) etc IF ',' is not found in qty	#not a list	IF '-' is not found in qty		#single number		TRY			RETURN formatted (qty * (geprice of param2))		CATCHERR			RETURN formatted(geprice of param2)	ELSE		#single hyphen range		DEFINE qty1 = first item of the array resulting by splitting qty by '-'		DEFINE qty2 = last item of the array resulting by splitting qty by '-'		DEFINE ret = ""		TRY			ret += formatted (qty1 * (geprice of param2))		CATCHERR			ret += formatted(geprice of param2)		ret += '–'		TRY			ret += formatted (qty2 * (geprice of param2))		CATCHERR			ret += formatted(geprice of param2)		RETURN ret ELSE	#is a list, so get the min/max values	DEFINE qty1 = first item of the array resulting by splitting qty by ','	DEFINE qty2 = last item of the array resulting by splitting qty by ','	DEFINE ret = ""	IF '-' is not found in qty1 #min value is a number TRY ret += formatted (qty1 * (geprice of param2)) CATCHERR ret += formatted(geprice of param2) ELSE #min value is a range, use the min value of the range DEFINE qty11 = first item of the array resulting by splitting qty1 by '-' TRY ret += formatted (qty11 * (geprice of param2)) CATCHERR ret += formatted(geprice of param2) ret += '–' IF '-' is not found in qty2 #max value is a number TRY ret += formatted (qty2 * (geprice of param2)) CATCHERR ret += formatted(geprice of param2) ELSE #max value is a range, use the max value of the range DEFINE qty22 = last item of the array resulting by splitting qty2 by '-' TRY ret += formatted (qty22 * (geprice of param2)) CATCHERR ret += formatted(geprice of param2) RETURN ret

Love, 04:03, September 21, 2014 (UTC)

Titles Trivia
Perhaps using <span style="color:rgb(0,0,0);font-family:monospace;"> instead might be better? Considering the template page clearly stated that the TitleAnchor template must only be used on the Titles page anyway. Besides, I'm pretty sure it wouldn't hurt to add colours instead of clogging up the texts with too many unnecessary punctuations, confusing new trivia editors. 19:29, September 23, 2014 (UTC)


 * I still don't see why you disagree with this because I honestly think that titles should be coloured by default in the first place, as with RuneScape text all over the wiki but whatever. I'm not going to add the punctuations back. 19:48, September 23, 2014 (UTC)

re:dumb name
set a reminder on your phone saying "wish that random australian guy on the internet a happy birthday" 23:59, September 26, 2014 (UTC)
 * 00:21, September 27, 2014 (UTC)
 * look again 00:25, September 27, 2014 (UTC)

Well excuse me
For looking at the damn title of the wikia and thinking that we should represent it more -- 03:34, September 27, 2014 (UTC)
 * Frankly, I don't care how you spell it. And I think you may be UNDER-doing it. -- 03:38, September 27, 2014 (UTC)
 * Im really sorry about this. I'm not sure exactly what kind of cactus was up my arse, but I'm truly sorry. Please accept this cake as an apology. [[File:Cake.png]] -- 04:08, September 27, 2014 (UTC)
 * I prefer baskets. 12:29, September 27, 2014 (UTC)

Re:Bestiary
For the rat, it's a more interesting version. Since it's incredibly hard to orb it in the Barrows due to EoC and stuff (I'd have to bring a friend, but it's still hard due to other aggressive monsters), I used the bestiary. As for the skeleton, its foot in the original image (which was fine otherwise) was clipping. Normally I'd not use the bestiary, but now that they removed the horrible lighting and added the whitescreen, it's fine. 07:11, September 27, 2014 (UTC)