It was made in 2016 over half a decade ago and has nav mesh editing which shouldn't have been in there (can break other mods and cause CTDs) and doesn't have any of the features fixes or updates that the latest version of SkyTEST added in the half a decade it was released, and its not supported.
So this mod is a lite version of the latest file to include all of the fixes and updates that have occurred in the last half decade+ and I'm supporting it. I also fixed the bugs in the latest version as well in this Lite Version too. :)
Well thank you for asking the question. Its a good question and gives me a opportunity to better explain the difference. Ill sticky this. Kuddos for a good question.
Is It Compatible/Patch Questions: Due to the light nature of this mod 99% of the time a patch is no longer needed and instead a change to your load order is all that is required (i.e. my mod should come before x or after x). I do not mind helping people out with compatibility but ONLY if you spent at minimum 2 min looking at my mod and the mod in question in xEdit.
Because this mod is so light weight it only take a couple min to check compatibility - specifically you only need to look at about 50 records which can all fit on your screen at once. All you have to do is expand each tab and look for records in Red. Green, yellow, and white records can be ignored, red records require your attention but ONLY IF those records are edited by both mods. So in perspective here you are expanding tabs and only looking for a single color on your screen. It takes 2 min. I want to push you all to be better modders so to that end doing what I described above will teach you how to check. I am busy making and updating mods so this 2 min inconvenience burden should fall on you not me. That said however you can absolutely report back and ask me questions about findings if after 2 min you are lost - or say you don't understand please help - i am always happy to help :)
im not sure it would be the cause of your lag but a bad patch for sure can cause a crash and the original version required a ton of patches for sure :)
thats a issue with you using cutting room floor as it relates to the wolves killing the alpha. you will need a patch. Also fyi in real life there is no such thing as a alpha wolf. just a shameless pug on a dumb fact no one seems to know lol.
I would look at whats being overwritten from those mods and mine and see if a patch is necessary. Bears of the north does not require a patch place my mod after. As a rule I will assume my mod needs to win conflicts. so you will need to review xedit and ask those mod authors if they can make a patch for their mod and mine should one be needed.
Lol, every day, a new piece of information. I checked them in more detail and have done these modifications with my very limited patching knowledge for Witcher Horse Expansion:
I made a patch based on your mod and only added "OBND - Object Bounds" and "WNAM - Worn Armor" data from the Witcher Horse mod. How does it sound?
very likely just fine. Albiet what my mod cares more about is the NPC record and more specifically the factions and packages associated to it. so as long as those win your fine. you can forward anything else through and overwrite. just factions and packages should win. hmmm also the race should win more specifically anything relating to size and attacks.
Hello. Can you tell if some lines in .esp file are responsible for this behavior? So removing them will remove the "flee" function altogether. I'd like to keep all other aspects of this mod but not the fleeing animals when their health is low.
that is a issue with the engine/load order you have. it has nothing to do with this mod. a delay in behavior is a native issue to the game and can be worsened by a having a high script load and just in general assume if you have a ton of mods its going to worsen.
I laughed out loud in delighted shock when a lone wolf started circling my test character and actually behaving like a predator would without its pack!!! And the way rabbits move is so cute, they don’t run in a straight line. It makes hunting an actually fun challenge and this is now necessary in my load order! Thank you so much.
If you use this with "The Gray Cowl of Nocturnal" (Normal and 10th anniversary edition), the desert wolves in that mod will attack each other. I made a very small patch so they stop killing each other. If you or anyone else want to use that patch, it can be found here.
See this post on GCoN page for more details. Thank you mannygt for the help.
Thank you for your mode! I enjoy using it a lot. There seems to be a compatibility issue with Beyond Skyrim: Bruma. Wolves there attack each other at sight and do not behave as a pack in the way they do in vanilla Skyrim. Is there a solution for these issue? Anyone knows if there's a patch available? Would change the load order fix the problem? Thanks! Also, there's a compatibility issue with fishing from the aniversary edition, the frenzy mudcrabs became invisible with this mod installed, there's already a patch available for it, in case of anyone else having the same problem.
invisible mudcrabs is due to the racial changes not being present in the anniversery edition file so forward those changes - in the future i will be removing the mud crab racial edits so that wont be necessary - as it makes things run smoother without having to patch like that. As for Beyond Skyrim Burma - i dont know what they did but that sounds like a issue on their end. If you are only seeing normal wolves there and they are not unique in look in any way then i would say thats a bug and they accidently used some wolf asset they shouldnt have or made a custom wolf npc when it was not necessary and for no reason.
Thank you for your kind and quick response. I´ll wait for the future update concerning the mudcrab issue. With Bruma, the wolves seem to be unique, as they look different than the vanilla ones and are call "timber wolf" and "pack wolf". So probably they are a custom wolf npc. The definitely have custom assets.
Thanks for this awesome mod! will you update the legacy version to v4.2? For some reason Gate To Sovengarde uses v3.6 so I'm trying to update the mod manually. Also any chance to have the OneWithNature patch work with the legacy version? Cheers!
long term it will be double the work to maintain the legacy version - more importantly users were constantly using patches for the original SkyTEST with my legacy version causing them CTDs and blaming me for it when I explicitly say do not use legacy patches for original skytest. That said the newest version removes this issue because its renamed thus preventing that issue from coming up.
Anyway you can just use the change log to guide yourself load both mods up and then update the legacy version with the edits i made in the latest version.
Thanks dude! I have another update coming this year it should increase compatiblility actually via updating how mudcrabs were modified by specifically not touching the race record. This will nix some compatability issues with the mud crab race.
Right so this mod cant cause a CTD for you. based on the log it looks likely like Precision.dll is interacting with something causing the issue i would be curious if you were shooting a slaughterfish or something too or if something like a AOE spell hit it maybe.
That said this mod is used by 160,000 people and no one has had a issue unless they were using a outdated patch. Also if the crash was caused by my mod it has to be repeatable without fail. This mod at its core is primarily edits to animal HP and factions and it includes a few custom behviors but no scripts no interactions with anything else. It literally cant crash you game. Its super good to use a log to analyze but you have to factor and filter things. Like for example the mod Immersive Patrols has no issues or CTDs BUT if you get a CTD likely that mod will show up becuase in just about every cell there will likely be a patrol. Does that mean that mod is causing the CTDs? No. It just means it is in most of your loaded cells so if you see a log with that mod you know to ignore that mod and look elsewhere. Hope that helps and best of luck!
Thank you. I was indeed hitting it with the basic Flames spell and Belrand was pounding it with Apocalypse spells I believe, possibly also hacking it with his axe. I also use ''NPC Spell Variance''
Yea I dont touch any of that.... Just because you see a name in the crash log doesnt means its the culprit. you have to figure out what was happening* is it repeatable* who to rule out* etc. The issue was your interaction with that slaughterfish not anything with me. I changed the faction thats it and I dont change the interaction. If you look at what I do youd see that a faction edit cant crash the game. There is nothing unhandled. Only unhandled exceptions crash the game.
Okay so It's likely Animation Motion Fix being the culprit in combination with Precision. Others reported the same CTD on the AMF page. Sorry if my comment looked like I implied yours is causing the CTD which is not the case. I needed the fresh eyes for a lead :p Thanks again.
348 comments
So this mod is a lite version of the latest file to include all of the fixes and updates that have occurred in the last half decade+ and I'm supporting it. I also fixed the bugs in the latest version as well in this Lite Version too. :)
Due to the light nature of this mod 99% of the time a patch is no longer needed and instead a change to your load order is all that is required (i.e. my mod should come before x or after x). I do not mind helping people out with compatibility but ONLY if you spent at minimum 2 min looking at my mod and the mod in question in xEdit.
Because this mod is so light weight it only take a couple min to check compatibility - specifically you only need to look at about 50 records which can all fit on your screen at once. All you have to do is expand each tab and look for records in Red. Green, yellow, and white records can be ignored, red records require your attention but ONLY IF those records are edited by both mods. So in perspective here you are expanding tabs and only looking for a single color on your screen. It takes 2 min. I want to push you all to be better modders so to that end doing what I described above will teach you how to check. I am busy making and updating mods so this 2 min inconvenience burden should fall on you not me. That said however you can absolutely report back and ask me questions about findings if after 2 min you are lost - or say you don't understand please help - i am always happy to help :)
glad it helps!
Just installed your ESL file, saw some conflicts on xEdit with these mods:
Witcher Horse Expansion
CCOR
Simple Hunting Overhaul
and Bears of the North (I saw your comment suggesting that the patch is not necessary anymore)
Is any patches required for other mods? If no, does load order matter?
Edit: About the wolf pack between Riverwood and Embershard Mine, the wolves kills the alpha wolf for some reason. Can it be explained by this mod?
I would look at whats being overwritten from those mods and mine and see if a patch is necessary. Bears of the north does not require a patch place my mod after. As a rule I will assume my mod needs to win conflicts. so you will need to review xedit and ask those mod authors if they can make a patch for their mod and mine should one be needed.
I made a patch based on your mod and only added "OBND - Object Bounds" and "WNAM - Worn Armor" data from the Witcher Horse mod. How does it sound?
I love your implementation of cowardly animals who run away from you.
But every time this happens, my dummy companions keep chasing them, because these animals are still considered enemies in fight mode.
Is there a way to make animals stop their battle state when they run away from you?
I'd like to keep all other aspects of this mod but not the fleeing animals when their health is low.
If you use this with "The Gray Cowl of Nocturnal" (Normal and 10th anniversary edition), the desert wolves in that mod will attack each other. I made a very small patch so they stop killing each other. If you or anyone else want to use that patch, it can be found here.
See this post on GCoN page for more details. Thank you mannygt for the help.
Anyway you can just use the change log to guide yourself load both mods up and then update the legacy version with the edits i made in the latest version.
Glad I did, this rocks
Crashlog
That said this mod is used by 160,000 people and no one has had a issue unless they were using a outdated patch. Also if the crash was caused by my mod it has to be repeatable without fail. This mod at its core is primarily edits to animal HP and factions and it includes a few custom behviors but no scripts no interactions with anything else. It literally cant crash you game. Its super good to use a log to analyze but you have to factor and filter things. Like for example the mod Immersive Patrols has no issues or CTDs BUT if you get a CTD likely that mod will show up becuase in just about every cell there will likely be a patrol. Does that mean that mod is causing the CTDs? No. It just means it is in most of your loaded cells so if you see a log with that mod you know to ignore that mod and look elsewhere. Hope that helps and best of luck!