Coming back to Rimworld after a bit of a break and finding out that this mod can't be updated is devastating Always been so helpful for hauling/cleaning animals, managing toxic fallout/heatstroke etc.

Sorry, the saving/loading was broken in my update. Cant seem to fix it, sorry about that.

Mlie you are truly a Rimworld legend. I hope someone is keeping tabs on your health or you have an automated pipeline, because if you ever leave the community it's going to collapse into a prolonged mourning.

Nope!

hello ! no news for 1.5 ?

Brrainz is extremely active on his discord for his mods, I'm sure he'd be happy to help with the harmony changes (link on the harmony mod page)

It's a knowledge issue and it's a case of finding the time/desire to do it. It seems how the game defines area restrictions changed, so the old plumbing doesn't work. I took a guess at what the new one might be, but now I get a harmony error. It may just be a few simple questions on the Discord to find a fix, the current one being it says that `main` isn't defined, which it appears to not be but I'm not sure why it gets declared like that to begin with because I've never used Harmony myself. Knowledge would go further than money in this problem, it's what is needed to fix it.

Unfortunate to hear :(

If you have a Ko-Fi I'd be happy to donate to maybe help motivate

Love this mod

I'm not sure. I have an error which on its face seems trivial to solve, and feels like a configuration issue (aka, I did a wrong thing or didn't do something) but the short version is the solution doesn't compile. This could also be because something in 1.5 actually did change and requires more support. As of now I don't have plans to do so. If it *is* a straight-forward compile I just buggered up I may eventually, but right now I am not working on it.

You able to update to 1.5?

1.5?

Hi, is there going to be an update for 1.5? Thanks :)

@eclipse looks like compatibility is already on the requests thread in Grouped Pawn Lists too. lol

@eclipse You'll want to talk to the author of grouped pawn lists. Hyomoto has already said he is providing it as is. Also, it does work (I use them together myself), the only "incompatibility" is that you can't multi-include/exclude a group as a whole.

I mean look at the first screenshot, the top ones areas (for all pawns from one group) are not excludable

Could make it compatible with https://steamhost.cn/steamcommunity_com/sharedfiles/filedetails/?id=2340773428
?

HOW THIS NOT VANILLA AAAAAAAA!!! Epic mod!! Like, Subscribe, Favorite, Share!

Your head is in the right place, just on the wrong mod. I appreciate your decorum but, in this particular case, it's out-of-place. I agree with you. Except there is no lie in the "as a convenience" description. I'm honestly providing the mod "as-is" with no ulterior or additional interests. I'm not motivated by likes, favorites and subs. I'm not worried if people unfamiliar to RimWorld find it and I kind of hope they don't. It's like a donut. You put it on your car when a tire goes flat to get you to a gas station. For whatever reason, this one is still on the car and is going to pop and go flying off into a culvert some day. It hasn't yet, but it will unless someone comes along and properly replaces it.

I understand where you're coming from and agree with you in theory. I mean no disrespect with my comments.

However, the overwhelming majority of cases I've seen where RimWorld mods are updated to 1.4 and have tags for earlier versions removed either were unintentional or was not documented in a clear way to explain what happened to cause those tags to be removed. So getting an explicit clarification is helpful. (Additionally, mentioning a mod was recompiled for a new version is not really clear to non-programmers -- or even simply non-RimWorld modders.)

The only actual "issue" I see from this situation is if someone wants to use this mod in both 1.3 and 1.4 (e.g., reverting and re-patching RimWorld when going between). When this 1.4-only version of the mod has the same package id, RimPy (and maybe RimWorld, too) complains loudly about having the duplicate. I don't have a good solution, though, and changing the package id has inter-mod compatibility issues, as well.

It is identical feature and bug-wise, not compatibility-wise. Nowhere is it implied or stated earlier versions are compatible. I did update the description slightly, but this is a bit like asking people to go in and explicitly say their mod *isn't* for 1.4. That's what the tags are for. This isn't compatible with previous versions and, as such, it isn't tagged for them.

Hi, if this is identical to the 1.3 one, and it still works for 1.3 and other earlier versions, can you include those in the supported versions? (Especially since RimPy complains having both installed.) If it doesn't work for those versions, can you mention that explicitly? Thanks!

I have a strange error, recursive error. Gist here . It seems that on some situations this mod enters in beep mode of h*ll, making a recursive continuous error. Only restarting fixes the problem.
https://gist.github.com/1ef19e78a60c891498baa33f865b1c4d

No changes were made to this version, so if Hospitality didn't change then it will still have all the same incompatibilities.

Does anyone know if it is still incompatible with hospitality?

@Hyomoto Hi, can you include a link to the old mod in the description please? Thank you.

This supposedly isn't compatible with Hospitality. Any chance of that getting fixed at some point? They're both great mods.

Can you PLEASE make it compatible with remove death amnesia mod?

Rimpy says they're incompatible.

I should probably have an opinion on the issue. While it's unlikely a bunch of mods used this as their base, when it comes to patches and sorting rules, preserving that compatibility is more important. As I'm not currently maintaining the mod, this is a bare bones recompile, it is still gguakes mod and as such maintains the original mod id.

I'm in favour of updating the mod ID. It's more important (imo) to be able to keep both versions of the mod around in case the proper one gets updated. If sorting rules are an issue, activate the old version of the mod, sort, and then replace with this fork in the same location

(>**)> <(**<) ^(* - *)v v(* - *)^ ^(* - *)^ ^(=_=)^

I am against changing modid. Because sorting rules created for older versions will not be applied if you change modid.

Thanks! But you should change mod ID (add tempupdate or something like this) because for now qquake version (old) must be unsubscribed to make this one work