User talk:Rye Greenwood

Thank you
Thank you for all you have done with translating the Official Terraria Wiki into the German language. I would like to invite you to the Official Terraria Wiki Discord and Official Gamepedia Slack. Discord is where we discuss all things about the Official Terraria Wikis and Slack is where Gamepedia Staff and Wiki Administrators/Editors talk and receive help with Wikis. – ReedemtheD3ad!  ( talk ) 17:43, 16 July 2018 (UTC)

Out of curiosity...
I just wanted to know why people keep removing this documentation change whenever it’s put onto the page. Thanks for your time, mate! 38.88.10.26 00:42, 21 November 2018 (UTC)


 * The template now handles desktop content. will categorize the item for desktop, console, mobile, and 3DS.
 * will categorize the item for console; 'mobile' for mobile, '3DS' for 3DS. There is no need to add a desktop parameter. – Ferretwings (talk )


 * Oh, my bad, it seems that y’all already removed the DSK param, thanks for the quick response friend! 38.88.10.26 01:08, 21 November 2018 (UTC)

Incorrect timestamp
On my PC it says that Rye Greenwood commented on my profile at 00:00, 6 March 2019 when it is March 5 in my area. Is there a glitch when it says 6 March and in my area it is March 5.


 * The timestamp was in UTC. See your preferences for a comparison between UTC and your own timezone. – Ferretwings (talk ) 01:24, 6 March 2019 (UTC)

Tall gate suggestion
(I think this is the right place...) Hey Rye, did you test out my gate suggestion?


 * Yes, I did. It does seem to work. Thank you for the suggestion! --Rye Greenwood (talk) 13:02, 7 May 2019 (UTC)

Template:Iteminfo on Guide:Making money
[continuing this here because I am not sure whether templates work correctly in profile comments and I prefer being able to preview my wikitext]

Template:Iteminfo has two different output styles: formatted and more readable data or raw data, literally like it exists in the source code. For example,  outputs the following:  – formatted and "wiki-fied". , on the other hand, outputs the raw source code data: (the internal, numerical rarity value). For certain stats, there are aliases to make the usage slightly more intuitive; hence, for instance, is valid as well:. These, however, do not work when using the raw mode:  results in  (nothing).

As per the source code, the item statistic value represents the purchase price. Since this is rather counter-intuitive (usually, a thing's "value" refers to the amount of money received in return for that thing), the template treats "value" as input differently: Using  returns the sales value:. Note that the raw mode is not used here! The raw mode,, outputs something different:  – the purchase price (because the raw mode is intended to accurately represent the source code).

There is no sales value statistic in the source code, which is due to the simple fact that it is always equal to 1/5 of the purchase price. Therefore, the template is bound to take the value stat from the source code and divide it by 5, if e.g.  is called. That is also the reason why there is no "original raw variable" for the sales value in the template's documentation table.

Typing all this out, I understand why it might cause confusion. The best solution would probably be to get rid of value as an alias and stick to the unambiguous sell as the only valid input for the sales value. I will go ahead and mark the alias value as deprecated.

Regarding the second point you brought up: Whenever I want to apply any calculations to any stat of an item, I need to get its raw, numerical value. That is because the parser function  can only handle numerical values. For example, the HTML (which is what is interpreted by ) of   is actually , which is definitely far from a raw, numerical value and thus does not work. Therefore, I have to 1) take the raw purchase price (because it is impossible to get the raw sales value, as I described above), 2) apply the logic for turning it into the sales value (which simply consists of dividing it by 5), 3) do the initial calculation I wanted to do, and 4) wrap it all in the  template.


 * 1) Take the raw purchase price:   →
 * 2) Turn it into sales value, dividing it by 5:   →
 * 3) Do my calculation (multiplying it by 999 here):   →  (although the brackets are not mandatory, they help provide a minimum of structure to the code)
 * 4) Format it into a nice and standardized output:   →

If this explanation still leaves questions, please do not hesitate to ask them.

--Rye Greenwood (talk) 22:34, 8 August 2019 (UTC)


 * Thank you. Sometimes I forget what a hodgepodge of layers wiki software is.... :-/  I'm going to extend the rounding to a number of other things, in particular limiting the larger values to gold. Basically, when tossing around averages and likely yields as this page does, more than two or three digits of precision is basically wishful thinking.  --MentalMouse42 (talk) 09:41, 9 August 2019 (UTC)