Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
It looks like that was commented out for awhile and then on the 3 it was uncommented.
Would it be possible to add a check for worktab or a try/catch and just use the older mechanism for setting priority if worktab is also installed... at least until the worktab side can be fixed?
A work around for this would be really appreciated...
Please please please :)
Or would it not even work? if so, never mind
thanks either way, I really enjoy this mod, it's just a shame that right now the 2 just aren't compatible with each other at all. It's use bots or use the worktab enhancements.
Deactivate Worktab mod
Load game
Activate the robot
Save Game
Activate Worktab mod
Load Game
Enjoy running robots and cry because you now have to redo ALL the priorities in the work tab.
Since yesterday i get only errors, cleaning bots don't move out.
but even in a game with just worktab and just misc robots plus misc robots++ bots don't work
Didn't mean to highjack, sorry. Just adding info - There seems to be more compatibility broken than only WorkTab
I removed HuntForMe from the active mods. Now i get:
Exception in Verse.AI.ThinkNode_PrioritySorter TryIssueJobPackage: System.ArgumentNullException: Value cannot be null.
Parameter name: type
at System.Activator.CreateInstance (System.Type type, System.Boolean nonPublic) [0x00003] in <eae584ce26bc40229c1b1aa476bfa589>:0
at System.Activator.CreateInstance (System.Type type) [0x00000] in <eae584ce26bc40229c1b1aa476bfa589>:0
at RimWorld.WorkGiverDef.get_Worker () [0x00008] in <1b9c4c73530448bcbb33283e1d4d7d05>:0
at AIRobot.X2_AIRobot.GetWorkGivers (System.Boolean emergency) [0x00142] in <f8629bf68b234d8ab8eae69a792259cb>:0
at AIRobot.X2_JobGiver_Work.TryIssueJobPackage (Verse.Pawn pawn, Verse.AI.JobIssueParams jobParams) [0x0002d] in <f8629bf68b234d8ab8eae69a792259cb>:0
at Verse.AI.ThinkNode_PrioritySorter.TryIssueJobPackage (Verse.Pawn pawn, Verse.AI.JobIssueParams jobParams) [0x000fb] in <1b9c4c73530448bcbb33283e1d4d7d05>:0
UnityEngine.StackTraceUtility:ExtractStackTrace ()
(wrapper dynamic-method) Verse.Log:Verse.Log.Error_Patch2 (string)
Verse.AI.ThinkNode_PrioritySorter:TryIssueJobPackage (Verse.Pawn,Verse.AI.JobIssueParams)
Verse.AI.ThinkNode_Priority:TryIssueJobPackage (Verse.Pawn,Verse.AI.JobIssueParams)
(wrapper dynamic-method) Verse.AI.Pawn_JobTracker:Verse.AI.Pawn_JobTracker.DetermineNextJob_Patch2 (Verse.AI.Pawn_JobTracker,Verse.ThinkTreeDef&)
Verse.AI.Pawn_JobTracker:TryFindAndStartJob ()
(wrapper dynamic-method) Verse.AI.Pawn_JobTracker:Verse.AI.Pawn_JobTracker.EndCurrentJob_Patch1 (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_Patch4 (Verse.Pawn)
AIRobot.X2_AIRobot:Tick ()
Verse.TickList:Tick ()
(wrapper dynamic-method) Verse.TickManager:Verse.TickManager.DoSingleTick_Patch3 (Verse.TickManager)
Verse.TickManager:TickManagerUpdate ()
(wrapper dynamic-method) Verse.Game:Verse.Game.UpdatePlay_Patch1 (Verse.Game)
Verse.Root_Play:Update ()
so it seemed like a safe assumption that you had wortkab :P
I'm writing as I test more things so its a bit in order of my testing
Bit of experimenting has led me to find that using the Scenario condition "Allowed age range" was for me preventing the bot from being able to spawn.
Creating games without this condition was working but any game with it would prevent bots from spawning
Text editing my ongoing save file to remove the corresponding Scenario condition "ScenPart_PawnFilter_Age" allowed me to spawn new bot in my current game.
I also text edited the age range to allow 0 as minimum age this also allowed me to spawn a bot (Note: the scenario editor has a minimum age of 15)
I have tested a few other scenario conditions which affect pawns and not found any others that give me this issue though there are plenty i have not tested
After cutting down my Load order to:
Harmony
Core
Royalty
Ideology
HugsLib
Misc. Robots
Misc. Robots++
Work Tab
MiscRobots WorkTab support
RimPy Mod Manager Database
RimSaves
[FSF] Complex Jobs
I found that after testing removing and re-adding mods from above list it seems to be MiscRobots WorkTab support which has introduced this issue