User talk:JuliaCat

Your edit was a few months ago now, but do you happen to remember how the loot options for the flesh sack are generated? We have ways to call items via their tags, so if it is a tag list we can automate that.

The images are not always the full stack images (the c image) - for example, medicine just uses the a image, and there are some other exceptions. When changing the pages images, make sure you use the correct one.

Ideally, we also don't want to have duplicate files (its harder to maintain, its harder to know which image to use when etc). Its not really an issue if the image name isn't the same as the page, because once the image is set as the page property we can call the image by calling the page image (e.g. with Template: Icon Small or with Template: Q or Template: P). This is better than specifically calling the image because you can just update the infobox and all the images everywhere on the wiki will update too.

That we don't have a colored version of the correct insect meat stack size image is a bit annoying though.

This comes off as an admonition, and its not meant to be, just an FYI for the current standard. You're absolutely killing it lately and its always up for discussion if you disagree or you think I've misunderstood.

Yeah I actually started doing that because iirc I was using some ask formatting template, and to include the icons and everything I think it was becoming too resource intensive, but that was probably due to it being a really long list of items more than anything. But yeah I didn't think of it at the time but just using Icon Small uses less resources comparatively and doesn't come across the issue with page images having different names. It would be nice to figure out how the icons for every item is chosen by the code though without having to go through it manually in-game. Thanks for the info, it's appreciated as always.

I wish I'd thought of it!

Just letting you know, if you want to add new properties to the infobox, you'll have to add the support for them to Template: Infobox main first. It doesn't do it automatically even when a property exists because that causes a lot of issues,

You're more than welcome to edit the infobox template if you feel up to it, or if you'd like to gimme a list I can do it for you.

If you wanna do it yourself, I'd suggest having a think about what heading you'd put it under and whether you want to also support things like grenadier armor and jump packs at the same time. I'd also suggest editing the doc page for the template with an example and then trying to get it to work with the preview. The infobox template is used on a lot of pages, and when it's edited the database often stutters and the wiki momentarily goes down, so if possible try to keep commits to a minimum.

Good to know, and I suppose a few utility items like the smokepop, disruptor flare, firefoam pop, and tox packs could use these properties too.

Just dropping by to say you're absolutely killing it with your edits, let you know that its very appreciated, and to give a much belated welcome to the wiki. I'm one of the moderators around here so please reach out if there are any issues or you need help with anything.

thank you, I appreciate the warm welcome <3. It's a fun hobby of mine to delve into the details and code of a game, and RimWorld certainly isn't lacking in those.

Thank you so much for doing all those light area images. They've been on the backburner for a while but they're really useful for new players. Really appreciate it ❤️