Does the bill for the smelter have to be set up a certain way? Whenever I set a weapon to recycle the job throws a red error and bugs out. Looks like this:

Exception in CheckCurrentToilEndOrFail for pawn Jem driver=JobDriver_RecycleThing (toilIndex=0) driver.job=(RecycleThisRecycle (Job_3842226) A=Thing_MeleeWeapon_Spear895282 B=Thing_VFE_FueledSmelter407068 C=(196, 0, 109))
System.NullReferenceException: Object reference not set to an instance of an object
at RecycleThis.ToilFailCondition+<>c__DisplayClass0_0`1[T].<FailOnUnpoweredWorkbench>b__0 () [0x0000b] in <9fead80ce8e54b46a3bb1faa28e2d130>:0
at Verse.AI.JobDriver.CheckCurrentToilEndOrFail () [0x00025] in <00638943358e4807bd44cd7bc8f572da>:0
UnityEngine.StackTraceUtility:ExtractStackTrace ()
Verse.Log:Error (string)
Verse.AI.JobUtility:TryStartErrorRecoverJob (Verse.Pawn,string,System.Exception,Verse.AI.JobDriver)
Verse.AI.JobDriver:CheckCurrentToilEndOrFail ()
Verse.AI.JobDriver:TryActuallyStartNextToil ()
Verse.AI.JobDriver:ReadyForNextToil ()
(wrapper dynamic-method) Verse.AI.Pawn_JobTracker:Verse.AI.Pawn_JobTracker.StartJob_Patch2 (Verse.AI.Pawn_JobTracker,Verse.AI.Job,Verse.AI.JobCondition,Verse.AI.ThinkNode,bool,bool,Verse.ThinkTreeDef,System.Nullable`1<Verse.AI.JobTag>,bool,bool)
Verse.AI.Pawn_JobTracker:TryFindAndStartJob ()
(wrapper dynamic-method) Verse.AI.Pawn_JobTracker:Verse.AI.Pawn_JobTracker.EndCurrentJob_Patch2 (Verse.AI.Pawn_JobTracker,Verse.AI.JobCondition,bool,bool)
(wrapper dynamic-method) Verse.AI.Pawn_JobTracker:Verse.AI.Pawn_JobTracker.JobTrackerTick_Patch0 (Verse.AI.Pawn_JobTracker)
(wrapper dynamic-method) Verse.Pawn:Verse.Pawn.Tick_Patch1 (Verse.Pawn)
Verse.TickList:Tick ()
(wrapper dynamic-method) Verse.TickManager:Verse.TickManager.DoSingleTick_Patch4 (Verse.TickManager)
Verse.TickManager:TickManagerUpdate ()
(wrapper dynamic-method) Verse.Game:Verse.Game.UpdatePlay_Patch1 (Verse.Game)
Verse.Root_Play:Update ()

@SkyLarkBlue should be fixed now.

Tysm!

I have some (marble) throwing rocks from Vanilla Weapons Expanded that have a flickering Recycle This button. This does not occur with other weapons from the same mod. There are no related error logs being generated.

Originally posted by Gyger:

I have some (marble) throwing rocks from Vanilla Weapons Expanded that have a flickering Recycle This button. This does not occur with other weapons from the same mod. There are no related error logs being generated.

Can you give me save with this flickering occuring?

Originally posted by Hate me:

Originally posted by Gyger:

I have some (marble) throwing rocks from Vanilla Weapons Expanded that have a flickering Recycle This button. This does not occur with other weapons from the same mod. There are no related error logs being generated.

Can you give me save with this flickering occuring?

Where do I send it to?

Originally posted by Gyger:

Originally posted by Hate me:

Can you give me save with this flickering occuring?

Where do I send it to?

anywhere, just give me link to save file. I am unable to reproduce this behaviour on my own.

https://ufile.io/vh1i1zwx Unfortunately the throwing rocks got destroyed but the low-shield pack is exhibiting the same issue.

This happens to me as well. I assumed it was because the game doesn't natively allow for the recycling of stony items (just metallic I think?). I don't know that I've ever seen a red error come up when it happens, just the recycle button hides so you can't click lol.

@Hate me
I am getting reports from users of “Project Rimfactory” that if your mod is used in conjunction with “Better Loading” then part of our mod breaks.
If only one of the two (your mod or “Better Loading”) is used, this issue does not exist.

I currently suspect that this could be caused by what is described in the Warning of “Better Loading” in line 154 to 166
https://gist.github.com/7c7bdbba626f0fc38f6a552510db99f8

Originally posted by IoDSn1p3rr3c0n:

@Hate me
I am getting reports from users of “Project Rimfactory” that if your mod is used in conjunction with “Better Loading” then part of our mod breaks.
If only one of the two (your mod or “Better Loading”) is used, this issue does not exist.

I currently suspect that this could be caused by what is described in the Warning of “Better Loading” in line 154 to 166
https://gist.github.com/7c7bdbba626f0fc38f6a552510db99f8

warning itself is nothing at all. It triggers because I patch method that runs all constructors for static classes with startup attribute. But my patch only reads data so, there's absolutely nothing it can break for other mods. If there's an incompatibility somehwere, it's not related to that warning. And I'll need some more info on this one.

@Hate me
Yes a warning in itself will not necessarily lead to problems, however this one specifically mentions that this action might (and in this case does) lead to a problem.
It seems that “Better Loading” changes something in relation to the method that you are patching and this is causing problems.
“In addition, when BetterLoading is installed, this postfix will run before any static constructors do, so it likely will not behave as the modder intended anyway. ”

As a Test i disabled this specific patch using dnSpy and i can confirm that without that patch and therefore that warning the issue no longer exists.

Line 163: “[BetterLoading] Modders: Consider either loading this data on world load, using a regular static constructor but asking your users to put the mod last in the load order, or if it MUST be done now, consider using BetterLoading API to detect the start of StageRunPostFinalizeCallbacks, which fires once static constructors are done.”

Please let me know if you need any additional information.

Originally posted by IoDSn1p3rr3c0n:

@Hate me
Yes a warning in itself will not necessarily lead to problems, however this one specifically mentions that this action might (and in this case does) lead to a problem.
It seems that “Better Loading” changes something in relation to the method that you are patching and this is causing problems.
“In addition, when BetterLoading is installed, this postfix will run before any static constructors do, so it likely will not behave as the modder intended anyway. ”

As a Test i disabled this specific patch using dnSpy and i can confirm that without that patch and therefore that warning the issue no longer exists.

Line 163: “[BetterLoading] Modders: Consider either loading this data on world load, using a regular static constructor but asking your users to put the mod last in the load order, or if it MUST be done now, consider using BetterLoading API to detect the start of StageRunPostFinalizeCallbacks, which fires once static constructors are done.”

Please let me know if you need any additional information.

Huh, I didn't that it runs method before all static constructors. Looks like betterloading is just incompatible with my mod then.

I get this error when I click on the writer's table when used in conjunction with Ben Lubar presents: Vanilla Books Expanded Expanded. Let me know if it makes more sense to report on that mod, I don't know enough about modding to know which angle it should be patched from.
It actually repeats endlessly until unselected:

Cannot get AdjustedCostList for VBE_WritersTable with null Stuff.
UnityEngine.StackTraceUtility:ExtractStackTrace ()
Verse.Log:Error (string)
(wrapper dynamic-method) RimWorld.CostListCalculator:RimWorld.CostListCalculator.CostListAdjusted_Patch1 (Verse.BuildableDef,Verse.ThingDef,bool)
Verse.Thing/<SmeltProducts>d__177:MoveNext ()
RecycleThis.Designator_RecycleThing:CanDesignateThing (Verse.Thing)
(wrapper dynamic-method) RimWorld.InspectGizmoGrid:RimWorld.InspectGizmoGrid.DrawInspectGizmoGridFor_Patch0 (System.Collections.Generic.IEnumerable`1<object>,Verse.Gizmo&)
RimWorld.MainTabWindow_Inspect:DrawInspectGizmos ()
RimWorld.InspectPaneUtility:ExtraOnGUI (RimWorld.IInspectPane)
RimWorld.MainTabWindow_Inspect:ExtraOnGUI ()
Verse.WindowStack:WindowStackOnGUI ()
(wrapper dynamic-method) RimWorld.UIRoot_Play:RimWorld.UIRoot_Play.UIRootOnGUI_Patch1 (RimWorld.UIRoot_Play)
(wrapper dynamic-method) Verse.Root:Verse.Root.OnGUI_Patch1 (Verse.Root)

Originally posted by SkyLarkBlue:

I get this error when I click on the writer's table when used in conjunction with Ben Lubar presents: Vanilla Books Expanded Expanded. Let me know if it makes more sense to report on that mod, I don't know enough about modding to know which angle it should be patched from.
It actually repeats endlessly until unselected:

Check latest update if it's fixed.