User talk:Rye Greenwood

Thank you

You Get A Star
Thanks for all your hard work!

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. {{equivcat| all | introduce/patch | ...}} will categorize the item for desktop, console, mobile, and 3DS.

{{equivcat| console | introduce/patch | ...}} 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. — Preceding unsigned comment added by Lepspring (talk • contribs) at 00:49, 6 March, 2019‎ (UTC)

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? — Preceding unsigned comment added by Patriotgrimm (talk • contribs) at 00:32, 7 May 2019‎ (UTC)

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, {{iteminfo|Dynasty Wood|rare}} outputs the following: 00* – formatted and "wiki-fied". {{iteminfo|Crystal Shard|rare|raw=yes}}, on the other hand, outputs the raw source code data: 0 (the internal, numerical rarity value). For certain stats, there are aliases to make the usage slightly more intuitive; hence {{iteminfo|Dynasty Wood|rarity}}, for instance, is valid as well: 00*. These, however, do not work when using the raw mode: {{iteminfo|Dynasty Wood|rarity|raw=yes}} results in 0 (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 {{iteminfo|Dynasty Wood|value}} returns the sales value: 10 CC. Note that the raw mode is not used here! The raw mode, {{coin|{{iteminfo|Dynasty Wood|value|raw=yes}}}}, outputs something different: 50 CC – 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. {{iteminfo|Dynasty Wood|buy}} 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 {{#expr:}} can only handle numerical values. For example, the HTML (which is what is interpreted by {{#expr:}}) of {{iteminfo|Dynasty Wood|sell}} (10 CC) is actually <span class="coins" data-info="10" title="10 Copper Coins"><s>10*</s>10 <img alt="Copper Coin.png" src="https://gamepedia.cursecdn.com/terraria_gamepedia/4/43/Copper_Coin.png?version=c51d2521b2f3a63b12ec63776baa3aeb" width="12" height="12"></span>, 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 {{coin}} template.

Take the raw purchase price: {{iteminfo|Dynasty Wood|value|raw=yes}} → 50
Turn it into sales value, dividing it by 5: {{#expr:{{iteminfo|Dynasty Wood|value|raw=yes}}/5}} → 10
Do my calculation (multiplying it by 999 here): {{#expr:({{iteminfo|Dynasty Wood|value|raw=yes}}/5)*999}} → 9990 (although the brackets are not mandatory, they help provide a minimum of structure to the code)
Format it into a nice and standardized output: {{coin|{{#expr:({{iteminfo|Dynasty Wood|value|raw=yes}}/5)*999}}}} → 99 SC90 CC

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)

In case anybody comes across this, there is now an easier way to handle expressions with sales values: see {{sell expr}}. --Rye Greenwood (talk) 00:40, 3 December 2019 (UTC)

This reversion... why? Do you have something against balanced parentheses?

Looking at this reversion ; I have no idea what else Jayflow222 might have been up to, but in this case it looks to me like he just inserted a correct open-paren to the clause. Was there some other reason to revert it? --MentalMouse42 (talk) 19:25, 11 August 2019 (UTC)

No, I must have missed the second parenthesis there. --Rye Greenwood (talk) 21:03, 11 August 2019 (UTC)

Looks like someone else took it the other way while I was checking with you. Whatever. --MentalMouse42 (talk) 23:29, 11 August 2019 (UTC)

Protected pages

Hi, Rye! I was trying to add the fr interwiki links to a few pages here on the English wiki, and I noticed that several of them are protected. At the moment, I was planning to add links to the pages that contain NPC names (Angler/Names, etc.), but I suppose there might be other pages as well that are open on one wiki but protected on another. Seeing as I do a lot of back and forth work here, I was hoping to establish a more consistent connection between the two wikis. Could you please let me know if there is any way that I might add these links where appropriate? Thank you very much! PuzzledKino (talk) 16:18, 28 October 2019 (UTC)

Hey! Thank you for your continued commitment to adding and correcting the interwiki links, that is appreciated. Unfortunately, there is no direct way for anybody without at least Administrator user rights to edit a protected page whatsoever – including interwiki links. The usual process in this case is to request addition or modification of an interwiki link of a protected page on the respective talk page. An administrator can then perform the edit. Of course, that would be only be practical if you only wanted to add/modify one interwiki link at a time. With a longer list, that would get too tedious, so in that case it is best to hand an administrator the list and ask them to edit all of the pages in one go. If you don't want to ask any person in particular (here is the list of administrators), feel free to head to the admin noticeboard (the response might be faster there, too).

I can't think of an easier way of doing this, unfortunately – I think I remember it's what I would be doing with de interwiki links, too, when I wasn't an admin here yet.

I hope this didn't scare you off of continuing to fix and add interwiki links; I can only repeat that that work is appreciated! Interwiki links are crucial for the visibility of the language wikis, so thanks again!

--Rye Greenwood (talk) 22:02, 28 October 2019 (UTC)

Thanks for your quick reply! While it's a bit of a shame since I'd be more than happy to do it myself, I do understand the reasoning behind this decision.

I'm glad my work here is appreciated! I'll continue to help however I can. Thanks again for helping me (so quickly and kindly, too!) PuzzledKino (talk) 23:19, 28 October 2019 (UTC)

Page to be deleted

Hi Rye! Could you perhaps do me a small favor? There is another Portuguese Terraria page that doesn't really serve any purpose. I forgot I'd listed it for deletion a week or two ago. The one line there basically says "it's a good sword, you're gonna want this." Could you delete that page please? Thank you! PuzzledKino (talk) 01:12, 23 November 2019 (UTC)

Sure, thanks for letting me know! --Rye Greenwood (talk) 01:18, 23 November 2019 (UTC)

Abbreviation "ce"...?

In your revision notes you often use the abbreviation "ce" -- what does that actually stand for? I haven't been able to figure it out by context. --MentalMouse42 (talk) 00:14, 3 December 2019 (UTC)

It stands for "copy edit" and refers to a general, mostly behind-the-scenes cleanup, i.e. mainly wikicode formatting and standardization/beautification. I think I have picked it up from User:Equazcion's user page, although by now I probably use it differently than he does – I usually (try to) add something like "minor reword" or "grammar" if I actually change article text. --Rye Greenwood (talk) 00:30, 3 December 2019 (UTC)

That makes sense, thanks. --MentalMouse42 (talk) 17:17, 3 December 2019 (UTC)

Your activity and mine on this Wiki.

I have been well active on Terraria Wiki, enough to have a free PRO subscription at this day of writing because I’m excited thar Journey’s End will be bigger than 1.3. The majority of my contribs consisted of uploading old item sprites and 1.4 spoiler images, adding spoilers on and tweaking the Upcoming features page.

I wonder what will you do once Journey’s End comes out? ReedemtheD3ad replied to me that the PRO user will prioritize updating sprites. And me, well, I may spend more time playing terraria since a long time and avoid too many spoilers on this wiki. --Superwill771 (talk) 00:05, 6 May 2020 (UTC)

Thanks for your commitment to contributing! I'll probably focus on backend work, like updating the databases and making sure the new content can be integrated seamlessly, but of course there'll be a lot to do in all departments. --Rye Greenwood (talk) 00:44, 6 May 2020 (UTC)

Fishing catches move

You have a bot, can you replace the links on fish pages to Fishing Catches with Fishing catches with it? Sorry if I'm misunderstanding what you can do with it. --172.58.158.160 17:36, 6 May 2020 (UTC)

Sure, that exactly is a standard use case for bots. It's running right now. Good work splitting off all those pages, by the way! --Rye Greenwood (talk) 18:02, 6 May 2020 (UTC)

An edit to Bosses

Somebody made an edit to Bosses claiming that "The Moon Lord's legs may be a boss in 1.4", despite the Upcoming Features page disproving it. Could you undo it? I'm sorry to bother you, but you seem to be online and I can't edit the page as it's protected. --172.58.4.30 23:17, 7 May 2020 (UTC)

Sure, that's no bother! Thanks for notifying. --Rye Greenwood (talk) 23:21, 7 May 2020 (UTC)

Template:Boss music

You've created a new template to automatically display the music that plays duing a boss battle. I'd like to change what it displays from "While $name$ is alive, music $music$ will play." to "While $name$ is alive, the music $music$ will play." Is that alright? --172.58.7.127 16:07, 10 May 2020 (UTC)

Of course, go ahead – although I appreciate your civility, you don't need to ask for permission for that. English is not my mother tongue, so my formulations often don't sound that natural. --Rye Greenwood (talk) 16:15, 10 May 2020 (UTC)

Weapon type templates problem

Hey, would you mind checking the French Sword page? I tried to import the recent templates you created thinking they would be l18n-ready, but it seems there is a problem. --Dinoxel ^talk 04:15, 18 July 2020 (UTC)

I did not think of the different implementations of {{pagename2en}} on the different wikis; that template is what caused the error. It should be fixed on FR now. If there's still something wrong, see if the page name has an entry in {{pagename2en}}'s database (Fr2e/db) first and if its translation is a valid name, as defined in the {{#switch:}} statement in the template code. Thanks for noting! --Rye Greenwood (talk) 13:17, 18 July 2020 (UTC)

Great! Thanks for the info and help! --Dinoxel ^talk 16:27, 18 July 2020 (UTC)

Careful with the heavily-used templates

Hey there, I'm reaching out to you because ReedemtheD3ad isn't currently online. The development team is currently working on the back-end of the login system to unite Gamepedia and Fandom, and for that they would need every wiki to slow down edits made to heavily used and transcluded templates/modules for the time being. Once this will be done (you can tell by the sitenotice getting removed), you will be fine to continue activities as usual.

Apologies for the inconvenience, I hope you understand, keep being awesome and have a great day! :) MannedTooth (talk) 16:52, 22 July 2020 (UTC)

Setinfo returns a wrong value + Rare sorting on FR doesn't work

Hey, {{setinfo|Princess set (Clothier)|buy}} doesn't return the proper value and I can't figure out why.

Also, I think I might have missed something while updating FR about the fix for the rare sorting on FR because the rare column doesn't sort anymore. (i.e. fr:Yoyos) --Dinoxel ^talk 21:10, 25 July 2020 (UTC)

Thanks for letting me know! The setinfo bug was caused by the two Princess Dresses sharing a name: Because the template works with item names internally, it calls {{iteminfo|Princess Dress|buy}} for both Princess sets, which gives an incorrect result for the Clothier's Princess set, of course. I have hard-coded a fix into the template now that catches this specific case and calls {{iteminfo}} with the item ID of the Clothier's Princess Dress. As for {{rare}} on FR, no, you did everything correctly there. The problem is that since the Yoyos table (and any other page fetching rarity data) takes its information from Cargo, it does not retrieve the most recent version of the items' rarity field. All item pages need to be null-edited (what would Cargo be without the joy of null-editing...) for the changed {{rare}} functionality to be transferred to the Cargo database, and then the sorting will work correctly. (Also, it seems just purging doesn't work in this case, it needs to be a null-edit; but I have no idea why. Anyways, I'm running my bot to null-edit all item pages.) --Rye Greenwood (talk) 02:00, 27 July 2020 (UTC)

Thanks a lot! --Dinoxel ^talk 13:44, 28 July 2020 (UTC)

Intitle and Look from

Hi, we had a short discussion on the Discord server about the templates, a few hours before you created them, and I made a template idea on User:Dig494/Sandbox2. Notably, the dpl should include redirects, for items that don't have their own pages (e.g. Wings, variants of entities, etc), a smaller design to fit in pages more cleanly, and just a plain vertical list since it's easier to read and doesn't take much space as a collapsed anyways. What do you think? — Dig494 15:53, 27 July 2020 (UTC)

Sure, feel free to go ahead and modify {{intitle}} and {{look from}}. I was just playing around a little to see what is feasible, since the templates aren't used anywhere yet. --Rye Greenwood (talk) 23:37, 29 July 2020 (UTC)

French problems

Bestiary tweak

Hey, would it be possible to add a parameter for |article = de l' that removes the extra space after the apostrophe? I tried to understand your code but it's way too complex for me at the moment --Dinoxel ^talk 17:25, 29 July 2020 (UTC)

I've added a small part in the l10n that checks if the last character of the article parameter ({{#sub:$article$|-1}}) is an apostrophe, and if yes, it won't print a space after the article. I figured this would be more convenient than an extra parameter. Sorry to hear you're having problems understanding the code! Let me know if there's anything I can do to help. --Rye Greenwood (talk) 23:33, 29 July 2020 (UTC)

Awesome, thank you! The little piece of code I've made for Bestiary changed so fast I couldn't assimilate everything properly, heh. I'll take a better look at StringFunctions next time. I was trying to understand where the space was created after on {{Bestiary}} but I just caught that the template was working by mixing itself and its l10n subpage. --Dinoxel ^talk 01:17, 30 July 2020 (UTC)

Potionlength problem

While I'm there, I came accross a really weird problem with fr:template:Potionlength. It no longer display anything unless /long is removed at a precise point. I've been updating as much templates as I thought were related near or far, purging, and null-editing but nothing happened. Also, I've uploaded the actual DE version (older EN version) to test and it worked just fine. --Dinoxel ^talk 01:17, 30 July 2020 (UTC)

{{l10n/long}} wasn't working at all; it would've never displayed a single thing (hence why the DE version would work – it doesn't use {{l10n/long}} yet). The reason is that even though you did synchronize it with the EN version recently, {{l10n/register}} on FR was still using an older version. That doesn't always necessary cause such critical errors, but in this case Westgrass had implemented a serious autoload optimization and the two versions didn't match at all. I'm guessing you didn't notice this because {{l10n/long}} is barely used (I probably wouldn't have noticed, either), but well, a simple sync of {{l10n/register}} fixed the problem. (Also synced {{l10n}} so as to not introduce more errors.) --Rye Greenwood (talk) 02:11, 30 July 2020 (UTC)

Argh, I missed one. Thanks again Rye. --Dinoxel ^talk 12:59, 30 July 2020 (UTC)

Data template

I've been updating {{data template}} recently on FR and noticed it would display the word English following by its translation into parentheses for $tr_lang$, wouldn't it be better to do the opposite or to remove the text in parentheses? See this example.

Also, unlike English, language names are lowercase in French. I did this change on FR data template and it seems to fix it, but it doesn't work when English is displayed (like there). Do you have anything to suggest? --Dinoxel ^talk 00:30, 31 July 2020 (UTC)

Do you remember when I suggested you to add {{tr}} to the {{#invoke:}} inside {{langInfo}} some time ago? Yeah, that caused this issue – sorry. I wasn't aware that the {{tr}} database already had an entry for "English", "English (Anglais)": that one comes from the source code (it's used in the language selection menu on the title screen).

Your fix is good, it works well! I've created an FR version of Module:LangInfo/data now, though, so the template now fully supports any possible language input and shouldn't require any local fixes. --Rye Greenwood (talk) 17:02, 31 July 2020 (UTC)

Great, thanks again ! ;) --Dinoxel ^talk 20:37, 31 July 2020 (UTC)

Percent template

Hey, I recently updated {{percent}} on FR and noticed Westgrass' edits (and yours) broke some stuff on fr:Cœur carmin. If the FR dec param is set to , (which is the correct value in French) it tries to search for images with <name>,png instead of <name>.png. --Dinoxel ^talk 00:33, 23 September 2020 (UTC)

Hm, looks like I didn't test thoroughly enough. That should be fixed now; thanks for notifying me. --Rye Greenwood (talk) 01:10, 23 September 2020 (UTC)

Drop infobox displaying strategies infoboxes

Hey, The Destroyer and The Twins infoboxes display twice on their French soul pages. Both these pages don't have the full name of the boss on their titles and are using {{transclude infobox|selection=y}}. I tried some things on the string I think is the cause but in vain. Any magic trick in mind? --Dinoxel (talk) 06:03, 19 October 2020 (UTC)

You looked in the right place already. I've made the fix, from when you mentioned the same problem here on EN some time ago, properly i18n-ready now, though. For FR, I set it to {{#ifeq:{{NAMESPACE}}|Guide|{{#ifeq:{{#sub:{{PAGENAME}}|0|10}}|Stratégies|y}}}}, which returns "y" for any page that is in the Guide namespace and whose title's first ten characters equal "Stratégies" (feel free to modify, of course). I've already synced the fix to FR, and I think it works correctly now. --Rye Greenwood (talk) 13:50, 19 October 2020 (UTC)

Yeah, I remembered that you fixed that but couldn't figure anything out because it was late. Thanks for the fix, and yeah it's better to have it on l10n. --Dinoxel (talk) 02:27, 20 October 2020 (UTC)

Tree Globe/tree styles

Hey, I imported your display of tree styles on FR and it displays nothing. I'm not really sure what to edit nor what would cause that error since the l10n part only concerns titles. --Dinoxel (talk) 09:29, 27 October 2020 (UTC)

Ah, I didn't consider the usage on language wikis properly, sorry. The problem was that it uses {{ifexists|File:<file name>}}, which queries the file name via DPL. This works on EN of course, but not on language wikis as these use the shared media repository. The way to check on a language wiki whether a file exists on EN is via {{#ifexist:Media:<file name>}}. --Rye Greenwood (talk) 12:33, 27 October 2020 (UTC)

French Extra Jump page + jump reach aditions

Hey, for whatever reason, it seems that items in the Accessories section on the French Extra jump page don't display at all although everything seems up to date. Any clue?

Also, I noticed that using |raw=y doesn't modify the comma. --Dinoxel (talk) 02:13, 11 February 2021 (UTC)

I made a silly mistake in {{equipinfo/list}}... The template used the {{formatnum:}} magic word to convert the item ID from an integer (as it is stored in cargo, including the comma as the thousands separator) to a string (as it is required by {{itemNameFromId}} and the like, without any thousands separator), but since {{formatnum:}} is language-dependent, that failed on FR. The SQL function CONCAT() is a much more appropriate and failproof way to deal with this conversion. Fixed that now, thanks for noting.

Using |raw=y in {{jump reach}} just ensures that it can be used properly in {{#expr:}} expressions, but the output of those expressions will be unformatted (i.e. with the dot as the decimal separator). I added a {{formatnum:}} to those expressions to apply proper French number formatting. (Also, for the percentages, I changed them to use {{percent}}, which automatically applies the correct formatting.) --Rye Greenwood (talk) 15:14, 11 February 2021 (UTC)

Thank you very much for your clear explanation and your quick responsivity! --Dinoxel (talk) 17:32, 11 February 2021 (UTC)

Drop infobox never displays the purse file

Hey, I noticed on the French wiki that the little bag file for items from Crates/Treasure Bags never display. The "isfromnpc" column on the Drops cargo table seems to have only "Yes" parameters as opposed to the English one which has both Yes and No, so I've tried digging into this in {{Loot}} but my few attempts failed so I'm once again asking for your knowledge. --Dinoxel (talk) 13:17, 3 March 2021 (UTC)

Oh, that's actually a very small fix; the Loot/row subtemplate contains the cargo storage for each row of {{loot}}. We can simply set isfromnpc to false there, because obviously {{loot}} is only used for items – just like we can set all three modes to true, because item drops are always the same in all modes. As always, a null-edit will probably be needed on each page that transcludes {{loot}} in order to put the change into effect.

Side note: A few items do already work correctly, all of which are Treasure Bag drops. You can see this with bosses for which you've already switched to the :loot: format in their {{npc infobox}}, e.g. Dévoreur des mondes. Check the {{drop infobox}} on any of its drops' pages, e.g. Écaille de l'ombre, and the bag image should be displayed along with the skull image.

--Rye Greenwood (talk) 14:13, 3 March 2021 (UTC)

Wonderful! Seems like I forgot another subtemplate existed. From what I've checked already, everything's working just fine now, thanks again! --Dinoxel (talk) 03:31, 4 March 2021 (UTC)

French Immunity accessories page exceeds template include size

Hey, it seems that the French Immunity accessories page doesn't display as it exceeds template include size. I tried creating a static page, but the same occurs. Any idea? --Dinoxel (talk) 12:17, 11 March 2021 (UTC)

Yeah, {{equipinfo}} does quickly reach that limit... That's why there's a version that uses Lua, {{equipinfo/lua}}, which is useful when the template is used a lot of times on one page. Accessories/typerow, for instance, uses that. I switched it on Accessoires d'immunité, and it should be good now. (Also, the item sources of many accessories weren't displayed because {{itemsource}} was attempting to use the French item names for the Cargo query. Fixed that by adding |lang=en to the {{itemNameFromId}} call in there.) --Rye Greenwood (talk) 13:08, 11 March 2021 (UTC)

Great, got it!

While I'm there I also found out that sources of sold-only items such as the Mechanical Ruler or Stopwatch on fr:Accessoires d'information don't display correctly. --Dinoxel (talk) 13:24, 11 March 2021 (UTC)

These can be fixed easily by adjusting their {{item infobox}} tags; see my edits on Détecteur d'organismes vivants and Règle. Those tags are important for the loot/drop, buy, and plunder parts of {{itemsource}} – you might have noticed that the source of the Hand Warmer on Accessoires d'immunité only displayed properly once you added the bag loot tag to the {{item infobox}} on Chauffe-main. --Rye Greenwood (talk) 11:28, 12 March 2021 (UTC)

Fishing poles page

Hey, I've been updating the French Fishing Pole page with your recent edits and none of the drop/loot sources display. I'm kind of confused as the appropriate tags are both declared and used on the same page about where to dig. I've recreated the Drops cargo already and noticed the Fiberglass Fishing Pole source doesn't display either on EN. I'm never sure if you're done already with the page, therefore I don't want to pressure you about anything. --Dinoxel (talk) 12:27, 24 March 2021 (UTC)

Yeah, I was pretty much finished with that page. I somehow overlooked the Fiberglass Fishing Pole, but all it was missing were the loot and bag loot tags, and it should be displayed correctly now. As for FR, try {{itemsource}} again. The problem was that the data was stored to the cargo table twice, on Cannes à pêche and on Pêcher, due to the transclusion on Pêcher. While that isn't a problem in itself, it does introduce caching errors: If you change the tags or some other infobox data on Cannes à pêche and do not null-edit Pêcher, then there are two rows in the cargo table which are about the same item but have different tag data (or whatever it is that you changed). It would look like this:

Cargo table before edit (excerpt)
_pageName	name	tag
Cannes à pêche	Scarab Fishing Rod	fishing poles
Pêcher	Scarab Fishing Rod	fishing poles

Cargo table after edit
_pageName	name	tag
Cannes à pêche	Scarab Fishing Rod	fishing poles bag loot
Pêcher	Scarab Fishing Rod	fishing poles

As you can see, there are two rows for the Scarab Fishing Rod that have different tags. Since {{itemsource}} retrieves exactly one row from the cargo table, it might get the row that is stored on Pêcher – the one with the cached, outdated data, so it would not see the changed tag. Hence, it is best to prevent duplicate cargo storage with those |cargo=<includeonly>n</includeonly> parameters. Now to put that into effect and remove the Pêcher row from the cargo table, another null-edit on Pêcher was required. The cargo table now looks like this:

_pageName	name	tag
Cannes à pêche	Scarab Fishing Rod	fishing poles bag loot

And this is exactly what we want, as it causes {{itemsource}} to behave as expected. So all that was needed was a null-edit on Pêcher! Sorry, I know that can be frustrating. I hope you understand it a bit better now, though, and of course feel free to ask if you still have questions.

--Rye Greenwood (talk) 13:56, 24 March 2021 (UTC)

This cache...

Thanks again for the clear explanation and for your time, I surely do understand more. --Dinoxel (talk) 21:20, 24 March 2021 (UTC)

Portuguese problems

/pt wiki links

I've been updating the PT wiki recently and came across a problem with all hyperlinks using template:item or template:eil that redirect to <English_name>/pt. I think it might be related to template:Lang thinking the wiki isn't a subwiki but from what I checked pt is placed at the same place as de, fr, ru... are already. Any idea? --Dinoxel ^talk 15:05, 1 August 2020 (UTC)

It's {{tr}} who was the culprit here; its code needs tweaking on language wikis (to prevent that /<lang code> behavior), just like {{lang}}. I've added some comments to the template, and it should be all fixed on PT now. --Rye Greenwood (talk) 19:35, 1 August 2020 (UTC)

{{version}} breaking things

Hey, that new version template you created is a really good idea, however I noticed it causes an error on Versão para Celular. --Dinoxel ^talk 01:16, 5 August 2020 (UTC)

Also causing some problems with {{source code ref}} (see here) --Dinoxel ^talk 01:26, 5 August 2020 (UTC)

Ouh, those are some serious problems; thanks for pointing them out. I resorted to a standard data template solution now, which only differs from others (like the getXInfo templates or Template:ItemInternalNameFromId) in that the database is scarily transcluded into language wikis. That means that the actual database template ({{current versions}} now) is not needed there, the EN one will be loaded directly. --Rye Greenwood (talk) 14:39, 5 August 2020 (UTC)

Spanish Wiki

Hey Rye! I noticed that you made an edit on an /es page here, and I had always assumed the Spanish Terraria wiki was over on Fandom, separate from Gamepedia. Are we (Gamepedia) also hoping to make a Spanish wiki for Terraria? Just curious, as I'd be willing to help some when I have time. Thanks! PuzzledKino (talk) 23:18, 4 August 2020 (UTC)

I just noticed there's an English Terraria wiki on Fandom too! I guess I never noticed, since I don't use that site. I don't know much about the merger, especially because I was absent during most of the discussion, but I suppose I'm mainly wanting to know if you guys need help with the /es pages here :] PuzzledKino (talk) 23:58, 4 August 2020 (UTC)

Right, there are a number of Terraria Wikis on Fandom (including languages for which there is a wiki here on Gamepedia; e.g. Italian or Chinese), sometimes even multiple for one language... Well, they just let anybody create any wiki there. None of the Terraria Wikis on Fandom are "official" in the sense that this Gamepedia wiki and its language variants are "official" (see Gamepedia's Wiki Connect program) – except for the Spanish one. At some point, it was declared the official Spanish Terraria Wiki for some reason; if I was ever told the reason, I can't remember it, unfortunately.

I don't know about the view statistics of the Spanish pages here, but given the lack of activity, I'd assume they're not exactly high. Hence I'm afraid editing the Spanish wiki here would be in vain (though any help is of course always appreciated) when it comes to the total amount of knowledge that Spanish-speaking players gain from the wiki. If you'd like to really help out in Spanish, (never thought that I would ever have to say it) I'd suggest you head over to Fandom. (On that note, I'm more and more impressed by the number of languages that you speak!) --Rye Greenwood (talk) 00:48, 5 August 2020 (UTC)

Thanks Rye! Your description helped me understand things a lot better. And well, I'll keep Fandom in mind, but I really quite like it here on Gamepedia, so I'll probably stick to helping the en/fr wikis here, and the pt/de wikis where possible. And thank you -- while English, Spanish, and French are certainly my stronger languages, I have a big passion for language learning that's rubbed off on the way I edit here. :] PuzzledKino (talk) 01:10, 5 August 2020 (UTC)

Translation projects creating EN interwiki links on EN

I think your last edit on {{Translation projects}} broke something on some English pages. The Health page has an EN interwiki link to Health and Mana Accessories and Health and Mana Accessories to Health and Mana Accessories/row. Also, Philo told me it was redirecting to Damage Booster for him. --Dinoxel ^talk 11:01, 21 August 2020 (UTC)

Fixed. --Westgrass (talk) 13:08, 21 August 2020 (UTC)

Thank you both! --Rye Greenwood (talk) 18:59, 21 August 2020 (UTC)

Loot info for drop infobox

Your new {{drop infobox}} is great! Since items are not only dropped from enemies but also looted from Chests/Treasure Bags/..., Is it possible to include loot info in {{drop infobox}} as well? For example, the Bee Wax, drop infobox says it is only dropped in classic mode, but, in fact, it is also dropped in expert/master modes as well (from Treasure Bag). It may be misleading to only show enemy drops. --Westgrass (talk) 01:42, 24 August 2020 (UTC)

Thank you! Yes, I was thinking of that as well when I looked at the Bee Wax page yesterday. I've come up with a way to integrate Treasure Bag contents into the {{npc infobox}} (see King Slime and Queen Bee for examples), so this information is in the Drops table now as well and will be displayed by the {{drop infobox}}. I'll see if I can find a nice solution for the other drop sources; which would be Chests and Crates, right? Perhaps Pots? --Rye Greenwood (talk) 00:41, 25 August 2020 (UTC)

Russian Drop infobox

Hey there! Rye, I can't to update Template:Drop infobox in Russian section. There's error occured: Drops table doesn't found. Can you help? ← Alex Great ^talk/_rus? 03:23, 24 August 2020 (UTC)

Ok, I fixed this problem with creationg Drops table in Cargo. But it have another problem: Russian Wiki haven't NPCs table in Cargo. I know that all info works fine in NPC infobox without this table. Is it possible to fix it, or I really needs to create this Cargo table? ← Alex Great ^talk/_rus? 03:34, 24 August 2020 (UTC)

The NPCs table is used for displaying the image of the NPC, but it falls back to a simple {{item}}, so it's really only a convenience. I've made a small fix, the template should be working for you once you sync that. You might get a different NPC image here and there, since the image of {{item|<NPC>}} is not always the same one that's stored in the NPCs table, but that's not a big deal; it will still be understandable. --Rye Greenwood (talk) 00:41, 25 August 2020 (UTC)

I sync the template, but it still have an error: Ошибка: не найдено ни одного поля с именем «image» для любой из указанных таблиц базы данных. which can be translated as Error: No one filed with the "image" name for any of this data base tables doesn't found. ← Alex Great ^talk/_rus? 04:06, 25 August 2020 (UTC)

Right, sorry. Should be fixed now. --Rye Greenwood (talk) 07:36, 25 August 2020 (UTC)

Hy, Rye. I'm updated the Drop infobox, but now it's have an operator error in the template. I also created Template Bool, but error still there. Can you help me with it? ← Alex Great ✉ 03:17, 23 December 2020 (UTC)

Hi, I have added a column to the Drops cargo table in this edit to Template:Npc infobox/drop, which means that I had to recreate the table in order to put the changes into effect. The Russian Drops cargo table doesn't have this new column yet, so you'll have to recreate it, too. --Rye Greenwood (talk) 12:52, 23 December 2020 (UTC)

Ideas for Drop infobox

Hey, I've been checking your new template recently and came across some things I had to tell you:

First, it could collapse if there are more than 5/10(?) enemies in the list (thinking about mobile users and their little screens),
Second, a picture (such as File:Bestiary Boss Enemy.png that totally fits that feature) could be displayed in order to catch the sight of visitors,
And last, similar to "list of x weapons"/"individual debuffs" pages, it needs a purge after saving, I guess a note should be added somewhere or literally a {{purge cargo}} I don't know.

I tried adding the picture in many ways but it's always breaking the collapsing table. What do you think? I added the template and let it to Depth Meter for the moment. --Dinoxel ^talk 07:24, 5 September 2020 (UTC)

I also found out that when the infobox is transcluded from individual Boss pages to their guide, it displays twice. --Dinoxel ^talk 14:18, 12 September 2020 (UTC)

Good suggestions! The infobox is now collapsible just like a navbox, and will display in the collapsed state by default if it contains more than five entities (I'm not sure either if this is a sensible value, but it can be tweaked anytime). I've added the image to the box title and fixed the duplicate storage on strategy guide pages. --Rye Greenwood (talk) 14:45, 14 September 2020 (UTC)

Great job, looking good as always!

Also, the new layout for Treasure Bags (i.e. Queen Bee) seems to cause some problem with the displays of Expert and Master. See Bee Wax. --Dinoxel ^talk 16:38, 14 September 2020 (UTC)

Thank you! Treasure Bag contents should display correctly now. --Rye Greenwood (talk) 21:27, 14 September 2020 (UTC)

Shadow Orb displaying the wrong image / NPCs using tableView

Hey, the Band of Starpower on the Health and Mana Accessories page displays the item image instead of the tile. --Dinoxel ^talk 14:52, 24 September 2020 (UTC)

Also, I added {{Drop infobox}} to the Slime Staff page and it seems to not work properly with Zombies using the tableView --Dinoxel ^talk 15:06, 24 September 2020 (UTC)

Fixed both issues, thanks for noting! --Rye Greenwood (talk) 12:48, 27 September 2020 (UTC)

Using |wrap=y to save width

Hey, do you think |wrap=y could be applied to all names on the drop infobox so it will save width and avoid having the name below the file for several npc names. --Dinoxel (talk) 13:00, 1 November 2020 (UTC)

Hm, that would be good, yeah. I don't currently see a solution where the icons only go on a new line if the text is still next to the image, though. Enforcing a wrap would always cause the icons to go on a new line. In situations with very wide images where the text is already underneath the image, another extra line just for the icons wouldn't look good, in my opinion. I'll think about it, or maybe someone else has a solution. --Rye Greenwood (talk) 15:43, 1 November 2020 (UTC)

Also, I think I added {{Drop infobox}} to 99% of the pages that would need it in my opinion, I suppose one solution would be to create on infobox with all the table to visually see which images take the most place, even if I expect it to be mostly bosses. The width value of boxes could be increased or the max-width value of images could be decreased by a few pixels, or both I'm not sure what would be the best. --Dinoxel (talk) 17:33, 1 November 2020 (UTC)

Eicons don't display on language wikis

While I'm there if I get it right, because {{Drop infobox}} uses the NPC cargo and thereby French names on the French wikis, no icons are displayed after npc names (i.e. fr:Forte potion de soin). Do you have any idea how that the template could use language names and icons from English names? --Dinoxel (talk) 17:33, 1 November 2020 (UTC)

Discord

Hi,we noticed that you are inactived on Discord for a long time. Many of us miss you very much. --Westgrass (talk) 14:55, 27 August 2020 (UTC)

I haven't gotten around to getting Discord to work on the device I switched to some time ago. I'll see you there soon, hopefully! --Rye Greenwood (talk) 21:26, 28 August 2020 (UTC)

A note about {{plural:}}

Just a reminder: the results of {{plural:0|A|B}} are different on Wikis in different languages. For English, it is B, but for French it is A. So, we should avoid using {{plural:0}} in l10n. -- Westgrass (talk) 17:13, 30 August 2020 (UTC)

I see; thank you. --Rye Greenwood (talk) 13:22, 2 September 2020 (UTC)

Combat accessories page

Hey, I'm not sure if you've already seen this discussion, but the Combat Accessories page seems to be totally broken, returning a "generated node count limit exceeded" error. --Eraloiz (talk) 21:49, 30 September 2020 (UTC)

Sorry, I wasn't online for a few days and haven't noticed that. It looks like Westgrass already fixed the error. Thanks for letting me know, though! --Rye Greenwood (talk) 22:00, 3 October 2020 (UTC)

Module:Exclusive/data

Hi, Rye! I noticed that you recently updated Module:Exclusive/data. And in last edit (by your bot) you removed separated Golf Trophies. As I always updated Russian version by alphabetical order, you can see the changes of last edit. ← Alexis oʼMegas ^✉/_WP 05:09, 12 October 2020 (UTC)

Fixed that – the individual trophies' pages simply needed a null-edit. Thanks for noting! --Rye Greenwood (talk) 13:00, 12 October 2020 (UTC)

Rock Walls and Beehive was removed from the database. See diff there. ← Alexis oʼMegas ^✉/_WP 05:16, 15 October 2020 (UTC)

Well, that's because neither of them were categorized in any version categories at the time you updated the database. --Rye Greenwood (talk) 16:07, 15 October 2020 (UTC)

Missing recipes on Hardmode Anvil

Hey, I found more or less the same problem on Recipes/Hardmode Anvil, the 12 recipes after the second Spectral Subligar recipe on Recipes/Hardmode Anvil/register don't appear anymore. I noticed a difference of 12 recipes when you recreated the cargo table, I have no doubt this is related. But unfortunately again, fixing this problem is out of my league. --Dinoxel (talk) 01:14, 15 October 2020 (UTC)

fixed. Westgrass (talk) 02:57, 15 October 2020 (UTC)

Item infobox

Hi. Something wrong in your last edit if Template:Item infobox. Please check it for pair of {{ and }} or something similar. Because the syntax highlighter show the mistake in the code. ← Alexis oʼMegas ^✉/_WP 09:20, 19 October 2020 (UTC)

Mhm, I forgot some syntax highlighters process the five brackets in a row incorrectly. It should be good now. --Rye Greenwood (talk) 12:44, 19 October 2020 (UTC)

Hey, it seems that your recent edit on Item infobox is breaking the buff column on the Fishing foods page. --Dinoxel (talk) 02:27, 20 October 2020 (UTC)

Thanks, I totally forgot about the tableView. Should be fixed now. --Rye Greenwood (talk) 21:24, 20 October 2020 (UTC)

Also, your tweak on item infobox makes it now impossible to use the | buff parameter such as on the pre-1.4.0.1 infobox with the Shadow Dodge on the Titanium armor page. --Dinoxel (talk) 10:31, 21 October 2020 (UTC)

Fixed that, too; thank you. --Rye Greenwood (talk) 14:59, 21 October 2020 (UTC)

Terraprisma Configuration

I found this through inventory editor, which also have a buff editor. I assume this is a helix, but i can be mistaken by something else though--Daud ahn (talk) 22:59, 6 December 2020 (UTC)

Oh interesting, thanks for this! Now I understand your edit much better and I agree, that looks like a helix. I went ahead and added a link to the image for better comprehension. --Rye Greenwood (talk) 16:20, 7 December 2020 (UTC)

I still think it should be noted as a wing pattern on the Terraprisma page. That's what it was most likely intended to look like with the actual number of capped minions. The helix pattern just comes from the mathematical formula they used for the wing spread going beyond its intended limits. We should stick with what's in the game and not what we see only with hacked numbers. --107.2.104.203 16:24, 7 December 2020 (UTC)

Sorry if this discussion isn't supposed to get so long, but I think the best course of action is to call it a wing as before, and move the helix bit to Notes or Trivia (not sure which exactly.) Something like "The minions' pattern actually forms a helix, but this is only visible when using third-party tools to exceed the minion limit." I do hope this is a viable option. --2057clones (talk) 16:37, 7 December 2020 (UTC)

I reckon it's better to continue this at Talk:Terraprisma. --Rye Greenwood (talk) 13:27, 10 December 2020 (UTC)

Broken page?

The Bone page seems to be broken but I'm not sure if it's on my end, if the last edit broke it or if it's just gamepedia having some issues. What's odd is if you look at it as a most recent edit it seems to be fine even though it should be the same source. --107.2.104.203 23:30, 16 December 2020 (UTC)

I don't see an error currently; does it still look broken for you? It happens that pages look broken sometimes. You can usually make sure that it's not only on your end by refreshing your cache or checking with another browser. If the error persists, then you can purge or null-edit the page; that often fixes errors related to server-side caching. --Rye Greenwood (talk) 23:39, 16 December 2020 (UTC)

I'll give that a shot. I sent the page to a random friend to double check and the page was broken on their end as well. One of these days I'll actually learn the ins and outs on how to edit this wiki more than cleanup work. I've been here long enough where I have no excuse. --107.2.104.203 23:43, 16 December 2020 (UTC)

The purge did the trick. Thank you. --107.2.104.203 23:52, 16 December 2020 (UTC)

No problem! --Rye Greenwood (talk) 09:47, 17 December 2020 (UTC)

Cargo usage of "Items" in Russian section

Hi, Rye. I have an issue with updating of Russian version of Tools article. Can you please help with it by checking ru:Инструменты#Кирки и буры page. I know that it uses a Cargo tabe of "Items" that I haven't in Russian section because it perfectly works in other articles without that Cargo table. Is it possible to fix it or I really needs to create "Items" cargo table for workable list of Pickaxes and Drills at Russian article? Thanks and Happy New Year. ← Alex Great ✉ 08:36, 1 January 2021 (UTC)

Ok, Philo04 already helped me with resolving this issue. I'm currently used static version from Tools/static. ← Alex Great ✉ 11:05, 1 January 2021 (UTC)

Happy New Year to you, too! Yes, those static subpages are meant to be used exactly in your case. You can find a list of all of them (well, there's only a handful of them, in fact) at Category:Static subpages. If you come across another page that uses DPL or cargo to create such a list, though, a new one for that can surely be made. --Rye Greenwood (talk) 12:48, 1 January 2021 (UTC)

Hi again, Rye :) I have another trouble with counter and full list of Arrows in ru:Стрелы. (English Arrows count is 17, when Russian article have only 10) Dinoxel said that you can make a page for all non existed infoboxes for correct working of same counters and a list. Can you do it? Or maybe how to fix this issue with /static variant? P.S. I also have an issue with unknown 2 ?'"`UNIQ--nowiki-00000002-QINU`"' in Wooden Arrow Sell (Стоимость) cell. Idk, how tof fix it. ← Alex Great ✉ 14:50, 6 January 2021 (UTC)

Dinoxel is right, I can let my bot copy all {{item infobox}}es from here to the RU wiki. I recently changed my bot setup a little, so I'll have to update that script; hopefully I can complete that today. As for the other issue: The error is in the row of ru:Деревянная стрела, which transcludes {{cc}} in the sell parameter of its {{item infobox}}. The {{cc}} template on RU includes a <nowiki/> tag, which cargo isn't too fond of. Simply sync your {{cc}} template with the newest English version, null-edit the Деревянная стрела page, and it should be good. --Rye Greenwood (talk) 12:00, 7 January 2021 (UTC)

Thanks for the first and big thanks for the second. Now coins works good. ← Alex Great ✉ 13:29, 7 January 2021 (UTC)

No problem. The bot is pasting all infoboxes on RU currently, it will be finished in about maybe an hour. Sorry it took so long to get that started! --Rye Greenwood (talk) 16:46, 9 January 2021 (UTC)

Previous edit on LangList

Hey, just letting you know that you recent edit on {{LangList}} broke the display of {{current versions}} on language wikis. --Dinoxel (talk) 20:24, 7 February 2021 (UTC)

Thanks! That was because I missed an edit to {{version}} (and also to {{navbox}}, for that matter). There should be no issues with {{langList}} not using {{lang}} if all of the following templates are synced with the most recent English version (you probably synced them all already, quick as always; this is more in response to Alex Great's comment):

--Rye Greenwood (talk) 19:53, 8 February 2021 (UTC)

Oh, and should there still be problems, then it's fine to leave {{lang}} in {{langList}}, since the {{lang}} on language wikis doesn't use {{langList}} anyway, so there's no template loop like on EN. --Rye Greenwood (talk) 19:55, 8 February 2021 (UTC)

Perfect, everything is looking fine now ! ;) --Dinoxel (talk) 21:26, 8 February 2021 (UTC)

Template "Unsigned" in Russian

Hello, Rye. I updated Russian version of Template:Unsigned with /l10n and /doc subpages. But as you can see Russian {{unsigned}} works different. It's always "Westgrass" instead of name of registered user in Example and it's always as "IP. Idk, why. ← Alex Great ✉ 04:34, 20 February 2021 (UTC)

And also see 5th example, where "unsigned comment was added by current time at Westgrass" (vise-versa result don't work). ← Alex Great ✉ 04:37, 20 February 2021 (UTC)

Thanks for fixing IPs. But 5th example (see above) still actual. ← Alex Great ✉ 02:47, 21 February 2021 (UTC)

Sorry I didn't get back to you. All that was missing for the original problem was {{isIP}}. Regarding the other thing, I couldn't figure out a way to reliably validate the input, i.e. check if it is a registered user name (even with a combination of {{isIP}}, DPL (which doesn't seem to work as expected at all with modifiedby), and {{gender:}} (which seems to be broken completely)) or a valid timestamp ({{#time:}} only recognizes English input, and doing some kind of localized-month-name-registration in a loop with reversed {{#time:}} would be ridiculous). Hence, I resorted to simply assuming the following:

If there's only one unnamed parameter given, it's the username.
If two unnamed parameters are given, the first one is the username and the second one the timestamp.
- Only on EN: If the second unnamed parameter is not a valid timestamp, then it is the username, and the first unnamed parameter is the timestamp.

It's really best to just use {{unsigned|<username>|UTC=<UTC timestamp>}}, nothing will behave unexpectedly then.

--Rye Greenwood (talk) 14:23, 21 February 2021 (UTC)

Ok, interesting. What about 5th example in English /doc? I see "Monday2021" at the end. ← Alex Great ✉ 02:17, 22 February 2021 (UTC)

Yeah haha, see, even on EN it doesn't work 100%. Monday2021 is a valid timestamp (although it doesn't make much sense: {{#time:r|Monday2021}} → Mon, 22 Apr 2024 20:21:00 +0000), so it is considered the timestamp of the edit, and the first unnamed parameter (the actual timestamp of the edit) is considered the username. That's why at least one of the two pieces of information (username or timestamp) should be passed via a named parameter, like in the eighth example in the template doc. --Rye Greenwood (talk) 08:15, 22 February 2021 (UTC)

OK, I understand. Thank you. ← Alex Great ✉ 02:16, 23 February 2021 (UTC)

Set bonus of Ancient Hallowed armor

Hi Rye, I noticed that {{getSetInfo|Ancient Hallowed armor|setbonuslist}} outputs nothing, I think that is not correct. Could you please take a look on it? Westgrass (talk) 09:47, 1 March 2021 (UTC)

There was an error in Template:GetSetInfo/db: the set bonuses were set to inexistent {{gameText}} keys. Fixed, thanks for noting! --Rye Greenwood (talk) 22:33, 1 March 2021 (UTC)

Display Buy values for Tavernkeep armors

Hey, I've been trying to display automatically the buy value for Tavernkeep armors using {{Setinfo}} but I cannot get it on armor infoboxes. It now works fine using {{setinfo|Dark Artist armor|buy}} though although I think the code could be tweaked a bit. Didn't try it on language wikis yet. --Dinoxel (talk) 12:41, 18 March 2021 (UTC)

I've tried it out on Dark Artist armor and it looks fine to me, great addition! Maybe the handling whether or not to use {{dm}} can be expanded a bit, but it seems to be working fine so far. --Rye Greenwood (talk) 18:09, 18 March 2021 (UTC)

Oh wow ok, I guess I should blame cache then. hehe --Dinoxel (talk) 19:29, 18 March 2021 (UTC)

Yeah, haha, if nothing else is to blame, then it's caching. So, I took a shot at improving DM handling and realized it required quite some restructuring, especially since a set might be composed of both items that are bought with normal coins and items that are bought with DMs (not that such a set is in the game, but the template supports manually setting head, body, and leg pieces). It should be working intuitively now, but please let me know if there are any errors. --Rye Greenwood (talk) 16:24, 19 March 2021 (UTC)

Setinfo doesn't work on Master Gamer's set

For whatever reason, it doesn't work properly. The info is also empty in the Items cargo database which I recreated. --Dinoxel (talk) 14:22, 7 April 2021 (UTC)

That was an error in the template caused by my last modification. I had falsely assumed that a set would always have a head piece, but since that's not the case with the Master Gamer's set, the calculation was skipped entirely. Fixed it now, thank you for reporting! --Rye Greenwood (talk) 15:27, 7 April 2021 (UTC)

Purge link on sitenotice

Hey, for whatever reason the purge link on {{Sitenotice problem fixing}} redirects to a random page on the wiki (not only articles, all of them). I'm not sure what causes it, I tried digging into {{Fullurl}} but I doubt it's related to it. Any idea? --Dinoxel (talk) 12:50, 14 April 2021 (UTC)

Hm, I haven't noticed that before but I see it now. After a bit of testing, I realized that the {{FULLPAGENAME}} magic word (or any other magic word related to the current page) doesn't work as expected if used in MediaWiki:Sitenotice (maybe because that is loaded before the page title is known or something, I don't know). Instead, it counterintuitively returns a seemingly random page title, for whatever reason. I'm afraid the only solution here is to remove the page-dependent, dynamic links for purging and switching to Desktop view, and give directions how to do that manually. (Well, JavaScript would be an option, but that might be disabled for some readers.) Anyway, thanks for reporting. --Rye Greenwood (talk) 14:51, 14 April 2021 (UTC)

Ideas to keep a track of English pages using {{Article quality}} on language wikis

Hey, I can't help myself but I've followed what's happening on DE lately and thought of something: what about creating a template that can detect when an edit is made on an English page having a language-equivalent page with a {{aq|5}}. That way, it'll be easy to keep a track of edits on the English wiki for fully translated language pages.

I also thought about not adding the said English page to the category/table if the next edit contains a undo or revert tag, meaning the edit was insignificant. --Dinoxel (talk) 17:46, 20 April 2021 (UTC)

That is an excellent idea! I don't reckon it could be done with a purely wikitext-based template, because I can't think of any way to connect the two wikis (as in, extract the DE/FR/... interwiki link target from an EN page) via wikitext, but with JavaScript it would surely be possible. Once I've made a bit more progress with the merge, I'll see what I can do. Also, I'm glad you're around over there, Dinoxel! It's nice to know that I'm not alone in this transition. --Rye Greenwood (talk) 13:47, 21 April 2021 (UTC)

Wonderful! It's quite natural! :) Even if I doubt it as you're a Template master, if I can help you in anyway, don't hesitate to ask! --Dinoxel (talk) 18:32, 21 April 2021 (UTC)

That's very kind of you, haha! I created a first version (though I didn't include the undo/rollback filter for now). You can see it at de:User:Rye Greenwood/Sandbox11 and you can also try it out on FR/PT (simply copy my sandbox). Let me know if you think of anything that could be improved! --Rye Greenwood (talk) 13:11, 13 May 2021 (UTC)

Immunity accessories is broken

Hey, I think your recent edits on {{equipinfo}} broke the page. --Dinoxel (talk) 06:04, 3 May 2021 (UTC)

That's right, sorry about that. Fixed it, thanks for notifying me! --Rye Greenwood (talk) 12:09, 3 May 2021 (UTC)

Exclusive versions on O-G/3ds npc infoboxes

Hey, it seems that versions don't display anymore on exclusive NPC infoboxes such as on Orca. --Dinoxel (talk) 20:54, 8 June 2021 (UTC)

Thanks for reporting! I turned the ni:variant variable into a simple Boolean switch because the $variant parameter wasn't used with a version string like "mobile/console" anywhere, but apparently I forgot changing that in the infoboxView. Your change here was right already, by the way! --Rye Greenwood (talk) 16:40, 9 June 2021 (UTC)

That's what I understood from the history yeah. I guess I should wait more time between my purges and edits :p --Dinoxel (talk) 20:07, 9 June 2021 (UTC)

Debuff links on Combat Accessories are broken

That's it. Also happens on fr:Accessoires de combat. --Dinoxel (talk) 20:06, 9 June 2021 (UTC)

This one involves a bit of digging, haha: The Combat Accessories page uses {{Accessories/typerow}}, which uses {{equipinfo/lua}} to display the "Effect" column. That template invokes Module:Equipinfo, which used {{buffNameFromId}} to convert the debuff IDs into names and then link them via {{eil}}. The {{buffNameFromId}} template calls {{getBuffInfo}}, which uses {{gameText}} to display a buff name, and there was the root of the issue. Westgrass modified {{gameText}} earlier today so that it wraps the output in HTML <span> tags. Tracing back our steps, this meant that {{getBuffInfo}} returned the debuff name wrapped in <span> to {{buffNameFromId}}, which gave it to Module:Equipinfo. That module then passed this <span>-wrapped debuff name to {{eil}}, which was unable to turn that into a link, because it cannot handle input that contains HTML tags. Therefore, it caused the output that you saw, with the two brackets around each debuff name. The fix that I applied now (and that might not be the best solution, but it's working for now) was to add an option to restore the original behavior of {{gameText}}, i.e. without the HTML tags around the output. The debuff name is hence a purely textual string again that can be handled without problems by {{eil}}. I'm afraid you'll have to sync a couple of edits on FR to fix the problem there: Module:GameText, Template:GameText, Template:GetBuffInfo, and Module:Equipinfo. I also made an edit to Accessories/typerow, though that is a minor fix unrelated to the debuff link issue. Hope this helps! --Rye Greenwood (talk) 22:44, 9 June 2021 (UTC)

Template:GetSetInfo does not support some vanity set.

For example: Bunny set. There is no buy/sell value for the set, and the rarity info is wrong. Westgrass (talk) 09:42, 15 June 2021 (UTC)

Hmm, the Zoologist's sets only have one item that has an armor ID; the other item is an accessory. The automatic {{setinfo}} works with armor IDs, though, so it cannot handle accessories, and hence those sets are not included in {{getSetInfo/db}}. I fixed the issue by manually setting the item infobox parameters (with a manual input, {{setinfo}} works with any kind of item; see the bottom of the template doc). Let me know if there are also issues on other pages or if it was only the four Zoologist's sets. --Rye Greenwood (talk) 11:27, 18 June 2021 (UTC)

Bot commands

Hey, would you mind using your bot to remove extra | allversions = yes and rename | duration to | debuffduration on FR, PT, and PL. Thanks in advance! --Dinoxel (talk) 17:29, 8 August 2021 (UTC)

Sure! Unfortunately, I have only very limited internet access currently, as I'm on vacation. I'm afraid I won't be able to get this done until in about two weeks, when I get back. --Rye Greenwood (talk) 22:04, 8 August 2021 (UTC)

All good, enjoy your vacation! --Dinoxel (talk) 23:02, 8 August 2021 (UTC)

last night I was a little worried about your inactivity in the last 2 weeks and hoped that nothing bad happened. Glad to know you are enjoying the good.Westgrass (talk) 05:15, 9 August 2021 (UTC)

Thank you both! The bot has completed the parameter renaming on all three wikis, and the remaining allversions should all be needed ones. --Rye Greenwood (talk) 15:23, 23 August 2021 (UTC)

Template:aq no longer displays

Hey, since the wiki is using the FandomDesktop skin, stars no longer display on FR, PT, and DE. Do you have any idea how to fix this? --Dinoxel (talk) 09:18, 24 August 2021 (UTC)

I have been occasionally thinking about this since the release of FandomDesktop, but I haven't found a good spot for the stars yet. The "page indicator" area, where the stars (and also the translation project banner on the EN wiki) used to be, is now cluttered with the language dropdown, and the edit button, and the three-dot dropdown... The light blue "WikiaBar" in the bottom right might be suitable, but it's quite wide already. We could of course also switch to a different design, maybe only a single star that is partly white and partly yellow like a pie chart, or something completely different. What do you think? --Rye Greenwood (talk) 13:35, 24 August 2021 (UTC)

Which exact template were you talking about? Westgrass (talk) 19:23, 24 August 2021 (UTC)

Template:Aq on the DE wiki, short for "article quality". It is transcluded on every page with a parameter set to a value of 0–5 as a rough assessment of the page's quality, i.e. how up-to-date and complete (in comparison to its EN equivalent) the article is. It's part of an endeavor to get more insight into which pages need work (an overview can be found at de:Terraria Wiki:Projekte/Artikelqualität) and also exists on FR and PT. In Hydra, the template displays five Fallen Stars in the upper right of the page that represent the quality (see e.g. de:Frostrüstung with Hydra) but, well, Fandom has unfortunately gotten rid of the indicator area with the new skin, so the stars are not visible in FandomDesktop. --Rye Greenwood (talk) 21:35, 24 August 2021 (UTC)

I will take a look into it to see if there is a feasible solution. Westgrass (talk) 11:37, 25 August 2021 (UTC)

Hello Mr. Rye

If you need verification from the game files or from older versions of the actual game, along with any demonstrations or anything really, I'm here to help, I'm online very often as well ;) AmsterWikis (talk) 00:35, 2 November 2021 (UTC)

That's good to hear, thanks for your contributions! --Rye Greenwood (talk) 18:22, 2 November 2021 (UTC)

Just message me on my talk page or something :D --AmsterWikis (talk) 20:25, 2 November 2021 (UTC)

Ore Standardization

I find it strange to hear a singular noun without "The" in front of it. e.g. "__ Bar is an ore". It just sounds wrong to me. Please consider changing them to "The __ Bar" for all of them, or "__ Bars are". --AmsterWikis (talk) 00:59, 17 November 2021 (UTC)

Sure, I've added a "The" to those pages now. --Rye Greenwood (talk) 15:12, 17 November 2021 (UTC)

RyeBot didn't update all the selected pages

Hey Rye, hope you're doing well!

I've finally started using your bot instead of manually updating pages on language wikis and came across two problems:

First, as you can see on this edit, I've tried to update Recipes/Hardmode Forge/register on FR, PL, and PT but it resulted in creating Receitas/Forja do Modo Difícil/register on the three wikis instead.

Second, on this edit, I've tried to update all the recipe pages on the French wiki but the bot only updated a few of them, as you can see here, none of the recipe pages having new recipes got updated. (i.e. By Hand/register with À la main/register)

That's it, thanks in advance for your help. --Dinoxel (talk) 14:46, 21 November 2021 (UTC)

Hi Dinoxel, sorry that you ran into issues, and thank you for reporting them! I appreciate that as always. The first error was caused by a tiny oversight (with a large impact) that I fixed now, so that part should work as expected now. The second one is quite simple: The bot could not edit most of the recipe registration pages because they're protected. I'm afraid there's no way around either making the bot an admin or lowering the protection.

I've added {{interwiki links}} to all the recipe registration pages here on EN and run the bot again. It has updated all the pages on PL and PT correctly (looks like they're not protected there) and a couple of unprotected pages on FR. --Rye Greenwood (talk) 02:49, 23 November 2021 (UTC)

Wonderful, thanks for the quick response! ;) Ah right, permission problems. I've set it up temporarily as an admin on FR, probably the fastest way to counter that yeah. Just started it, seems to have worked just fine!

This {{interwiki links}} template really comes in handy, we should really consider adding it on every page/template although I'm not sure how it could manage sub-language wikis on language wikis. --Dinoxel (talk) 08:29, 23 November 2021 (UTC)

Yeah, the template is quite useful for syncing templates and modules. For normal articles; I don't see a way to automatically retrieve e.g. the Italian translation of a page on e.g. the FR wiki. Here on EN, we can easily fetch them via DPL as they're on the same wiki, but unfortunately DPL can't be used cross-wiki. --Rye Greenwood (talk) 19:06, 24 November 2021 (UTC)

Actually, I think I might know how.

First, {{interwiki links}} must be on all pages with at least the EN link (which will be later used as the key to fetch other language links on sublanguage wikis), the template will automatically find sublanguage pages using something like <pagename>/<lang> with <lang> being the in {{langList|onWiki}}.

Second, all these sublanguage interwiki links will be stored on a Cargo table using the EN link as the key and will have a static page just like how Module:Exclusive/data is handled.

Also, the more I think about it, the more I think both {{Translation projects}} and {{interwiki links}} could be merged together. --Dinoxel (talk) 20:19, 4 December 2021 (UTC)

That's a great idea, that could work! It would still require frequent syncing of that static module, but obviously that's much easier than keeping all the interwiki links on all the pages up-to-date individually (and it can be automated easily as well). I'll try and see how we can implement this. --Rye Greenwood (talk) 02:58, 5 December 2021 (UTC)

┌────────────────────────────────────────────────────────────────────────────────────────────────────┘ Alright, I think I've managed to come up with a decent solution. It's slightly different from what you suggested: I figured we don't need a cargo table on the EN wiki, but we do need it on the language wikis. Similarly, the static page (which is just a template that fills the cargo table with data) is not needed here on EN, only on the language wikis. I did put {{translation projects}} into {{interwiki links}}, but I'd still like to keep that template separate.

I've described the system on Template:Interwiki links. Essentially, every English page stores all off-wiki interwiki links, and every on-wiki and off-wiki page simply needs to transclude {{interwiki links}} and will get all interwiki links (on-wiki and off-wiki) automatically. To try it out on FR, you'll need to sync Template:Interwiki links and Template:Interwiki links/print, copy the code from Template:Interwiki links/datagen and put it into a new page fr:Template:Interwiki links/data, create the cargo table from there and null-edit the page again. Replace the manual interwiki links on fr:Guide with {{interwiki links}} and you should get the entire list of interwiki links, both on-wiki and off-wiki (i.e. also cs, it, etc.). Guide is the only mainspace article that I've put the template on for now, for testing purposes, but if you think everything's alright, I can have my bot put it on every page like intended.

--Rye Greenwood (talk) 01:04, 7 December 2021 (UTC)

I'm speechless, it took you only two days to come up with this, you're really a mad man! This is also very well documented, as usual. Thank you, that's perfect!

Just tested a few things already, it's working so well! I give you the green light for the bot! --Dinoxel (talk) 23:26, 7 December 2021 (UTC)

By the way, I guess your bot could automatically update it (with Module:Exclusive/data while we're at it) on all the concerned wikis once every day/two days if the page has changed? --Dinoxel (talk) 23:35, 7 December 2021 (UTC)

It seems that {{Interwiki links/datagen}} cannot display all the pages for the Cargo db, it stops at 'Charged Blaster Cannon' --Dinoxel (talk) 09:49, 9 December 2021 (UTC)

Thank you for the kind words! The bot completed the first pass of pages, I think it'll be finished with the rest in the next few days. And sure, I can set up an auto-synchronization so that those databases stay up-to-date on the language wikis.

I realized that my approach caused a way-too-heavy load on Template:Interwiki links/datagen; it's simply not able to generate that much code on its own. That's why I did end up creating a cargo table here on the English wiki, which is populated by {{interwiki links}}. The datagen template can now essentially just display the entire data of that cargo table, so that should work correctly now (that is, only for the pages the bot has already processed, of course).

--Rye Greenwood (talk) 05:27, 12 December 2021 (UTC)

Wonderful! :) --Dinoxel (talk) 11:14, 14 December 2021 (UTC)

Magiluminescence doesn't display its source

I've added it to Movement Accessories and even recreated the Items cargo table but it still doesn't display anything. --Dinoxel (talk) 20:19, 4 December 2021 (UTC)

Thanks for reporting! This one is a bit convoluted, bear with me: Accessories/typerow, the row subpage of Movement Accessories, uses Template:Itemsource to display the accessories' sources, which only displays the crafting recipe of e.g. the Magiluminescence if its listcat in the cargo table contains "craftable items". That listcat is set by {{item infobox}}, which in turn automatically sets the listcat if {{iteminfo|Magiluminescence|craftable}} returns true. That wasn't the case because the "craftable" attribute of the Magiluminescence was set to false in the root database, Module:Iteminfo/data. I tried regenerating that database and noticed that the "craftable" and "material" attributes of all items were set to false – so the problem was rooted in the database generator, Module:Iteminfo/datagen. The issue was caused by {{gameText}} wrapping its output in <span> tags, which I believe we have already talked about before. I've fixed that issue and regenerated the database (and of course, you might've guessed it, null-edited the Magiluminescence page, so that the {{item infobox}} there updates the Magiluminescence's listcat in the cargo table), and the item source shows up correctly now. --Rye Greenwood (talk) 01:58, 5 December 2021 (UTC)

Ah, wonderful. Totally didn't expect Module:Iteminfo to have a problem. Yeah, I remember talking about something similar too. Good job again, you're the best! --Dinoxel (talk) 23:30, 7 December 2021 (UTC)

Template:Fullurl

In Template:Fullurl, what is the purpose of {{#vardefine:fullurl:encode|{{#if:{{{text|}}}|{{#if:{{bool|{{{noencode|}}}}}||y}}}}}},
specifically, the {{#if:{{{text|}}}|...?
Can you give an example where you would not want to encode the url?

When the text param isn't used, the query string wouldn't be encoded. With {{fullurl | Terraria Wiki:Sandbox | action=edit | preload=Terraria News}}, "News" wouldn't be included in the query string because of that space. Is this intended? — Ferretwings, Wiki Specialist 13:05, 14 December 2021 (UTC)

This must be a bug. See the last two examples on Template:Fullurl/doc, the result of the last example is not as intented, obviously. --Westgrass (talk) 02:32, 15 December 2021 (UTC)

Uploading a new version of an image is broken!

So, I want to point out that every time I upload a new version of some random image instead of it appearing as a new image, it appears as the same image but with bad quality. Can anyone tell me why this is happening to me? Angrybirdgamer (talk) 13:59, 13 April 2022 (UTC)

I was able to upload a new version of this image just fine, so I'm afraid I don't have the same problem. If you're still experiencing this issue, could you provide some screenshots? --Rye Greenwood (talk) 06:54, 14 April 2022 (UTC)

Well, it seems that I am not experiencing this problem anymore! Although it probably might happen again but if it does, I will provide some screenshots.Angrybirdgamer (talk) 13:04, 14 April 2022 (UTC)

That may be a cache issue. Using Ctrl+F5 may solve the problem. BadPiggy1024 (talk) 08:25, 14 April 2022 (UTC)

Alrighty! I will give that a try then! Thanks! Angrybirdgamer (talk) 13:04, 14 April 2022 (UTC)

It is a known cache issue. Wait a while it will be ok then. Westgrass (talk) 09:05, 14 April 2022 (UTC)

Alrighty! Thank you! Angrybirdgamer (talk) 13:04, 14 April 2022 (UTC)

Wiki timeout errors

For the past couple weeks, I have been experiencing this wiki problem were going into any page would sometimes time out and then go into an error page. However, the error only occurs if the page has been loading for too long. I notice this wiki uses "Cloudflare's Always Online" system which doesn't seem to work for me all the time and also the error page states that the host is not online for some weird reason.

Is anyone else experiencing this problem too? Angrybirdgamer (talk) 13:52, 3 May 2022 (UTC)

Yes, I've experienced that a couple of times as well. I'm afraid there's not much we as editors can do about that; that would be something for the wiki.gg folks. --Rye Greenwood (talk) 14:51, 4 May 2022 (UTC)

When this happens, most of the time the edited content has actually been saved, if you revisit the page you will see the updated content. --Westgrass (talk) 08:49, 17 May 2022 (UTC)

Terraria.NPC.SpawnNPC()

I just finished reading through the code of Terraria.NPC.SpawnNPC() method, and came up with a fully commented code. I found that there are many details in the code that can be used to improve and correct various wiki pages. I would like to share this document with you, but I have no method to send it to you. --Westgrass (talk) 16:17, 18 May 2022 (UTC)

That sounds awesome, you could send it to me on Matrix or via email if you'd like. --Rye Greenwood (talk) 18:49, 18 May 2022 (UTC)

I have send you an email via wiki. But by this way I can only send plain text message, please reply me a email then I can send attachment to you. -- Westgrass (talk) 08:28, 19 May 2022 (UTC)

Thank you and help

Copied from Discord:

@westgrass @Rye Greenwood I am truly amazed at the work you have done with the databases.
I do have a problem, however.
You left Fandom 🤣 🤣 🤣 
Would you please create an administrative guide to wiki maintenance?

Westgrass isn't always good with English, so perhaps you would be more suitable for this task? Ferretwings (talk) 23:36, 9 June 2022 (UTC)

Sure, but "wiki maintenance" is very broad and I'm sure you know a lot about this topic already. Is there something specific that you need help with? --Rye Greenwood (talk) 12:00, 10 June 2022 (UTC)

Wiki database maintenance. Ferretwings (talk) 23:31, 10 June 2022 (UTC)

Editor icons colors

Hey, with your recent ooui changes, the editor icons are hard to read. Thanks for the fix in advance. Hayaku (talk) 15:02, 20 June 2022 (UTC)

Sorry, I missed that part. Should be fixed now; thanks for letting me know. --Rye Greenwood (talk) 19:23, 20 June 2022 (UTC)

Jousting Lance damage formulae

Hey, over at Calamity, we were looking into the Jousting Lances' code to try and understand it, since Calamity adds a new buff to their damage. However, we weren't able to work out how you got the numbers you added to the page for the calculations. Could you explain how you got the numbers that are currently on the page please? Temp35 (talk) 19:05, 13 October 2022 (UTC)

Hi, sure. Near the top of Terraria.Projectile.Damage is the following block:

if (type == 877/*ProjectileID.JoustingLance*/ || type == 879/*ProjectileID.ShadowJoustingLance*/ || type == 878/*ProjectileID.HallowJoustingLance*/)
{
	num = 0.1f + Main.player[owner].velocity.Length() / 7f * 0.9f;
}

So this num depends on the player's velocity. All entities are moved every tick by the amount of pixels specified in their velocity vector, so velocity.Length() represents the player's pixels-per-tick velocity. With 16 pixels being in 1 tile and 60 ticks being in 1 second, the conversion factor from pixels-per-tick to tiles-per-second is [math]\displaystyle{ \frac{16}{60} = 1/\frac{60}{16} = 1/3.75 }[/math].

With this in mind, we can rearrange the formula a bit so that the num is a bit easier to handle ([math]\displaystyle{ v_{\text{ppt}} }[/math] is pixels-per-tick velocity, [math]\displaystyle{ v_{\text{tps}} }[/math] tiles-per-second):

[math]\displaystyle{ \begin{align} \text{num} & = 0.1 + v_{\text{ppt}} / 7 * 0.9 \\ \text{num} & = 0.1 + \frac{v_{\text{tps}}}{3.75} / 7 * 0.9 \\ \text{num} & = 0.1 + v_{\text{tps}} / 26.25 * 0.9 \\ \text{num} & = v_{\text{tps}} * \frac{6}{175} + 0.1 \\ \end{align} }[/math]

This is essentially what I also put in a comment on the page, not sure if you saw that.

num is a factor for the projectile base damage, which can be seen after going down through a damage>0 condition, a loop over all NPCs, three can-hit-the-NPC conditions, and a condition that the projectile is hitting the NPC:

int num5 = (int)((float)damage * num);

num5 gets increased by another factor that is 0 in the default case for Jousting Lances, and is then transferred to the next variable:

int num19 = Main.DamageVar(num5) // simplified

±15% randomization, check. Then a whole bunch of other stuff happens for this weapon and that weapon, none of which is relevant here, until we finally reach:

int num35 = nPC.StrikeNPCNoInteraction(num19); // simplified

This shows that num19 is the final damage applied to the NPC.

And this is how we arrive at the formula that I put on the Jousting Lance page:

[math]\displaystyle{ \text{damage} = \left\lfloor \text{lance damage} * \left( v_{\text{tps}} * \frac{6}{175} + 0.1 \right) \right\rfloor }[/math]

(The flooring is the casting to int when we multiply damage * num.)

With this formula, we can simply enter our lance's listed damage and our tiles-per-second velocity and get the (pre-DamageVar randomization) damage. For instance:

Let's assume that we are a completely blank character with no boosts whatsoever, so that our Jousting Lance is listed at 60 damage, and that we're moving at 20 mph at the time of impact:

[math]\displaystyle{ \begin{align} & \text{lance damage} = 60; \quad v_{\text{tps}} = 14.6666\cdots = 14\frac{2}{3} = \frac{44}{3} \\ & \text{damage} = \left\lfloor 60 * \left( \frac{44}{3} * \frac{6}{175} + 0.1 \right) \right\rfloor \\ & \text{damage} = \left\lfloor 60 * \left( \frac{211}{350} \right) \right\rfloor \\ & \text{damage} = \left\lfloor \frac{1266}{35} \right\rfloor \\ & \text{damage} = 36 \\ \end{align} }[/math]

We would deal 36 damage. Notice how the [math]\displaystyle{ \frac{211}{350} }[/math] (≈0.6) is our num in this case.

Another example for a slightly boosted Shadow Jousting Lance and 50 mph:

[math]\displaystyle{ \begin{align} & \text{lance damage} = 143; \quad v_{\text{tps}} = 36.6666\cdots = 36\frac{2}{3} = \frac{110}{3} \\ & \text{damage} = \left\lfloor 143 * \left( \frac{110}{3} * \frac{6}{175} + 0.1 \right) \right\rfloor \\ & \text{damage} = \left\lfloor 143 * \left( \frac{19}{14} \right) \right\rfloor \\ & \text{damage} = \left\lfloor \frac{2717}{14} \right\rfloor \\ & \text{damage} = 194 \\ \end{align} }[/math]

We would deal 194 damage. Here [math]\displaystyle{ \frac{19}{14} }[/math] (≈1.36) is our num.

Did this clear things up for you or should I clarify or revise something? If you need help with a Calamity formula or with how to display it best on the wiki, just point me to the relevant code. I'd be glad to help.

--Rye Greenwood (talk) 04:17, 14 October 2022 (UTC)

Thanks for the incredibly detailed explanation, that definitely helped clear things up. Temp35 (talk) 13:24, 19 October 2022 (UTC)

About "frogLegJumpBoost" stat in GetEquipInfo

Hi, you removed "frogLegJumpBoost" from statList of GetEquipInfo in this edit, sadly, it made this table (third row) broken. Could you please take a look on it? --Westgrass (talk) 17:26, 17 October 2022 (UTC)

Sure, sorry, I must've forgotten about that table. It's fixed now! --Rye Greenwood (talk) 02:56, 18 October 2022 (UTC)

Critter cages gifs.

Will you please make gifs for remaining critter cages?--Blazerun19 (talk) 13:53, 17 January 2023 (UTC)

Hi, unfortunately this is a considerably time-consuming process and I'm afraid it's not a priority for me at the moment. --Rye Greenwood (talk) 21:42, 19 January 2023 (UTC)

Updated furniture sprite sheets

Several furniture sprite sheets need to be reuploaded to 1.4.4. --Blazerun19 (talk) 23:32, 5 February 2023 (UTC)

Sytling codebase project

As we have discussed, we need a better approach to maintaining Common.css. I've posted my solution, see here. Css code still needs further splitting and cleaning, but I think this should be a good start. Westgrass (talk) 16:22, 4 March 2023 (UTC)

Fantastic, I appreciate it a lot! I'll try it out right away. --Rye Greenwood (talk) 20:05, 4 March 2023 (UTC)

Thanks for your great work on the project! I've fixed a bug with the toolset on pull (about new remote files) and updated the readme (about the edit summary). Hope the toolset is helpful to you. --Westgrass (talk) 02:55, 5 March 2023 (UTC)

Sure, it is. I noticed that my compiled CSS was slightly different from yours, though (e.g. fewer blank lines); I'm going to look into that. --Rye Greenwood (talk) 07:33, 5 March 2023 (UTC)

My SASS is Dart Sass v1.50.0. It is not the latest version. --Westgrass (talk) 07:45, 5 March 2023 (UTC)

I've updated to 1.58.3, and the compiled CSS changed. --Westgrass (talk) 07:54, 5 March 2023 (UTC)

Ah, I see. Version 1.52.2 was relevant: "Preserve location of trailing loud comments (/* ... */) instead of pushing the comment to the next line." --Rye Greenwood (talk) 01:21, 7 March 2023 (UTC)

Hi, So just a question

Hi. i am making a book about terraria and i'm wondering if by some chance the owner of this wiki would want to be a sponsor? if so then at the end i'll have a epilogue and at the end i'll add this wiki. just a wonder because i can't go ask myself because i am on a school laptop so i just wanted to see if they would like me to sponsor them in it. thank you for all your hard work that you do to make this terrarian community better! -Wolf (talk) 11:43, 9 May 2023 (UTC)

Hi, the wiki isn't really "owned" by anybody. The site is hosted by wiki.gg and the game Terraria is trademarked by Re-Logic, but the wiki contents are owned by everybody, in a philosophical sense. As for licensing: All article content is licensed under the Creative Commons Attribution-NonCommercial-ShareAlike 3.0 License – part of the terms of this license is that you're not allowed to use content from the wiki for commercial purposes, so you wouldn't be allowed to sell your book, for instance, if you used wiki material in it. See Terraria Wiki:Copyrights, Terraria Wiki:General disclaimer, and wiki.gg's terms of service for the relevant legal information. --Rye Greenwood (talk) 19:15, 10 May 2023 (UTC)

Ok, I had no clue about it so i just wanted to check. at least i ain't using anything from here for it. and at least that saves me a few more hours. i ain't done one whole page so i guess it'll be fine. besides, it's more my adventure of terraria including pictures of my endgame character, all the recipes i will have crafted, all stadiums that i make, and every boss fight (plus the whole old one's army and such), etc (i could go of for centuries). it'll be about, idk 1000+ pages. i'm getting ahead of myself so let me stop here. sorry for all this writing but anyways yeah, thanks! Wolf (talk) 11:13, 11 May 2023 (UTC)

and really, i do this a lot so yeah, i dont mean to but i don't pay attention either.

Tmodloader 1.4.4

Hey, I just wanted to let you know that tmodloader 1.4.4 stable just recently dropped and I was wondering if you could potentially update the page if its needed. Angrybirdgamer (talk) 21:32, 2 August 2023 (UTC)

Sure, done. Thanks for notifying me! --Rye Greenwood (talk) 22:42, 2 August 2023 (UTC)

Thank you for reverting my edit

Hello!

Thank you for reverting this Special:Diff/886818 edit of mine. I added the comment already and forgot it. That's how it landed there twice in different sections. I am a content moderator in another wiki and check for those errors there too.

So, keep on doing your good work. And thank you for that!

Ffets (talk) 09:11, 28 August 2023 (UTC)

Tables are difficult to read

Hello Rye Greenwood!

I've got my difficulties in reading the recipes tables, because the lines seperating the recipes are missing. It's hard, to spot, which ingredients belong to which result. Would it be possible, to change the table style in a way, that each 2nd row would be given a slightly darker or lighter background color or add seperating lines inbetween rows.

I think, I saw those alternating colors somewhere in a wiki, but can't remember how it was done. In addition, I don't know, where those styles are defined in this wiki and if I would be allowed to change something there.

Ffets (talk) 21:52, 13 September 2023 (UTC)

Hi, I'm not sure I understand what you're referring to. Would you mind pointing me to an example or uploading a screenshot of this issue? --Rye Greenwood (talk) 19:18, 15 September 2023 (UTC)

I think he was taking about zebra striped list. --Westgrass (talk) 14:27, 24 October 2023 (UTC)

Ah, I see, that makes sense. I don't know if that's the best option for our recipe tables though because of the occasional rowspans in the first column.

I did find out what Ffets meant by "the lines seperating the recipes are missing", I think: The recipe tables that are loaded via {{ajax}} in the "Used to craft" sections of crafting station items, like Placed Bottle#Used to craft. The lines are missing because AJAX removes the terraria class from the table. I tweaked the template to allow preventing that; compare Placed Bottle#Used to craft and Alchemy Table#Used to craft. Would this be a sufficient solution?

--Rye Greenwood (talk) 02:42, 26 October 2023 (UTC)

Request help for review

Hi, could you please review contributions of this user? I think his edits does not follow the wiki's writing style and should be reverted, but I'm not quite sure. (I'm not good on English writing, you know) What's your opinion? --Westgrass (talk) 14:27, 24 October 2023 (UTC)

I looked through some of the edits and at a glance it seems like that editor is intent on replacing "to be found" and "to perform" in particular for some reason. I don't really see why... Looks like you dealt with it already though; thanks for asking anyway! --Rye Greenwood (talk) 01:15, 26 October 2023 (UTC)

Localized name in Module:Iteminfo/data

Hello, I'm new administrator of the Russian Wiki. Westgrass recently have made an update in Module:Iteminfo/data which allowed ot make templates like {{ItemNameFromId}} patricianly Lua-based (so now they don't need separate DB and can be invoked directly from modules). I want to implement the same system on the Russian Wiki. Therefore, I've added lname field in the datagen module (now we have 2 DBs for English and Russian item names). The problem comes when I'm trying to generate data: I had been trying to generate everything at once, 1000, and 300 items per one invocation, but it was alway ended up with 5xx server error. Can you help me with generating data? — BotAntony (talk) 04:12, 14 November 2023 (UTC)

I think Module:Iteminfo/data (and its datagen) should keep global and language-independent. Therefore, lname should be retrieved via {{tr|<English item name>}}, or you can implement a {{getItemLname|< English item name / item id >}} template for your language. -Westgrass (talk) 06:13, 14 November 2023 (UTC)

I agree with Westgrass that Module:Iteminfo/data is not the right place for localized item names. Your problem with generating the data comes from not reading the documentation; it's explained right there: "If you want to re-generate the entire database (i.e. all items), then you will need to do so in chunks, as the data generator cannot handle all items at once. Put the following wikicode on a sandbox page and save/preview it: <div style="white-space:pre">{{#invoke:Iteminfo/datagen|gen|0|99}}</div>. Copy the output and replace the respective lines here with it. Repeat with |100|199, then |200|299, and so on, until you reach the greatest item ID (5455). Also feel free to try a larger interval." --Rye Greenwood (talk) 01:07, 15 November 2023 (UTC)

A potential security issue in script for Hair Dyes

A user from Fandom pointed out a security issue in script for Hair Dyes page. {{pc}}, {{gc}}, {{sc}}, and {{cc}} are not protected, any user can edit it to include <script> in their code. Then those js code will execute on Hair Dyes. After researching, I found the result of expandtemplates API was used in $(el).html(textFromApiResult), and the result of this API is wikitext, <script> tags in it will not be escaped. This makes XSS attacks possible. We should use parse API in such situation. Its result is final html code, all risky tags and codes will be escaped. See Special:Diff/896396. This issue can be reproduced by following js code:

new mw.Api().get({
	action: 'expandtemplates',
	prop: 'wikitext',
	text: '{{test}}' // The content of template:test: <script>alert('lol')</script>
}).then(function(apiResult) {
	var templateOutputs = apiResult.expandtemplates.wikitext;
	$('<div>').html(templateOutputs).appendTo($('body'));
});

-- Westgrass (talk) 05:52, 21 November 2023 (UTC)

A good catch! I was not aware of that; thank you for fixing it and letting me know. --Rye Greenwood (talk) 02:14, 24 November 2023 (UTC)

Only4theme template

Hello, this wiki has multiple themes and, unfortunately, not all images can fit them all. F.e. logos of macOS and PlayStation on the main page are barely seen on "Snow" and "Legacy" theme. It can be fixed by adding {{only4theme}} template, but it doesn't work since the wiki mograted to wiki.gg. Can you create SCSS page with the following styles for the template so it could work?

.theme-special {
    .dark {
        @theme Snow {
            display: none;
        }
        @theme Hallowed {
            display: none;
        }
        @theme Legacy {
            display: none;
        }
    }

    .light {
        @theme Underground {
            display: none;
        }
        @theme Overworld {
            display: none;
        }
        @theme Jungle {
            display: none;
        }
        @theme Crimson {
            display: none;
        }
        @theme Corruption {
            display: none;
        }
    }

}

—BotAntony (talk) 00:40, 17 December 2023 (UTC)

The CSS variable --ooui--icon-normal-filter can be used to apply a black filter on light themes and a white filter on dark themes. I made it available via the CSS class blackwhite-icon which you can add to any element (it's also used by {{auto icon}} now). This fixes the near-invisibility of the icons on the main page. What other use cases would there be of an {{only4theme}} template? I don't really see any currently. --Rye Greenwood (talk) 05:49, 1 January 2024 (UTC)

Can you make the pillars each a seperate page.

It gets annoying to scroll to each pillar on a single page. I would appreciate if you made each on its own separate. I suggest copy the contents of the already existing info on them. — Preceding unsigned comment added by Duke sharkron (talk • contribs) at 8:23, 20 December 2023

Version icons and guides in general

Could you showcase how to properly write the version icons? I've seen it in the code, but it's just extremely confusing.

On the wiki style guide page, it is said that the editors should use the encyclopedia style, and, if my memory isn't wronging me, that guides can also be written more loosely with the occasional you. However, most guides that I've seen use you as the main "Ansprache". Should these be changed to the encyclopedic style or kept as they are?

Also on the Ansprachen topic, will we be incinerated if we use one? I do like one quite a lot and I rarely see it here. NationOfKiribati (talk) 14:50, 18 February 2024 (UTC)

Hi, sure. Version icons are displayed via the template "eicons" (short for "exclusive icons"). You need to provide the name of a game entity or a patch name as a parameter like so:

Code	Result
`{{ eicons \| 1.3.0.1 }}`	(Desktop, Console and Mobile versions)
`{{ eicons \| Slimy Saddle }}`	(Desktop, Console, Old-gen console and Mobile versions)

Add | invert = y (y or yes or 1 all work) to invert the icons, i.e. to display the icons of all opposite versions (with respect to the five main versions at the moment):

Code	Result
`{{ eicons \| 1.3.0.1 \| invert = y }}`	(Old-gen console and 3DS versions)
`{{ eicons \| Slimy Saddle \| invert = y }}`	(3DS version)

This is useful for when something changed in a certain patch, e.g. if some weapon's damage was increased from 10 to 20 in 1.3.0.1:

The weapon deals {{eicons|1.3.0.1}} 20 / {{eicons|1.3.0.1|invert=y}} 10 damage. → The weapon deals (Desktop, Console and Mobile versions) 20 / (Old-gen console and 3DS versions) 10 damage.

Or depending on the availability of some entity, e.g. there are 6 souls on platforms that don't have the Soul of Blight and 7 souls on platforms that do have it:

There are {{eicons|Soul of Blight|invert=y}} 6 / {{eicons|Soul of Blight}} 7 different souls. → There are (Desktop, Console and Mobile versions) 6 / (Old-gen console and 3DS versions) 7 different souls.

In some cases, the | not = parameter is relevant. For instance, if the sell value of the Slimy Saddle changed from 2 GC to 1 GC in 1.4.4, then you wouldn't use | invert = y because it would result in the following:

Its sell value is {{eicons|1.4.4}} {{gc|1}} / {{eicons|1.4.4|invert=y}} {{gc|2}}. → Its sell value is (Desktop, Console and Mobile versions) 1 GC / (Old-gen console and 3DS versions) 2 GC.

Here the 3DS icon is displayed even though the Slimy Saddle isn't available on 3DS. The | invert = y parameter blindly inverted the versions of 1.4.4 but that's incorrect, so the | not = parameter is needed for the correct version icons:

Its sell value is {{eicons|1.4.4}} {{gc|1}} / {{eicons|Slimy Saddle|not=1.4.4}} {{gc|2}}. → Its sell value is (Desktop, Console and Mobile versions) 1 GC / (Old-gen console version) 2 GC.

Regarding your other question: That's right, guides can be more informal. Guidespace in general is a bit of a lower priority in my opinion, so I don't think it's as pressing of an issue to remove the second-person writing there as it is in mainspace. That said, if you feel like a guide can benefit from a more encyclopedic style, then go for it! (Do note though that for certain guides it's probably even preferable to directly address the reader, such as the tutorial-like Guide:Getting started.)

"One" is alright; I'm not a huge fan personally (but that doesn't mean I'll incinerate anybody who uses it) and prefer "the player" or the passive voice, but it's certainly better than "you".

--Rye Greenwood (talk) 18:10, 20 February 2024 (UTC)

Search redirects

How do I redirect a search to a page? For example, if I search "witchs broom" it doesn't redirect me to Witch's Broom, and I'd like to make it so that the search "witchs broom" redirects the person to Witch's Broom. NationOfKiribati (talk) 22:10, 20 February 2024 (UTC)

Create the redirect page and type in #REDIRECT [[<the page title you want this page to redirect you to>]] as its content. In this case, create Witchs Broom, content is #REDIRECT [[Witch's Broom]] (I have created it already) BadPiggy1024 (talk) 07:33, 21 February 2024 (UTC)

Unit test for Template:Sell_expr

Hi, could you please made the examples on Template:Sell_expr/doc unit tests? This template was broken, I fixed it but I'm not sure everything is fine yet. --Westgrass (talk) 16:50, 21 February 2024 (UTC)

I'm pretty sure you fully fixed it already! The examples all look correct to me at the moment. --Rye Greenwood (talk) 18:06, 21 February 2024 (UTC)

L10n name for new "Legacy" namespace

Hi, per the discusstion, we are planning to add the new "Legacy" namespace. We need the localization names of this new namespace for other non-English languages. What should its German localized name be? --Westgrass (talk) 09:55, 4 April 2024 (UTC)

Good! The German name should be Alte Plattformen: and for the talkspace Alte Plattformen Diskussion:. If you could also create Alt: as an alias for easier linking etc., that'd be great. --Rye Greenwood (talk) 15:50, 4 April 2024 (UTC)

Suggestion for compare page list gadget

Hello, Rye Greenwood! I found (your) compare page list application in German wiki and copied its on Russian one. Do you still support its? If yes, can you add option to set limits (for max pages which can be compared at once, and offset, like for DPL) to prevent crashes when comparing large amount of pages? Or you have another way to compare pages except checking page history manually? Horn772 (talk) 18:20, 17 April 2024 (UTC)

Oh wow, I haven't touched that beast in quite some time... Not since we moved to wiki.gg, I think. But if it's of use to you, then I'll see what I can do. Can you tell me what exactly the use case is? Do you have a large category with lots of pages, or are you even comparing all pages in mainspace, or...? --Rye Greenwood (talk) 00:55, 19 April 2024 (UTC)

Even categories with less than 100 pages will do crash. We are have the Article Quality template/project and I want to compare 5-stars articles (over 900 pages in the category) with their respective english articles for any changes. Comparing pages which have multiple categories at a time (e.g., which have Enemy NPCs and Forest NPCs categories) may also solve the problem, but its more harder to code and maintain, I guess. Horn772 (talk) 06:58, 19 April 2024 (UTC)

Thanks!

It looks much better now --Sirlance3000 23:03, 18 April 2024 (UTC)

Navigation menu

Search