Bug/Issue crew members not attacking monsters.

they used to attack everyone.but ever since a 1.3.x update they stopped attacking monsters. they only attack humanoid npcs. I don't have any crew member editing mods enabled. please fix. this is on a win10.

 

http://steamcommunity.com/sharedfiles/filedetails/?id=1187073507 these are the mods that i use.

 

I believe that the hunter crewmembers mod is doing this.
Try disabling it.

 

i disabled it but my crew still ignores monsters.

 

Oh

 

Do you have a log? Maybe I can help, but I need a log.

 

so i found out that they dont attack anyone thats in a planet. they only fight in vault dungeons and ship encounters.

 

the crew members attack normally on the unstable version.

 

Hmm... will have to look into that when I decide not to play unstable.

 

I made a video on the bug.

 

That is very strange. It may be caused by the game engine not updating the npc's state. That's my best guess as of now, but I may have to do some testing of my own. Can you provide me a list of the mods you use? (Link above is broken)

 

here it is http://steamcommunity.com/sharedfiles/filedetails/?id=1347960655

 

The ones I would think could cause an issue are...

• Avali Triage
• Frackin Universe
• Lombaxes
• Toei Sonic Race

Other than that, I have no idea what could cause this.

 

Thanks,but the bug happened before I got those mods.

also they attack on spaceships,vault dungeons,and story missions.but not on planets.

 

So this discussion started on the 31st of October, 2017. That means that the bug must have started around that time, right?
If my subscribed items have a subscription date on them in the workshop by opening up the workshop, pressing "Your Files" and then "Subscribed Items", it should for you as well. Try doing that and post a list of the mods with either an update around that time or subscribed to around that time. This may mean looking under "Change Notes" for each mod. I may try to do some digging, but I cannot do all of the work by myself. This should help narrow the list of possible culprits.

 

ok i should do that. and btw heres my log

 

also there is another person who seems to have the same problem https://steamcommunity.com/app/211820/discussions/3/1290691937706633648/

 

there is a simpler way to find what mods were subbed to/updated around the time of the error rather than going into the change log of every mod. Follow the instructions above and list the mods subscribed to around the time of the error, then, in the right column there should be an option to sort by date updated. click that and list the mods updated around the time of the error

 

the bug started when update 1.3.3 was released.