NGS Issues | PLEASE POST DETAILS HERE |

[Daisama]

This crap right here
This is driving me into berserker mode on modding NGClient.aes/BlackCall.aes.
I need those freaking hooks and you already know why. LOL

Yeah. Well, if you really want to, you can just cc every 4 minutes after closing bc. I'll pm you if i come up with a simple work around. I have a few ideas.

Oh and yeah, my client never got booted overnight.

[Rava]

Don't take my word for it, but try "Default.reg" in your mabinogi folder.

[ShaggyZE]

the tools are listed on the first post, if your not getting booted then we'll call it anecdotal, because a full install of tiara's data folder, meaning even risky mods installed causes me and a few other's to boot, but not everyone, i can provide proof, but it doesn't matter if it happens to you or not, because the tools listed on the first post don't boot everyone either, so some things are OS dependent on the ways NGS is scanning for them, but no more or less then eachother.
all the kick times seem to be the same 3:30-5 minutes or longer when you CC to reset the heartbeat.

[Rothchild]

I want to note that I got booted twice after replacing my custom .pack with one that contains a modded race.xml(for doll bag pickups) Here is what I did verbatim. I logged out of Mabi and started up logue's data packer. Packed my data folder with the only change being me adding the race.xml to my folder(note that I didn't previously have a race.xml, I added it) and set my custom .pack to read only like I previously had it set on pre-existing custom .pack(also note that I changed the name of the .pack from dumbpac.pack to dumbestpac.pack lol) I logged in using my client.exe shortcut targeted to the Nexon login servers and was kicked shortly after. I tried launching a second time(via client.exe shortcut) and was booted once again. I logged back in with mabi's default patcher and wasn't kicked. This kick puzzled me more than any previous kicks because the only change I made was replacing my .pack with another .pack

It leads me to speculate on one or all of the following
1). Mabi is some how detecting changes to client files, probably via logging information on your client somewhere.
2). It detects the game being launched from alternate source other than Mabi's default patcher.

I believe number 1 was already stated or is pretty clear lol but I wanted to share my experience in hopes that it helps narrow down the issue. I really think we just need to find commonalities between people getting booted and people who aren't getting booted. This will ultimately lead to what is causing the boots. I do feel that the different clients, installation patterns, and selection of mods we all chose to use contribute the the confusion we are facing when it comes to narrowing down the issue.

I also want to note that my last assessment(the one in which I stated .pack files were being detected) was flawed due to me having the data packer open during some of those checks. That being said I tested again without having the data packer open and got the same results except being kicked for .pack of course.

[Vermilliontrigger]

Just quickly sharing my experience on the off chance it helps someone here somehow. Windows 7 user.

Mabi + Abyss + Poison Pack + Golem AI data: Detected and crashed
Disabled ALL options of Abyss: Detected and crashed
Removed Pet AI data: Detected and crashed
Renamed Cheat Engine (On the off chance that was causing it): Detected and crashed
Finally I went with the last resort of outright removing Abyss: No detection

So for me, for whatever reason, it was flat out detecting Abyss' files as the issue, from the look of things.

[Fl0rn]

So for me, for whatever reason, it was flat out detecting Abyss' files as the issue, from the look of things.

Have you checked the logs for abyss?  They're in the mabi folder, should be something like abyss.log i believe.  Look for any fails in the log.

Have you tried toggling various features on/off for abyss, or flat out turning them all off?  Make sure you set them to 0, not delete the entries as deleting them just resets them to default, meaning some will be turned back on.

[Rixunie]

It works fine for me. Windows 7, have been playing since the anti-mod update with literally no issue.
I launch through the official steam launcher, and I have absolutely no problems playing the game. I use Abyss, Tiara, and installed through the UOTiara installer at Hoggshobbies

[Raidramon2015]

I use the shortcut launch and all mods work good both PCs have win 10 on them and using Tiara and Abyss with mod_sharker

[Morillo12]

So I reinstalled Mabinogi, implemented the latest Abyss & Poison Pack, and changed DataFolder=1 to DataFolder=0 in Abyss.ini (don't know if it's what made the difference or not, but I suppose it's worth noting since I didn't do it before?)... it's been over 30 minutes and I haven't been booted. I also didn't close NGS this time (another difference). My OS is Windows 10.

Update on this. I made no changes since then and got booted, sometime this morning, while I was away.

Edit: I relogged and am having no issues again... interesting

[Fl0rn]

Update on this. I made no changes since then and got booted, sometime this morning, while I was away.

Edit: I relogged and am having no issues again... interesting

Did you get dc/ed or booted?  Nexon's infamous for server instability, so a dc is nothing to worry on.

[lolzor]

There's always a chance NGS crashed itself for some dumb reason. If you're online for 10 hours straight, that wouldn't surprise me to happen.

[Morillo12]

Did you get dc/ed or booted?  Nexon's infamous for server instability, so a dc is nothing to worry on.

Nah, no dc - I got the NGS detection message on all of my clients

There's always a chance NGS crashed itself for some dumb reason. If you're online for 10 hours straight, that wouldn't surprise me to happen.

Might've been that, I was logged in for over 2 days

[Rothchild]

Okay so I finally got around on running some more tests based on the feedback I've been seeing. First I want to say that I was reluctant to test using a freshly installed client because I am usually very neat when it comes to updating my client and my mods. When Nexon updates Mabi I usually open up the default patcher in my clean mabi folder and update it then move my mods from modded mabi copy to clean mabi copy. I've been pretty much doing this for years without causing any errors so I rarely need to download a fresh copy. Anyways, I had a fresh copy which I downloaded and stored for a rainy day a few revisions ago.(so I didn't have to waste time downloading again) I moved my clean copy over to my c drive and dropped abyss files into it. Then I turned off all abyss mods(except for bitmap) because I planned to test everything out one by one. I logged in and immediately started CCing to see if I could cause myself to be kicked. Wasn't kicked. I waited for 10 minutes everything seemed to work fine. I then moved my old abyss .ini into my new mabi folder to check if it works before I wasted all that time testing abyss mods one by one and that worked just fine. Been in game for an hour+ without being detected. As I was typing this I also took the time to test my custom .pack and that worked just fine. I just moved it from old folder to new folder. No need for data folder.


tl;dr? Abyss+.pack+fresh copy of mabi worked fine for me.

[Fl0rn]

Idle thoughts after seeing Rothchild's post.  It doesn't take a genius to crack open a few pack files, and see redundancies across the packs.  Likewise, i've noted that when we get an update to mabi to make files obsolete, they're still stuck around in the folders.

Now, dumb thought as i wouldn't consider this with like any other company/game, but could there be obsolete files, or remnants in current files, that could be causing issues?  Cuz a fresh install would certainly get rid of most remnants, aside form what nexon keeps on their server.

I have no basis for this really, like i said it's more of an idle wondering.

[Rothchild]

I worked backwards a bit to see exactly what was causing the detection for me. I started by comparing all my new client files with my old client files to see what was different. Only thing that was different was some blackcipher.log files and my Abyss. Log files shouldn't be an issue. I dropped my old Abyss in to see if it was being detected and I was booted as I thought. I'm actually quite embarrassed that this is what it came down to but hey... hope my experience helps.

[Daisama]

Idle thoughts after seeing Rothchild's post.  It doesn't take a genius to crack open a few pack files, and see redundancies across the packs.  Likewise, i've noted that when we get an update to mabi to make files obsolete, they're still stuck around in the folders.

Now, dumb thought as i wouldn't consider this with like any other company/game, but could there be obsolete files, or remnants in current files, that could be causing issues?  Cuz a fresh install would certainly get rid of most remnants, aside form what nexon keeps on their server.

I have no basis for this really, like i said it's more of an idle wondering.

Who knows? If someone who has uninstalled(including deleting the folder) and reinstalled has had an issue, i'd like to know about it. (Edited to be less of a )

I worked backwards a bit to see exactly what was causing the detection for me. I started by comparing all my new client files with my old client files to see what was different. Only thing that was different was some blackcipher.log files and my Abyss. Log files shouldn't be an issue. I dropped my old Abyss in to see if it was being detected and I was booted as I thought. I'm actually quite embarrassed that this is what it came down to but hey... hope my experience helps.

By dropping in abyss, what files exactly did you move over? The ini? the whole thing? Is it a old version? Does it differ from the one you're currently using?

[Rothchild]

By dropping in abyss, what files exactly did you move over? The ini? the whole thing? Is it a old version? Does it differ from the one you're currently using?

the .dll and .dat most likely the one that comes with Tiara is causing the issue as it is out dated. I already moved over .ini from previous installation as I stated in my prior post.

[Daisama]

the .dll and .dat most likely the one that comes with Tiara is causing the issue as it is out dated.

That does make sense. That would probably explain why I didnt have an issue when i installed tiara, as i only got the data folder.

[ShaggyZE]

the .dll and .dat most likely the one that comes with Tiara is causing the issue as it is out dated. I already moved over .ini from previous installation as I stated in my prior post.

The .dll is the same and the .dat that Tiara uses is newer then the one Abyss uses, so that's not the case, check the dates, i believe his is 2014 and tiara's is 2016.

That does make sense. That would probably explain why I didnt have an issue when i installed tiara, as i only got the data folder.

Actually it wouldn't make sense, because before Blade was uploading Abyss to my server himself, and if not when he updated we would upload it, so the versions between Tiara and Blade were never different until a few days ago, Draconis started using the latest ijl15.dll renamed to .dat as to increase chances of avoiding NGS detection.

[Daisama]

The .dll is the same and the .dat that Tiara uses is newer then the one Abyss uses, so that's not the case, check the dates, i believe his is 2014 and tiara's is 2016.
Actually it wouldn't make sense, because before Blade was uploading Abyss to my server himself, and if not when he updated we would upload it, so the versions between Tiara and Blade were never different until a few days ago, Draconis started using the latest ijl15.dll renamed to .dat as to increase chances of avoiding NGS detection.

Interesting. Well, this is all above my head. Good luck.

[MasterNick]

My Abyss is actually the latest it seems, modsharker is old still working fine, and Tiara at V227. Nothing seems to be a problem here. Might test the others if needed.

Please do, cause I actually want to know myself, I tried a lot of methods, and will continue to, until something works -.-.

[Rothchild]

The .dll is the same and the .dat that Tiara uses is newer then the one Abyss uses, so that's not the case, check the dates, i believe his is 2014 and tiara's is 2016.

Probably because the Tiara I been using is different. I didn't feel the need to download a new copy since it had the same revision number... oh well.

[unknownuser1]

for what it's worth:

I did a clean install - no problems.

Tried online tiara - booted after about 5 minutes.

clean install then offline tiara - booted after about 5 minutes.

used friend's ijl15.dll file - because this seems to be what was causing problems before i tried clean install - no problems, was able to afk all night.

[Draconis.Pendragon]

for what it's worth:

I did a clean install - no problems.

Tried online tiara - booted after about 5 minutes.

clean install then offline tiara - booted after about 5 minutes.

used friend's ijl15.dll file - because this seems to be what was causing problems before i tried clean install - no problems, was able to afk all night.

This is essentially what I've been doing with all PCs that I work on.  I pull the  ijl15.dll file from the latest patch, and then rename to  ijl15.dat.  Then this allows people to get on, and stay on as well as myself.  This is all I'm doing.  Btw, I'm no longer using KR files of any sort.  I stopped using those awhile back once most of the issues we were having were ironed out, around early April.  This was also because I wanted to be sure that I was using the same files that everyone else "should" be using if the patchers pull and update the files as they should.  This is why I use PowerPatcher to pull all files and keep the directories to validate myself.

[ShaggyZE]

Probably because the Tiara I been using is different. I didn't feel the need to download a new copy since it had the same revision number... oh well.

when their is a significant enough change, the minor revision number will change, hovering your mouse over the .exe or right clicking and going to properties shows the details ie 228.0.0.1, and the old installer will notify you, otherwise your right their is no need to download a new copy as the online version pulls the files from the FTP so it always has the latest files.