Terraria Wiki
Terraria Wiki
KKeine Bearbeitungszusammenfassung
Zeile 86: Zeile 86:
   
 
: That error is not caused by the name "Vogelscheuche" itself; replacing the entire page content with {{tlc|bestiary}} displays the entry just fine. The problem is that the Lua parser fills up a lot of its memory with handling this enormous number of infoboxes, and then doesn't have enough left for the {{tl|gameText}} (which does need some space itself, too; given it's loading every single string that is used in the game into memory) which the automatic Bestiary entry text generation relies on. For the record, the English wiki is pretty close to the limit on the [[:en:Scarecrow]] page, too – eleven infoboxes are simply not exactly lightweight. Maybe this can be fixed properly sometime, but for now I've entered the Bestiary entry text manually. --[[Benutzer:Rye Greenwood|Rye Greenwood]] ([[Benutzer Diskussion:Rye Greenwood|Diskussion]]) 16:49, 13. Sep. 2020 (UTC)
 
: That error is not caused by the name "Vogelscheuche" itself; replacing the entire page content with {{tlc|bestiary}} displays the entry just fine. The problem is that the Lua parser fills up a lot of its memory with handling this enormous number of infoboxes, and then doesn't have enough left for the {{tl|gameText}} (which does need some space itself, too; given it's loading every single string that is used in the game into memory) which the automatic Bestiary entry text generation relies on. For the record, the English wiki is pretty close to the limit on the [[:en:Scarecrow]] page, too – eleven infoboxes are simply not exactly lightweight. Maybe this can be fixed properly sometime, but for now I've entered the Bestiary entry text manually. --[[Benutzer:Rye Greenwood|Rye Greenwood]] ([[Benutzer Diskussion:Rye Greenwood|Diskussion]]) 16:49, 13. Sep. 2020 (UTC)
  +
  +
:: Ah, that makes sense. Darn, I thought I was close to solving it, too... ;) Thanks for figuring out the problem and updating me on it! [[Benutzer:PuzzledKino|PuzzledKino]] ([[Benutzer Diskussion:PuzzledKino|Diskussion]]) 17:11, 13. Sep. 2020 (UTC)

Version vom 13. September 2020, 17:11 Uhr

Template tweaks

KupferspitzhackeCopper Pickaxe
  • Kupferspitzhacke (Inventargrafik)Kupferspitzhacke (alte Inventargrafik)
Stack digit 1
Eigenschaften
  • Pickaxe mask 35 %
  • Hammer mask 0 %
  • Axe mask 0 %
Typ
Ben.geschw.22 (Schnell)
SeltenheitSeltenheitsstufe: 0
Erwerben5
Verkaufen1

In {{Crafts row}}, the English ingredient name is listed first (| Copper Bar | Kupferbarren | 12).
Would it make more sense to list the German name first? (| Kupferbarren | Copper Bar | 12)
I can change the template if you like.

In {{Item infobox}}, would you rather have Erwerben and Verkaufen on 2 separate lines? I can edit that template to always do that.

Ferretwings (Diskussion) 19:17, 23. Jul. 2018 (UTC)

First of all, thank you for helping out! It is still rather lonely here, haha! (I am just going to answer here as well, for the record :D) Well, generally, yes, German names should appear before the English ones, but changing that now would mean swapping the parameters on every page that uses them... If you know how to swap the two parameters automatically, or ... fast in some way, then that would be great! And about the Erwerben/Verkaufen layout... Actually it does look better in two lines by default, yes. It would be kind of you to change that! Thanks again! --Rye greenwood (Diskussion) 19:36, 23. Jul. 2018 (UTC)

Small typo

Hello! I would like to mention here, because I do not know how to fix this, that on the following page the word "Knochenschlangenbanner" is misspelled a few times. On the page, it is instead spelled "Kochenschlangenbanner." I would fix this myself, but I couldn't figure it out hehe. Just a small typo, hope you don't mind. Thank you! Take care! PuzzledKino (Diskussion) 19:50, 12. Okt. 2019 (UTC)

Hey! Thank you for helping out, I don't mind that at all! Unfortunately, "Kochenschlangenbanner" is how it is spelled in-game, hence I am a bit hesitant to change it. The English wiki does not fix typos either, e.g. on the Daybroken page ("Incenerated by solar rays", as in-game, instead of "Incinerated by solar rays", which would be correct). Once a Banners page is created here, we can create a redirect for the correct term, of course.
Regarding the technical side and how to change things: Large parts of the {{npc infobox}} and {{item infobox}} templates are automated, i.e. in this example, the infobox determines the banner of the enemy by retrieving the NPC ID of the enemy using {{npcinfo}} with the page name ("39"), running that through the NPC ID → banner item ID database ("1627"), turning that into a name with the item ID → name database ("Bone Serpent Banner"), and asking Module:Tr/db for the German translation ("Kochenschlangenbanner"). Therefore, the only way to modify the output is in the last step – altering the translation. The translation database Module:Tr/db is generated from the source code, but it can be overridden by editing Module:Tr/db-custom.
I hope this helps. If it does not or if you disagree with me about sticking to the in-game word, please let me know! And again, thanks for helping! --Rye Greenwood (Diskussion) 01:16, 13. Okt. 2019 (UTC)
Oh! Thank you! I should have foreseen something along those lines. I believe the French wiki, where I have been more active, came to the same conclusion. I definitely agree that yours/theirs is the most practical decision.
I also greatly appreciate your insight on the technical side; it's my weakness! You have been very helpful.
It's nice to help out here. You're all very kind. Thanks again! PuzzledKino (Diskussion) 02:07, 13. Okt. 2019 (UTC)

Sternebewertung

Hallo Rye Greenwood, ich habe ein paar Verbesserungen bei Artikeln gemacht, welche niedrige Sternebewertungen hatten. Dazu zählt der Maxihai und die Muskete. Auch bei anderen Artikeln die ich erstellt habe, wie dem Leichenbestatter, dem Minihai, dem Flammenwerfer und dem Elfenschmelzer hast du noch keine Bewertungen hinzugefügt. Könntest du das vielleicht bitte machen, damit ich weiß, wo ich noch etwas verbessern kann? Vielen Dank

Mischboxx (Diskussion) 13:34, 26. Mai 2020 (UTC)MischBoxx

Natürlich, wird erledigt! Entschuldigung für die lange Funkstille, ich habe deine Nachricht völlig übersehen. Danke für deine Mithilfe! --Rye Greenwood (Diskussion) 16:35, 9. Aug. 2020 (UTC)

art-en

Hey Rye, my goal just now was to add the art-en for Werkbänke (Work Benches), but I must have done something wrong with the translation document. Perhaps I added Werkbänke to the wrong database? In any case, could you point me toward the right page for these additions? Thanks! PuzzledKino (Diskussion) 13:53, 9. Aug. 2020 (UTC)

Hey; you did everything correctly. Only the last step was missing, updating the "real" translation module, Module:Tr/db. This module is where {{tr}} takes its data from, Tr/db-custom is merely an aid for managing custom additions (e.g., it facilitates that an EN→DE entry is automatically added the other way round, DE→EN, as well) and it ensures they don't interfere with the strings from the source code. So yeah, for applying custom additions, Module:Tr/db needs to be updated with the code generated by Template:Tr/luadata. That template page displays the newest version (once it has been purged – "Aktualisieren" in the "Mehr" dropdown) and the text can simply be copied and pasted in Module:Tr/db. The system is quite similar to how Module:Exclusive/data is updated on the EN wiki. I have done that now. Sorry for the inconvenience! --Rye Greenwood (Diskussion) 16:35, 9. Aug. 2020 (UTC)
Thanks Rye! I'm pretty sure I understand it now. I don't pretend to be good at coding (far from it ahaha), but I double check everything I do to try and identify (and then share) any mistakes I make. Thanks for watching over my edits and kindly helping whenever I need a hand :] PuzzledKino (Diskussion) 19:57, 9. Aug. 2020 (UTC)

Neue Seiten

Hey Rye! Thanks for your help on my previous edits. I wanted to ask you something: I've occasionally been making some edits/new pages here under the impression that, even if they're not perfect (and they won't be with my current level of German :p), they will encourage and provide growth of the German wiki. This is especially relevant because it's usually just the two of us here, I think.
If I'm wrong and my edits are causing an inconvenience, please let me know. I only want to help grow this wiki, not slow its growth down or make it harder on anyone. Thanks again :) PuzzledKino (Diskussion) 19:43, 28. Aug. 2020 (UTC)

Your impression is absolutely correct! Your edits do help the growth of the wiki; it's easier for me to improve a page that already exists instead of creating a new page, because I'm regularly overwhelmed by the amount of missing content and can't decide where to start (although it's not as bad as it used to be, haha).
A thing that I myself have forgotten and remembered today: I made {{1.4}} some time ago, for pages that contain hard-coded strings of new 1.4 entities, e.g. Empress of Light, Bestiary, etc. I've decided not to translate these yet, since they're in English in the game as well, and wait for the official translation. So if there is such a term in the source code of a page (e.g. Schneider which has Graveyard in its shop inventory), just put the template at the bottom so that when the localization update comes out, we'll have an overview of pages where those strings need to be replaced. --Rye Greenwood (Diskussion) 21:20, 28. Aug. 2020 (UTC)
That's good to hear! Thanks :) When possible, I will try to keep my edits focused on specific tasks (like the Solar Eclipse enemies for example); that way we can have an even stronger sense of direction. But sometimes I just wander around and fix little things here and there, too. And I had no idea that page existed! I'll try and add the template where needed. PuzzledKino (Diskussion) 21:34, 28. Aug. 2020 (UTC)

Module:Tr/db Protection

After spending more time than I'd like to admit reading our conversation from August and trying to get Sense to appropriately show its art-en, I think I realized why I can't do it: the page Module:Tr/db is protected, so I can't finish the last step by pasting tr/luadata's code into tr/db! Assuming you would prefer that tr/db remains protected, could I ask you to do the honors by finishing this process for me? Thanks Rye! PuzzledKino (Diskussion) 15:09, 4. Sep. 2020 (UTC)

Don't be embarrassed, I totally understand that things can get confusing, haha! I've updated the module and lifted the protection, so feel free to update it yourself whenever necessary. --Rye Greenwood (Diskussion) 15:39, 4. Sep. 2020 (UTC)
You can say that again! Thank you -- next time, I'll get this right! :] PuzzledKino (Diskussion) 15:45, 4. Sep. 2020 (UTC)

Problem with Event-Gegner Box

Hey again! I noticed while creating the page Schlachter that the Event-Gegner Box contains all sorts of errors suddenly (or perhaps a single recurring error). Not sure how or when it happened, but I wanted to let you know. PuzzledKino (Diskussion) 16:58, 4. Sep. 2020 (UTC)

Mhm, I'm aware of that issue, but I wasn't able to figure out the reason yet. It occurs quite unpredictably; sometimes it's there, sometimes it isn't... Properly debugging that "interpreter exited with status 1" also requires digging deeper into the MediaWiki configuration, which us normal editors don't have any access to (only Gamepedia staff, I presume). I've made a small optimization to the module that generates the exclusivity icons, maybe that helps a bit. Other than that, I guess the only "fix" is to remove the navbox? --Rye Greenwood (Diskussion) 23:52, 4. Sep. 2020 (UTC)
Ahhh... well, I'm really at a loss as for what to suggest, but I suppose I could let you know if/when I see the problem again, so that we could perhaps connect it to some sort of activity/type of edit/etc. Not sure how much that'll help, but I'll keep an eye out. Thanks for filling me in! PuzzledKino (Diskussion) 00:32, 5. Sep. 2020 (UTC)
I don't know if this section is the most appropriate but, Rye, why aren't you using all the l10n templates from the English wiki yet? Is it related to all the German pages not being created yet causing an error? I'm just wondering because everything works perfectly on the French wiki (except literally for fr:Liste des PNJs which also has a problem on ZH). --Dinoxel (Diskussion) 01:53, 5. Sep. 2020 (UTC)
Hm, I think I sometimes postpone updating a template here because it would involve changing many pages that it's used on, or maybe because it's still being worked on on EN... and then just forget about it? I'm not sure. If you're referring to the navbox error, though, then I have to admit I'm not too fond of these huge master navboxes in general, and may possibly not have the greatest motivation to update them all to the new /content system (regardless, I doubt that would solve the Lua error). German pages not being created usually doesn't cause any issues, it only leads to some missing content like on Liste der NPCs (or for, well, {{drop infobox}}). Or have I misunderstood you? --Rye Greenwood (Diskussion) 13:50, 5. Sep. 2020 (UTC)
I might have gotten confused watching how DE was working, I noticed a few changes with EN and thought you overwrote a lot of templates and things but it seems that Master templates were just using the 2 years old layout and you automated tr/db. I noticed that template:item and template:eil were still using German inputs, should they use English ones (or both works but one is preferable) ? Also, about the French en:List of NPCs, I was just saying that it was the only page not working on the wiki (as far as I know) but I literally fixed what was wrong a few seconds after sending you this message. I agree with you as well about these templates, they are kind of annoying to update and pretty huge. Do you have a list of things to do on DE that I could take care of, except translate pages obviously? Because It won't bother to update templates on DE aswell. I usually wait until the page is no longer edited for a couple of days before updating both the templates and pages. By the way, do you know which one of this wiki and the fandom one will remain after the merge? --Dinoxel (Diskussion) 04:32, 6. Sep. 2020 (UTC)
I think I've applied a mixed layout to the master navboxes of some sort; both the old rectangles on the left containing the "headings" and the newer {{navbox/start}} wrapper. I considered that a nice layout.
In regard to {{item}} and {{eil}}, I want to maintain support for German inputs, e.g. so that the templates are easier to use for those who play the German version of the game and may not always have the English names in mind. I don't mind whether the templates are used with German or English input in article text, though.
If you'd like to help out, I think updating npc and item infoboxes on existing pages might be a task. You know, where there are new 1.4 stat version differences or old parameters... I don't have an overview over the details and scope there, though, unfortunately.
I don't have any new details on the Fandom merger, so no, I have no idea which one will remain or when or even if the wikis will be merged. I'm hoping that this one remains, of course. The quality of the German Fandom wiki is... often astoundingly lacking.
--Rye Greenwood (Diskussion) 13:03, 13. Sep. 2020 (UTC)

Problem with Vogelscheuche Bestiary entry

Hey Rye! Just pointing out that the Vogelscheuche page has the error „Lua-Fehler: not enough memory“. I have a feeling this is caused by Bestiary/Liste not containing an entry for the default "Vogelscheuche" (only for its variants), but that wasn't enough for me to find a fix nor to explain why a similar problem isn't happening on the English wiki. Oh well. PuzzledKino (Diskussion) 16:52, 6. Sep. 2020 (UTC)

That error is not caused by the name "Vogelscheuche" itself; replacing the entire page content with {{bestiary}} displays the entry just fine. The problem is that the Lua parser fills up a lot of its memory with handling this enormous number of infoboxes, and then doesn't have enough left for the {{gameText}} (which does need some space itself, too; given it's loading every single string that is used in the game into memory) which the automatic Bestiary entry text generation relies on. For the record, the English wiki is pretty close to the limit on the en:Scarecrow page, too – eleven infoboxes are simply not exactly lightweight. Maybe this can be fixed properly sometime, but for now I've entered the Bestiary entry text manually. --Rye Greenwood (Diskussion) 16:49, 13. Sep. 2020 (UTC)
Ah, that makes sense. Darn, I thought I was close to solving it, too... ;) Thanks for figuring out the problem and updating me on it! PuzzledKino (Diskussion) 17:11, 13. Sep. 2020 (UTC)