@daz_ian: Thanks for the info, it's partly correct. I've used the updated Outfitter as basis with this dependency, but it's just basic support and not really needed. Long story short: you can ignore it.
The development version (Github, branch "Linearized") and coming versions will have the dependency and warning removed.

According to the warning Mod Manager shows me, this mod depends on De-generalize Work , which Steam isn't listing here as a dependency.

Yes, there are still some minor issues. Just pushed the final update for tonight as there was some excessive logging.

Whatever you did seems to have done the trick! Thank you!

The only issue left seems to be pawns who can't decide between two pairs of boots / shoes and repeatedly pick up one set, then try to pick up another and drop the first. Rinse and repeat.

Forbidding one set seems to resolve the issue though.

@Balabalalde: Thanks for the log, very helpful. I've just reverted some of the changes and dida test. If the bug is still showing up, I'll have to snoop through some more mods adding worktypes.
ToDo: remove the Children messages

Here's a screenshot of the issue https://ibb.co/jLFrc4z

I think I have the same issue as kathryn, and it started happening after the hotfix. While you can click on outfitter, the part of the menu showing stat preferences and the info screen on the right portion is gone.

Here is the log https://gist.github.com/12290e7bbe02ce96a4ca1485bebcdf88

My thought is that its something to do the "Exception in Verse.AI.ThinkNode_Tagger TryIssueJobPackage: System.Collections.Generic.KeyNotFoundException: The given key was not present in the dictionary."

@kathrynboomer: it should look like in the screenshot. Can you post your log?

when i click outfitter, it doesn't pop up any menu..

kamikadza13: hot tested, should work as good as e.g. Outfitted.

CE compatibility?

I've been keeping an eye on Outfitter since 1.0 was released. Today Mehni from the rimworld subreddit informed me that there is a completely new version with a different title. I'm guessing that's why Outfitter hasn't been updated.

Outfitted (with a d): https://steamhost.cn/steamcommunity_com/sharedfiles/filedetails/?id=1595812861

@[SUN]KTV: here it is: https://steamhost.cn/steamcommunity_com/sharedfiles/filedetails/?id=1525516966

@Killface: please let me know when you merge, i'll delete mine.

I would love to see this updated for b19. such a great mod.
@Ara if you manage to make it work i ll gladly use it. Thanks

Okay, i got it working in B19. That feels very... "clumsy" , as i don't exactly know what i did, but it works, and i can see all the behaviours of the mod. I will try loading it with a more "complete" modlist and see if there's errors, but it should be OK. Regarding the Log.Message error, my guess is that this mod had not been recompiled with the b19 assembly.

@Killface: i will submit a PR, if that's okay with you.

@Mel : Alas, it's incompatible with B19. When trying to load or start a game with it, you get this error:

Exception from asynchronous event: System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.MissingMethodException: Method not found: 'Verse.Log.Message'.

Basically, it says that outfitter tries to call an unkown method. If you take a look at the github repository, you can see this method being called by outfitter. It should be safe to remove, but i don't know enough about C#'s tooling to do it myself and test further.

@Killface : i will gladly accept any pointers. (or does the c# world call them references? :p )

Is this compatible with Beta 19? I know it says it isn't, but I want to know whether that's just a label dealio and not a code-wise issue.

plz plz plz this was my most favorite mod, please update

update?

please update soon for V.19

@Fluffy Thanks, that dealt with some of the errors, the rest were fixed by redoing my stockpiles. Big help.

@killface; you're using .Max() on an enumerable that has no elements.
@Zerazar; try drafting everyone, and then save, disable, and load again. You may get errors on the first load, but after another save/load they _should_ go away.

Outfitter is giving me errors

https://pastebin.com/YNYaLMyb

If I unload outfitter (I'm not actually using its features), the game explodes with a bunch of different errors when I load in.

@dninemfive: I'm currently not actively developing, and I don't want to release a mod I wouldn't use and I would have to maintain. But the mod is open source, and everyone's free to build upon it.

Can we get a version of this which doesn't patch the tailor workbench? I use Better Workbench Management but this mod overrides that one regardless of their respective locations in the load order.

Nevermind, the other mod's author made them work without messing each other up.

This mod appears incompatible with the new animal armor mod. Just letting people know.

@Killface
The latest update is good. \o/ Thanks for your hard work!

@Killface You simply forgot to update Outfitter infused. The error message pops up because in the new build the variable name "ApparelScoreRaw_PawnStatsHandlers" was changed to "ApparelScoreRawPawnStatsHandlers" so the old infuse assembly can not work with the new outfitter. The outfitter infused source code is already altered for the new variable name in the github repo.

I haven't had any trouble loading saves for what it's worth throughout the fix stuff. Sorry to folks who are having trouble :c

@Fluffy, yeah I know, I just wanted to evade changing the mods after game start (steam to local) - with my number of mods it takes forever ;) thanks for the warning though.

@m33n; you'd be better off copying the contents to (steam)\steamapps\common\RimWorld\mods\Outfitter.

Make sure the contents are one level below the mods dir, so RimWorld\mods\Outfitter\About\About.xml, and NOT RimWorld\mods\outfitter\outfitter\about\about.xml.

That way, you're installing it as a 'local' mod, and steam won't try to 'update' your local version. By the way, if you want to be completely sure you can finish your save games, you can also copy all the mods from the steam workshop location to this 'local' location when you start a new game - that way you're sure you will always have the same (versions of) mods that you started with.

Thanks to @Killface for great mod!

thanks to you two!

So the workaround is to download https://github.com/Killface1980/RW_Outfitter/archive/0.18.1.zip and copy its content to (steamfolder)\steamapps\workshop\content\294100\738206572\ overwriting steam content.

I've been lucky enough to have a copy of the mod before the game-breaking update.
Here's the link to the old version, to be used in existing games until the Steam version is fixed:
https://www.dropbox.com/s/3jzrs8hkt58dnqi/Outfitter-0.18.0-rollback.7z?dl=1

You can install it like other non-Steam mods [rimworldwiki.com], and put it in the load order in place of the Steam version of Outfitter.

think steam screwed up in this case. cause for me just after u pushed the rollback steam started acting up for me. so might want to reupload the rollback maybe the rolled something back.

Sorry to confirm, unsubbed and subbed multiple times. Still cannot load any old saves, cannot start the new game either.

yeah still same error of

Exception from asynchronous event: System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.MissingMethodException: Method not found: 'Outfitter.ApparelStatCache.add_ApparelScoreRaw_PawnStatsHandlers'.
at (wrapper managed-to-native) System.Reflection.MonoCMethod:InternalInvoke (object,object[],System.Exception&)
at System.Reflection.MonoCMethod.Invoke (System.Object obj, BindingFlags invokeAttr, System.Reflection.Binder binder, System.Object[] parameters, System.Globalization.CultureInfo culture) [0x00000] in <filename unknown>:0

My game broke :(

damn no luck even unsub and resub still got the error.

had same issue of same error i unsub then resub now to see if that fix it

@SC.Vith; that looks like the same error as before, are you sure steam has properly updated the mod? It takes some time and/or a restart of RimWorld sometimes.

heh, it's weird to be on the other end of this for once :P It's usually me that screws up other people's saves, this time it was my save that was (temporarily) broken. At least this was only temporary, I've actually managed to release 'fixes' that permanently corrupted people's save files!

Anyhow, I know how it feels, you want to get bugfixes and improvements out there, and it's hard to test everything. I try to do a start a new game, save it, and then load it again test cycle at a minimum now, but that's only after several hard lessons...

P.S. I noticed the GitHub releases weren't synced with the steam ones. I have a node.js build script that automates releases to steam and GitHub, does versioning, change logs, etc, all with a simple command line interface. Hit me up on discord if you're interested.

Still can't load my save or start a new game. Getting the following error:
Exception from asynchronous event: System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.MissingMethodException: Method not found: 'Outfitter.ApparelStatCache.add_ApparelScoreRaw_PawnStatsHandlers'.
at (wrapper managed-to-native) System.Reflection.MonoCMethod:InternalInvoke (object,object[],System.Exception&)
at System.Reflection.MonoCMethod.Invoke (System.Object obj, BindingFlags invokeAttr, System.Reflection.Binder binder, System.Object[] parameters, System.Globalization.CultureInfo culture) [0x00000] in <filename unknown>:0
--- End of inner exception stack trace ---
(etc)...

np killface. everyone makes mistakes or rushes things.

Reverted. I want to apologize for the trouble this rushed and rarely tested "fix" caused. Coming updates will be tested more thoroughly.

hi there, just saw your messages. will revert in a few minutes.

There's also no download of the previous version on your github. Would be cool if you could fix this somehow. I can't even continue with my save with the mod disabled.

I really want to use this again, but whatever you did on the 11th has broken it beyond repair. Same as everyone else.