Is that something that can be arranged on this wiki? I no longer go by maple on most sites, so I'm wondering if there is a request form or anything of the sort here.
User talk:Harakoni
Jump to navigation
Jump to search
Reply to "Regarding possible username changes"
Reply to "Stone blocks pages rewrite"
Reply to "A question"
Reply to "RimWorld Chinese Wiki team need helpš¢"
Reply to "A small question"
Reply to "A question"
Reply to ""Paintable" boolean property"
Reply to "Re: #ask lists"
Reply to "Thanks for the user page!"
Sorry, to my knowledge there's no way to change the name of an account.
This is unfortunately not currently possible due to the version of MediaWiki we're currently using. As someone's online handle has changed (a few times already), it is something I'd like to accommodate, but it does come with some teething issues to make sure that updating the version of MediaWiki doesn't break any of the essential plugins (e.g. stuff like Semantic MediaWiki)
It will be possible once we're on MediaWiki 1.40+, but I don't have any kind of timeframe on when that might be. Sorry.
Do we have any objection to them just making a new account as a substitute in the meantime, User:Zesty? It'll lose the edit history but as long as its not abused (i.e. only do it once, don't use both accounts to sock puppet, be open about your old and new account) I don't see a particular issue.
Yup, making alt / new accounts is fine and is a fine solution.
In my opinion, there's no need to block any of the accounts though. The community is small and I really doubt anyone is going to around sockpuppeting.
Once its done, we can block the old account to orevent abuse and explain the transition in the block reasons.
Sorry for the extremely late response, I've just been procrastinating on it cause of the mediawiki thing, new account is User:ItsKairoKay, wouldn't mind the sandbox being moved over to it.
Hey! Thanks for approving my work and your great changes. Particularly, I remember thinking about the lower rest effectiveness right after posting, but got busy and didn't go back to add it, so I was glad to see you had.
I was going to go in and rewrite the pages for the other four stone block types once the slate blocks page was approved (Slate was a "proof-of-concept", if you will) but I saw you had made similar changes to Granite blocks as well. Are you working on any more right now? Don't want to step on your toes or start on something you're in the middle of.
Also, while I can mostly understand why you made the changes you did, and will try to stay consistent with them in my future edits, can I ask why you got rid of the "Info" template? As far as I could tell, that was so that the stone blocks "List" template (e.g. on the stone blocks page) would pick these up and display quick comparisons. Is that a feature we're trying to phase out, or something?
I did granite just because it was largely already up to the standard you had set with slate and it was a quick task. Absolutely happy for you to update the others, including any subsequent changes you think are needed to slate and granite. You did an excellent job with slate and the template and this is a collaborative process not a hierarchical one.
RE: Info/List. Essentially yes. Info is a holdover from an earlier much less comprehensive time of the wiki where it made sense to put detail in the intro, but it's too inflexible for all the different types of pages the wiki has now and it requires the duplication of info. It was also inconsistently used even at its peak. It is being slowly phased out but its a low priority so no real action is being taken besides removing it when we come across it.
Also I was going to say welcome to the wiki but what I should be saying is welcome back! Looks like your last edit before this lot are from before I even joined on.
Glad to have you return, please feel free to hmu if you have any issues, questions, or anything. I'm also about to automoderate you so no more waiting around for mods to approve edits.
Thanks for the welcome (back) and the automoderateĀ :) I just looked at my edit history and I guess I've contributed more than even I remembered :D makes sense though; I've always loved RimWorld and always find myself coming back eventually.
And thanks for the explanations! Collaborative over hierarchical is a great way of putting it. Nevertheless standards are a great thing, so I stick to them when they exist (can you tell my day job is a software developer haha)
By reviewing the game's XML file, I found that on the "Injury Healing Factor" page, it only mentions that the healing speed of the Nociosphere is 0%. In fact, the same applies to the FleshmassNucleus. Additionally, I would like to know if the healing speed for Mechanoid is 0%? Or is it the default 100% but the Mechanoid cannot self heal?
Hello, I am writing on behalf of the RimWorld Chinese Wiki team. We would like to inquire about an efficient method to extract and organize game data for populating our wiki's infoboxes.
Currently, due to the limited number of active contributors, updating these sections has become quite challenging. However, we still aim to provide players with comprehensive and detailed content. If you could kindly share any advice or tools that might streamline this process, we would be immensely grateful.
Thank you sincerely for your time and assistance!
Really grateful if could helpšš
I forgot to log in to my account last night. If possible, you can reply under this comment
While editors have made tools to automate the extraction of data before, the majority of it is just taken manually from the .xmls. They're largely human readable (though they are in English) so copying data over that way is typically less work than developing bespoke tools. We had the advantage of being able to grow with the game though - if we were to have to do it all again now, maybe automation would be more viable.
The real trick is making sure that the data is accessible such that you can update one page and have all the other pages update automatically and you can build templates that can extrapolate from it. This wiki uses semantic media wiki and the properties to do that. Template: Infobox main sets most of the properties the wiki uses. For example: here are the properties for a flak vest. And I can ask the wiki to tell me that. So I can use {{Q|Flak vest|Market Value Base}} to say the market value is 225 silver and that number will update whenever the page is updated. The same basic premise lets us do things like the Template:Apparel Stats Table where we take the values from the page properties and do math to find the outcome.
It also has a nice feedback loop where you can tell the wiki to print the details of every item in a class and you can easily spot missing entries.
Sorry if that is not particularly helpful for your case.
Thank you for your thoughtful response - the insights you've provided have genuinely helped advance our understanding of the matter. If it's not too much to ask, would you consider sharing a contact method for professional communication platforms like Discord? This would allow us to consult you more conveniently should any follow-up questions arise. Please understand this is merely a respectful inquiry, and we completely respect your boundaries if this request isn't appropriate. Your guidance would be sincerely appreciated regardless.
Please note this message was translated by AI. Apologies in advance if any phrasing comes across as impolite! š
Hello,may I ask a question about the "Empire/Pawns"page? I don't know the content in "color guide",what does it do in the game? (sorry my English is not so good)
I honestly don't know. You might need to ask User: JuliaCat
Hi, I want to ask a question in "Raider".
What does the "HP" mean in the "Gear" blank?
Sorry that my English is not good enough to understand.Ā :(
Is that the durability of the gear?
If so, why it can exceed 100%?
Yes it is, and it can exceed 100% because it allows the developers to skew the result when selecting a value randomly in that range because if it selects a value above 100% it defaults to 100%.
So for example, if the range is 90% - 190% then approximately 90% of the time the item would have 100% durability but 10% of the time it would have less.
While if you had 90% - 100% only 10% of items would have 100% durability and 90% of the items would have less.
I understand, thank you for your answer:D
Please let me know if that is unclear.
Also, if possible, I would like to ask how many active editors are currently on the wiki?
That depends on how you define active. There's always people around, but there's ebbs and flows of activity. Some people do a few edits a month forever, others do 100 edits in their first month and then never again, some people do bursts every once in a while.
That likely refers to individuals who have been actively engaged in editing recently, with the emphasis being on their participation frequency rather than the quantity of content edited. :D
There is a question about the "reading speed" page.It seems that there is an error in the data table, which should start at 80%?
Ahh i see. Would you mind adding the {{recode}} template to the page with a description of the issue?
That's ok. Iāve added the information, though itās currently undergoing review.
Hi Harakoni,
Is there a reason why the "paintable" boolean property is not visible by default in the info boxes? I've noticed that in several pages, the property & value is provided (e.g. in Toy box), but it is not displayed currently.
Hello Daylong698
Not Harakoni, but the reason is that "Template:Infobox main" was not updated to use that value. It should have a section added along the lines of:
{ {#if: { { {paintable|}} } | { {#if: { {#var:setProperty}} | { {#set:Paintable= { { {paintable|}}} }} }}
;Paintable
:{ {ucfirst:{ { {placeable|} } } } }
}}
Changing that template always leaves the wiki temporally unavailable, which is why is not updated very often.
PD: I wrote the above before submitting the change, but it was never sent. Ups.
Nice. Always great to see an issue reported and already fixed. Implementation looks good and its working on the pages.
Thanks a lot, Arcangelus!
I might need to reopen this topic. I was editing the Spacedrone page, and noticed that although I wrote "False" in the wiki, the infobox displays "True" as the value of "paintable" nevertheless. In the Crashed_shuttle page, it is also paintable=false, however, the infobox displays nothing. I've tried to change the boolean value to capital "F", but it does not display differently. At the same time, in the Property:Paintable page, the values are displayed correctly, therefore I assume that there might be something happening with the infobox displaying the value.
Ah I see the issue. It was setting the property correctly but it was displaying "placeable" instead of "paintable". Fixed.
Thanks, looks good now
Thanks for bringing this functionality to my attention - I'll implement it into the (Chaos) Skip pages, and Mass Chaos Skip, when I get around to it. I can't think of any other information off the top of my head on any of the current psycast pages that would benefit from being collated in a similar manner - if you see something, let me know. Once I'm done with all the remaining psycast pages, I'll go back and take another pass at them. Speaking of which, if there are any other methods (either in the same vein as the #ask function or simply editing process) to improve formatting on my pages, let me know - I'm satisfied with the substance of information I've provided, but I'm not happy with the formatting - it's essentially just paragraphs, and not particularly adept at presenting the information in a concise, easily digestible manner. This is partly due to psycasts being fairly freeform in terms of their usage, but the point stands regardless.
While keeping the standard sections of Acquisition/Summary/Analysis is a good practice, you might want to use subsection a bit more to break up the text and make it easier to skim or find specific sections. Analyses that have a paragraph focusing on specific strategies separately to the more general analysis more generally are good candidates.
You also generally want to bring the readers eye to the important info or what they're likely on the page to find. Thats why we implemented the color templates (Good, Bad, Up, Down etc) but its also why things like the drug pages list the effects in bullet points - they draw the eye on pages that are otherwise quite long and involved.
In terms of general skills, i think editors really benefit from knowing the very basics of how #asks and {{Q}} and {{P}} work and the parser functions because you can do things as simple as putting values in text to the big complicated mathematical templates like {{True Melee DPS Calculator}}
Overall, the pages you've worked on are high quality though, and while page can always be improved at a certain point there will be diminishing returns and it can be more beneficial to refocus on other pages.
That said, do what you feel motivated to do. Someone sticking around long term only working on their niche interest >>>> someone working on "the most needed pages" and getting burnt out - the work is better, more work gets done total, and most importantly its a better experience for everyone involved.
Just wanted to show my appreciation for creating a user page for me and the (rather witty) recognition you added, it means a lot. Cheers!
Hi Harakoni,
(I'm not sure whether this is the best place for error reporting, if not, please direct me to a better location and I'll do it there in the future).
In Floors / Comparison table / Flesh / Filth Multiplier cell, there is an error "Expression error: Missing operand for *.%".
Thanks for fixing and also for the info!