User talk:Jimyoda

From RimWorld Wiki
Jump to: navigation, search

Contents

Thread titleRepliesLast modified
Want some help?201:01, 8 January 2017
Trees013:14, 6 November 2016
bad hunting223:53, 6 October 2016
Fancy charts and graphs and stuff502:19, 3 September 2016
Title case vs sentence case023:37, 2 September 2016
Title case vs sentence case413:48, 31 August 2016
Typos102:00, 2 August 2016
Whitespace in Template:VersionFrame419:20, 24 July 2016
Template Transclusion323:35, 19 July 2016
Labeled section extension103:19, 23 October 2015
New Features416:00, 7 September 2015
Ideas503:29, 22 June 2015
Joy Objects302:40, 19 June 2015

Want some help?

Do you want some help removing the TNTN?

Skywardhigh (talk)00:55, 8 January 2017

Actually just about done, actually. Thanks though. There will still be pages that link to it, like pages ending with /en, but those are essentially obsolete, so no use changing those.

Jimyoda (talk)01:00, 8 January 2017

Alright, just thought I'd ask

Skywardhigh (talk)01:01, 8 January 2017
 
 

Saw you tagged the Trees page for rewrite.

In the spirit of D for Dwarf, I say tag it C for Cannibal and call it done.

Mehni (talk)13:14, 6 November 2016

bad hunting

you added that bad weather will have a negative effect on hunting.

is there realy a bad weather shooting debuf? i thaught that it was the lower light level that caused the shooting debuf.

PieTau (talk)20:01, 6 October 2016

IIRC the list, that pops up on hovering on the target, includes a separate entry for weather, so that's in addition to low light level. This was from an old note I wrote / memory, so I'll confirm when I get a chance to run the game. I need to check for fog too.

Jimyoda (talk)21:35, 6 October 2016

Confirmed that weather is listed as a factor in the 'shot by' popup. Daylight is not affected by weather. During the day, light can stay at 100% even when it's raining. I'll make an update with exact details.

Jimyoda (talk)23:53, 6 October 2016
 
 

Fancy charts and graphs and stuff

I wanted to start working on adding information for the various drugs added to the game, but I don't know how to make all the fancy diagrams and charts and shit like you see in Beer, Clothing, Food, etc. I also couldn't find any source of information. Is there anywhere I can go to read up on how all this works?

Maoman (talk)08:39, 2 September 2016

I'll give some examples on how to do this.

Jimyoda (talk)14:16, 2 September 2016

Those colorful tables use the STDT (Standard Design Design Template) template.
{| {{STDT| wikitable c03}}
table code
|}


It's open to use whatever color you think looks best, but I generally avoid colors used for other type of items. I found that the colors below aren't used by anything else. (These tables look horrible on gray background, but will be fine on white.)
Refer to Templates for color codes.

Example[edit]

Drug info
Addictiveness 6.5%
Market value $80.00
Hit points 50
Work to make 10

Code
{| {{STDT| c_19}}
|-
!colspan="2" scope="col" style="text-align: left" | Drug info
|-
|Addictiveness || 6.5%
|-
|Market value || $80.00
|-
|Hit points || 50
|-
|Work to make || 10
|}

I'll work on a new drug template (similar to ones like Template:Medicine or Template:Raw_food) and adding parameters for drugs into the 'infobox main' template. That way each drug's page can have it's own nice infobox. And the Drugs page can list all the drugs with very little code, like it's done on Materials.

Drugs Summary[edit]

You can add a summary table at the bottom of the page.

Name Addictiveness (%) Market value Hit points Work to make
Go-juice 6.5% $80.00 50 10
Luciferium 100% $100.00 50 N/A

Code
{| class="sortable c_18 text-center table"
! Name !! Addictiveness (%) !! Market value !! Hit points !! Work to make
|- style="center-text"
| style="text-align: left;" | Go-juice|| 6.5% || style="text-align: center;" | $80.00 || 50 || 10
|-
| style="text-align: left;" | Luciferium || 100% || $100.00 || 50 || N/A
|}

Jimyoda (talk)16:16, 2 September 2016

That's really helpful, thanks. Would you mind explaining (or pointing me to an explanation of) how the templates work? I looked at the code in the two templates you linked but don't understand what it means. How do you make it, change it, and use it?

Maoman (talk)23:35, 2 September 2016

This will explain it all:
https://www.mediawiki.org/wiki/Help:Tables

In the first table (Example) I used STDT but it doesn't let you customize it much with text alignment and such.

The second table (Drugs Summary) I just used a straight up table that allows text alignment.

Jimyoda (talk)23:52, 2 September 2016

Oh perfect, that's exactly what I hoped existed somewhere. I could only find wikipedia and wikia stuff though, never mediawiki.

Maoman (talk)02:19, 3 September 2016
 
 
 
 
 

Title case vs sentence case

Ignore this, I double posted by accident.

You say articles should use sentence case, but almost every single weapon uses title case... Short Bow, Pump Shotgun, Heavy Charge Blaster, etc. I'm not trying to argue, just want to know for sure one way or the other - consistency is important in wikis.

Maoman (talk)05:27, 29 August 2016

Title case vs sentence case

You say articles should use sentence case, but almost every single weapon uses title case... Short Bow, Pump Shotgun, Heavy Charge Blaster, etc. I'm not trying to argue, just want to know for sure one way or the other - consistency is important in wikis.

Maoman (talk)05:27, 29 August 2016

Aw crap, I double posted. :/

Maoman (talk)05:28, 29 August 2016
 

Sentence case appears to be the de facto standard. The majority of pages here use Sentence case. Several that used Title Case were renamed to use Sentence case, but there are those that were never changed, especially the weapons. So, the weapons pages should actually get renamed to use Sentence case. Although the priority may be to get Zesty to approve a page that outlines such standards.

Using Sentence case makes linking pages easy and clean. Whereas using Title Case complicates things, as shown here:

A link written in Title Case, [[Pump Shotgun]], naturally shows inline as Title Case. Output: Pump Shotgun
But to follow standard English rules, we should capitalize proper nouns, not common nouns.

To fix it we have to create the link as [[Pump Shotgun|pump shotgun]]. Output: pump shotgun


But when we use Sentence case we can simply write [[dining chair]].

A [[dining chair]] is more comfortable than a stool.
Output: A dining chair is more comfortable than a stool.

You can still capitalize as needed:

[[Dining chair]]s can be made of metal or wood.
Output: Dining chairs can be made of metal or wood.

Jimyoda (talk)16:05, 30 August 2016

"To fix it we have to create the link as [[Pump Shotgun|pump shotgun]]."

But simply typing [[pump shotgun]] seems to work: pump shotgun. Or am I missing something?

Maoman (talk)09:06, 31 August 2016

Oh, that was a bad example. The pages Pump shotgun and Pump Shotgun both exist, so neither show as redlinks. The former redirects to the latter. But to follow the standard style, Pump Shotgun should redirect to Pump shotgun. And eventually, pages that use Title Case should be deleted after all links to them have been corrected.

Jimyoda (talk)13:48, 31 August 2016
 
 
 

Just wanted to say thanks for catching my typos! :>

Theaetetus (talk)20:46, 1 August 2016

Sure, no problem. Noticed one then figured it was a copy-paste oversight - easy to miss.

Jimyoda (talk)02:00, 2 August 2016
 

Whitespace in Template:VersionFrame

Hey, would you mind taking a look/stab at Template:VersionFrame? It's adding whitespace, which is more obvious on Version history than on the individual pages.

Not quite sure where it's coming from. :\

Theaetetus (talk)10:43, 23 July 2016

OKay, I started taking a look at it.

Jimyoda (talk)13:45, 23 July 2016

I'm running out of time to check further, but my first suspect is the hotfix and bugfix parameters. When specified, it seems there's no extra whitespace. When omitted because they're not needed, the template might be putting something there anyway. Again, I'm not certain and have to step away until I can look into it later. There are IF statements that should prevent that, but I'm going to follow into it anyway.

Jimyoda (talk)14:49, 23 July 2016

My thoughts exactly. I tried adding comments around the if statement newlines, just in case, but it didn't seem to do anything.

Theaetetus (talk)15:19, 23 July 2016

After some experimenting I had some success.
There are at least three methods to eliminate the extra line breaks.
1 - Remove all the carriage returns within the code itself. It's effective, but not very readable or easily edited when you have a series of IF statements in a single (window-wrapping) train. So not a good solution.
2 - Consolidate the each section's pair of IF statements into one, thereby reducing the amount of natural carriage returns. That might have worked, but I didn't try.
3 - In each IF statement replace the 'value if empty' parameter with an actual null surrounded by single quotes. I saw that if you put ANY text, there was no line break. However, we don't want anything to show. The nbsp code to create a space works, but a null is even better.

I used option 3. It was very simple to implement and very effective.

Jimyoda (talk)19:20, 24 July 2016
 
 
 
 

Template Transclusion

Hey, noticed you'd talked at one point about the ability to transclude infobox parameters into tables so we didn't have to keep updating everything in two places.

Did you ever figure out a good method to do this? I've been reading over MediaWiki tutorials and the only way I can think to do it would be to make a /params page and then transclude the params into both the infobox and any tables. Not sure if that'd even work, tbh, but then it'd make it harder for casual contributors to add.

Figured I'd ask if you'd found a better solution.

Theaetetus (talk)16:23, 19 July 2016

If I understand you correctly, I've already done it. Rather than using transclusion, I've learned how to use MediaWiki's commands to work with data. Data is stored with the set command and displayed or queried with the show or ask commands, pretty much like variables in programming. When you make a table you can construct each line to display the data using the show command. That's nice, but tables still end up getting very big, repetitive, and hard to manage and edit. The elegant solution is to use a template to construct each line and display the data.

Look at Animals#Animals_List. Look at the code and you'll see no data is actually specified there. Each table line is produced using the template, Animals/Row. The data was populated within each animal's page which called Infobox main which stored the data.

Other pages, like Plants, (done by someone other than me) do a very similar thing. It's done to another level by using a 'list' command, however that page is often broken. In fact, right now it's not showing anything.

Admittedly, having pages call templates which call other templates does confuse some people trying to make certain updates, but I'm just applying MediaWiki's power and purpose, and wiki templates, and I'm willing to help anyone willing to learn it.

Let me know if you need help with anything.

Jimyoda (talk)17:41, 19 July 2016

Yeah, I noticed that. I'm not 100% on how the behind-the-scenes magic is working, but when on the edit page for an animal, I'm seeing the set variable values below the Submit/Preview buttons. Did you have to do anything special to get it there, or is it just showing all set params?

Theaetetus (talk)17:56, 19 July 2016

Nothing extra need be done, you just specify the variable names and values as usual. MediaWiki calls them page properties. Most properties are set by whatever value a person typed into the page. But certain properties can be, and are, determined by other properties. For example, within Infobox main, an animal's training abilities are determined automatically based on intelligence and body size. It seems that's how the game does it too. But what you see is not a list of all possible parameters. If a parameter is not set to a value within the page, then that property does not exist for that page.

You can also view the properties for any almost page - on the left under Tools, click Browse Properties. (Pages for game objects will have many properties. Pages that are just informational usually only have properties of Categories and Modification date.)

One thing to note is that properties are stored in a database. If you're ever working on a page and a property or something isn't actually showing up to date (especially when that data is shown on another page's table), look for a drop-down arrow just left of the search box. Click the drop down, click Refresh, and that will force an update into the database of changes on that page.

Hope that answered your question and was helpful.

Jimyoda (talk)23:35, 19 July 2016
 
 
 

Labeled section extension

Hello Jimyoda,

I'm not sure if you are the person to talk to about this, however I've been doing a fair amount of work cleaning up the plants section and I think it has been going fairly well. I'm still adding content etc. and I would be happy to get any comments you might have on the section. I'm working on creating tables that can draw content for each row directly from the relevant page. This is proving problematic as there does not appear to be a critical extension for doing this sort of work installed on the wiki. Can be found here: https://www.mediawiki.org/wiki/Extension:Labeled_Section_Transclusion is it possible to get this installed on the wiki so I can start working on this??

Also, I was wondering if it is possible to make hyperlinks appear white in the infobox CSS class. Currently if I try to turn the header into a hyperlink the link is very hard to see on the dark background. I think this would be very good functionality to have if infoboxes are transcluded onto different pages.

Cheers,

Armagin

Armagin (talk)18:50, 22 October 2015

If I understand correctly about the table you want to make, I've done it with Animals#Animals_List already, so I can certainly help with that. It's done by transcluding a template instead of transcluding sections. I'm not an admin, just an editor, so if you still want to request the extension, talk to Zesty. Ask him about making changes to the CSS class as well.

I really like the new layout of the plant infoboxes. The horizontal lines are a nice touch. The font in the header is a bit big though. I would try to be consistent with other infoboxes. Most infoboxes use Template:Infobox/Thing. The header for that is Template:Entry/Top. I'm not sure what exactly specifies the font/size but it should be in there.

When viewing on a smartphone I found that long information text can flow between the two infoboxes. It doesn't usually happen, but to see it on a PC go to Strawberry Plant and make the browser very narrow. Simply putting the information text after the infoboxes fixes it. By the way, can and should the two infoboxes be one infobox?

Another thing about the header is maybe try a color besides gray. Maybe some shade of green, for plants?

One key thing I found is to take full advantage of the Properties feature of Wikimedia. Once the data is entered, you can display it however you want. It's what you'd need to make that table. Actually that data was already being defined by the Define|Plant template in the previous versions of the plant and tree pages. That Define template is the very heart of setting properties. Well, I'll start looking into it and write up another message.

Jimyoda (talk)03:19, 23 October 2015
 

New Features

Hey Jimyoda, I am adding in a couple of categories from my post in the forums on all of the animals. Is this okay? How do I gain access to do so?

Louisthebadassrimworlder (talk)13:50, 6 September 2015

Sure, have at it. The animal pages are indeed lacking reproduction and life stages info. Once a stat is listed on a page, the infobox template needs to be updated before it will display. But I will update the infobox template so that infoboxes display the data you added.

Jimyoda (talk)15:40, 6 September 2015

Thanks Jim! I have already done so on alpacas, but it doesn't show :(

Louisthebadassrimworlder (talk)17:10, 6 September 2015

I updated the template so that the stats are showing now, plus I added market value. You're never required to list a stat but if you use these, they must be written exactly as follows:
|offspring =
|maturityage =
|marketvalue =

I've added these stats for a few animals so far.

Jimyoda (talk)05:11, 7 September 2015

Thanks bud!

Louisthebadassrimworlder (talk)16:00, 7 September 2015
 
 
 
 

I have an idea for a single or series of pages that detail how the diplomatic systems work. This could be how you can improve relates with the various fractions in a new world other than by giving them silver, and detailing what happens in fraction related event, such as how the fraction's relation with you determine what event they might trigger and what they do in the case of meeting one of their enemies in an event. I may not be able to set up everything on my own, but I should be able to get the general outline of what should be present on the page or pages I create.

I look forward to hearing your opinion of this idea.

Caleb B. (talk)11:11, 19 June 2015

That sounds really good. There is a real lack of info about what things raise or lower faction relations. After making up a list of everything that has an impact on relations I'd see if it's a big enough topic to stand on its own and have its own page. If not, I'd probably just add it directly under the Factions heading here Overview#Factions. If I could only come up with a few things I would let it live there. But if got lengthy I would create new page instead, Factions, and include everything relevant to faction relations there. Some things that impact relations are related to other topics, like prisoners, visitors, surgery, etc. I would identify those pages and mention the info and/or add a link to where the relations info is. For example, when visitors get injured in your crossfire they blame you and (I think) hurts your relations. So I'd go to People#Visitors, mention it there, and add a link to the other page that talks about relations.

Sometimes when drafting alot of new text I do it in a local document, or on Google Docs.

Another you can do is go to your own page and use it to draft up stuff and use it as a sandbox. That's very useful to play with queries where the displayed results are only visible after you click Save Page.

Anyway, it'd be great to see what you come up with.

Jimyoda (talk)15:55, 19 June 2015

So, I have a sort-of rough draft of what I might put on the wiki, but I don't know if the fraction events and fraction relations should be on the same page. This is really just a thing of, I don't know if their is a limitation to the size of a page or if these two topics should be considered separate. As of this reply, I only have the relations part basically finished, but I have all the information I might need to type up the page or part of a page on the events. I hope you can share your opinion on this matter.

Caleb B. (talk)18:23, 19 June 2015

Do what you think is best. Start with whatever you have the most material for and post the page. Don't worry about length, there's no page length limitation. You can create headings in the page to organize separate aspects of that topic, but if you feel the information doesn't fit well and needs its own page, then go for it. Again, do what seems best, you can always change it.

Jimyoda (talk)02:15, 20 June 2015

Ok, so I believe that I made it look at least somewhat decent. If you care to have a look at it, here you go. Thanks for your assistance and opinions on getting this page up.

Caleb B. (talk)12:51, 20 June 2015

Glad to help. Good to see you got the page up.

Jimyoda (talk)03:29, 22 June 2015
 
 
 
 
 

Joy Objects

Hey there. I took the liberty of "making" the pages for each of the three Joy based objects using only the information you added to the subsections of the Joy page. If you have any problems with this, feel free to say so and I shall make my own information and incorporate that which you have done.


Thanks,

Caleb B. (talk)00:39, 20 May 2015

No worry, that's actually a good idea. I think that anything that can be built or picked up should have its own page. I'll probably set up the Joy page to transclude the text from the individual pages. Transclusion allows text from one page to show up on another page, so when you edit the source page those changes show up in the target page. Anyway, feel free if not bold to make changes and additions.

Jimyoda (talk)02:05, 20 May 2015

Thanks for the information. And on a little side note, while just glancing over your sandbox, I noticed that the chart you have for the textiles didn't have working links because the page "Textile" does not exist while the page "Textiles" does. Don't know if you saw this or not, but there you go.


Thanks again,

Caleb B. (talk)20:08, 20 May 2015
Edited by another user.
Last edit: 02:40, 19 June 2015

The sandbox is just a scratchpad to play around in, so anything in there doesn't really matter. Granted there are references to categories that don't exist, but they're just categories - they don't really do much.

(Help) CatPerson here. I don't know how to reply to your messages (I'm a noob at this). It says that I don't have persmission to create pages. What do I do?

Jimyoda (talk)18:02, 21 May 2015