Messages

[Updated to 3.11.0]

Updated to 3.11.0

The update for Rimworld 1.3 is live.
Changes include drafted hunting immunity for tame-designated animals and a few translation updates.

Could you add a setting to make finish off only cut neck and not brain? I'm using HOPM and it's a bitch having to shoot pawns in the legs until they die.

I don't want to mess with that, to be honest.

Hello, I hope I have not left anything. Spanish localization update:

Merged, thank you.
Next time please provide the changes in the form of files or a pull request, as they are easier to handle.

[Updated to 9.0.0]

Updated to 9.0.0

Hey folks!
With Rimworld 1.3 being just around the corner, here's the matching HugsLib update.
Notable changes:

• Log publisher should now work properly on Linux.
• Publisher now has "logfile" command line argument support. E.g. "RimWorldWin64.exe logfile=c:/log.txt".
• Mod Settings window now immediately updates when changing a SettingHandle value from code.
• Log publisher network timeout extended to 90 seconds.

There are a few minor breaking changes, refer to this wiki page for a full list:
HugsLib 9.0 for Rimworld 1.3 API Changes
Take care, and as always, let me know if you find any issues.

[Updated to 3.10.1]

Updated to 3.10.1

Quick fix for a compatibility issue with Prepare Carefully.

[Updated to 3.10.0]

Updated to 3.10.0

This release was originally just a few fixes, but I got carried away as usual and added a bunch of new stuff. I regret nothing!

- The "Allow" button that appears when things are selected has been improved. Now you can right-click it to pick up the allow or forbid selection tool, and right-click it for the context actions of those tools. Which tool you get depends on the state of the button. Also, the button now supports the classic allow and forbid icons if you have those enabled in the mod options.
- New tool right-click menu actions have been added: "Allow/Forbid visible things" and "Select similar in home area".
- Many have asked for special handling of the Anima tree, so here it is: the "Cut", "Chop" and "Harvest fully grown" tools will now ignore it, unless you select it and issue the chop command specifically. This applies to both dragging and right-click commands.
- Some loading tips with common Allow Tool knowledge have been added.
- Performance of the mod has been greatly improved. The bulk of the problem was caused by how urgent hauling jobs were issued, but designation cleanup and the "No storage" alert were also involved. So, if you disabled the alert for performance reasons, you can turn it back on- it now only costs a small fraction compared to what it used to.
- A roundup of fixes:
  - The startup error that has been reported by many has been fixed. Thanks to lbmaian for submitting a quality fix, and tending the topic while I was away.
  - Colony guests taking urgent hauling and finish off jobs has been fixed. Thanks to InsanityPrelude and Jiopaba for submitting the solution.
  - Auto-unforbid prey when drafted haunting with ranged weapons is now working properly.

Minor bug, selecting 2 or more items changes the text size in the reroll window.

That's super weird. I did confirm it on my end though, so thank you for the report.
I'll see about including a fix the next time I'm updating.

https://hatebin.com/rnqqryvryv

Got what I needed from that log. Cheers.

In the log it says: warn couldn't find drop spot.

Yeah, had this happen a few times, too. It's a bit tricky to reproduce.
The error is caused by a method in the base game that makes a limited number of random attempts. I suppose I could replace it with one of my own that is guaranteed to succeed.
If it happens again, do post your log, or just the trace of the error- it'll help me track down the method.

Ah ok. By major update do you mean the major version changing or minor version changing? I don't know if there is a 2.0 update planned. I haven't played the game since b18... I assume even when the minor version changes, old saved games won't be compatible, so I could do the switch when 1.3 comes out?

Yep, I mean the minor Rimworld version change in this case.
Judging by the unstable branch, Rimworld 1.3 will have quite a few breaking changes, so that might be a good time to organize your "accidental data loss", if you choose to do it that way.

I see that HugsLib UtilityWorldObject is deprecated and I should move to the built in WorldComponent. If i do this (and update the component loading appropriately), will a WorldComponent automatically read data from the savefile previously saved as HugsLib UtilityWorldObjects? Or do I need to implement migration code?

You would have to migrate the data manually if you want to preserve it.
If I had to migrate, I would do it first thing during the WorldLoaded event, and add a flag to the UWO to indicate that it has already been migrated. This would also trigger the migration when a new world is created, but that would only "migrate" the default values- so, whatever.
In my own mods I just ditched the UWO's with the old data- that was during a major update, and since most players fired up fresh saves, no one complained.

[Updated to 8.0.1]

Updated to 8.0.1

I switched the patches on deprecated method errors to warnings to be less intrusive. I figure it's not a high-priority issue and someone will pick up on the problem eventually, and the info will find its way to the author of the mod.
Also, I removed the check from the 1.1 version of HugsLib altogether.

[Updated to 2.6.0]

Updated to 2.6.0

Hey folks, the 1.2 update is live.
While I was at it, I tweaked some stuff:
- There is now a button to re-enable the dice button after you clicked "Keep this map"- you can find it in the mod settings.
- You can now enter an arbitrary number into the map size setting. If your PC can handle it, I won't be the one to stop ya.
- There are now some optimizations in place, so you should notice significantly faster preview generation.

Take care and have a good one.

[Updated to 2.3.0]

Updated to 2.3.0

Tagged as 1.2-compatible. No further changes.

[Updated to 1.10.0]

Updated to 1.10.0

Tagged as 1.2-compatible. No further changes.

Will the lastest version work with Rimworld 1.0 ?

Yep, should be fully compatible with both 1.0 and 1.1.

[Updated to 3.9.0]

Updated to 3.9.0

Tagged as 1.2 compatible. No further changes.

Are those *Errors* or warnings or messages?

Errors, currently. Though the thought did cross my mind.
I could switch them to warnings, but those mostly go unnoticed by the players. Perhaps you have some thoughts on how to better handle the issue.