i only have abyss, but i also read up that AVG can cause it to happen, is that true? Also i removed all mods did a clean install and it still happened, it stopped after i restarted computer. know anything??
Avg has been known to detect mabinogi as a threat and lock away one of its files rather than mod related items. Though crackshield and things like that will tend to be detected by avg as well and stopped immediately before it saves the file to the drive.. You can temporarily disable avg or set permissions to ignore the folder entirely.
Not sure if this will be of any help, but I didnt have any problems with mods being detected like this until an hour ago when I disabled Nagle.
Im going to go out on a limb and say this is unrelated to your detection of mods.
Hmm, so I'm trying to use kanan on my desktop and it gets NGS error, but when I use it on my laptop it works fine and goes undetected (I believe its the Old October version of kanan from the date), but I tried copying files over and it gets detected on desktop even if the frida is 8.1.1 :S Not sure how to make desktop version work
Your itemdb.xml is probably outdated. (just taking a guess here)
Since it's not NGS, i would recommend making a tech support thread if you need further help though, as this thread was intended specifically for NGS issues and nothing else.
Yes, when the game updates and you have modified data files, not all the files will be updated. If you do not have the item information for a new item that was added to the game it will force your game to crash if said item is displayed on screen and loaded into memory. Mabinogi crashes from very minuscule memory hiccups so if it cannot find the data for certain items you will need to update the data files to the new version, or never look at a new item. Granted this may effect any mods related to that file if corresponding changes are relevant. In some cases there may be no issues, but your new items will definitely not have their descriptions and just their call item ids.
Using Kanan, and tried using abyss getting kicked due to NGS
If you are using
both kanan and abyss, and abyss is triggering the ngs detection then might I give a suggestion? If you are not feeling like waiting for the update on abyss patiently, then perhaps I can suggest a simple solution to making abyss not be detected until the updates. Usually disabling the part of abyss being detected will prevent detection. This being said, you are also using kanan as you stated here, which holds some similar modifications that are usually detected in abyss. Would it not be a wise move to temporarily disable the redundant modifications of abyss that are also in kanan -- and only use the non detected items that are abyss? This seems like it would solve the issue out flat so long as those modifications are the issue. At least until the abyss is updated, which should not take long at all. I think its usually the cp reader that is detected but someone else can provide more insight into that. Just keep an eye out on the abyss updates.