[September 3, 2023]Abyss Patcher

[skylaar727]

Unfortunately can't speak for whether this has been happening in prior updates, as I only just reinstalled abyss today having played clean for a year or so.

Having a problem with the game CTDing with no error message when advancing from floor 1 to floor 2 alban, the moment I click the next floor button, doesnt happen going from floor 2 to 3 or 3 to 4. I initially had abyss and poison pack installed, but have since disabled poison pack for testing, still occuring. I've also tried disabling skip cutscene which was suggested as a sometimes problematic mod but still having the issue. Data folder is completely clean save for mabinovel content, was just about to try disabling ExtraThreads when this unscheduled maintenance hit.
Both Log and Debug have been enabled since I first noticed the issue, just unsure where this particular log file generates.

My abyss.ini is mostly stock, with a few of the features I don't care about disabled. Any suggestions for rectifying this issue would be appreciated. I'm trying to figure it out myself but with Alban being 3 entries a day, a little direction would be of use. Running latest version ofcourse. Thanks. Can provide my ini if needed to see my configuration also.

Patchlog including CTD time

[09/02/16 15:22:37] - Source created by Blade3575 and Plonecakes for MabiMods
[09/02/16 15:22:37] - Credits: kotarou3, spr33 and whoever made mod_kirisame.
[09/02/16 15:22:37] - Initialization successful.
[09/02/16 15:22:37] - ijl hook installation successful.
[09/02/16 15:22:37] - Applying unpack detection hooks..
[09/02/16 15:22:37] - Finished applying unpack detection hooks.
[09/02/16 15:22:37] - Client unpacked.
[09/02/16 15:22:37] - Reverting unpack detection hooks..
[09/02/16 15:22:37] - LoadDLL undefined
[09/02/16 15:22:37] - Applying patches..
[09/02/16 15:22:37] - Abyss: Data Folder patch succeeded.
[09/02/16 15:22:38] - Abyss: Bitmap patch succeeded.
[09/02/16 15:22:38] - Abyss: Bitmap Position patch succeeded.
[09/02/16 15:22:38] - Abyss: Alt Name Color patch succeeded.
[09/02/16 15:22:38] - Abyss: Anti Glare patch succeeded.
[09/02/16 15:22:38] - Abyss: Bugle to System Message patch succeeded.
[09/02/16 15:22:38] - Abyss: Channel Move Description Cut patch succeeded.
[09/02/16 15:22:38] - Abyss: Deadly Life patch succeeded.
[09/02/16 15:22:38] - Abyss: Disable Alt+Enter patch succeeded.
[09/02/16 15:22:38] - Abyss: Disable Barehand Msg patch succeeded.
[09/02/16 15:22:38] - Abyss: Disable Map Position Marker patch succeeded.
[09/02/16 15:22:38] - Abyss: Disable Quake patch succeeded.
[09/02/16 15:22:38] - Abyss: Enable Multi-Client patch succeeded.
[09/02/16 15:22:38] - Abyss: Exception Hook patch succeeded.
[09/02/16 15:22:38] - Abyss: Far Alt Display patch succeeded.
[09/02/16 15:22:38] - Abyss: Fast NPC Text patch succeeded.
[09/02/16 15:22:38] - Abyss: Infinite Dye Time patch succeeded.
[09/02/16 15:22:39] - Abyss: Last Position patch succeeded.
[09/02/16 15:22:39] - Abyss: Money String patch succeeded.
[09/02/16 15:22:39] - Abyss: Move To Same Channel patch succeeded.
[09/02/16 15:22:39] - Abyss: No CleanUp patch succeeded.
[09/02/16 15:22:39] - Abyss: NoDelay patch succeeded.
[09/02/16 15:22:39] - Abyss: NoDMP patch succeeded.
[09/02/16 15:22:39] - Abyss: No Partner Zoom patch succeeded.
[09/02/16 15:22:39] - Abyss: No SM VIP Message patch succeeded.
[09/02/16 15:22:39] - Abyss: Ping patch succeeded.
[09/02/16 15:22:39] - Abyss: Quiet Pet patches succeeded.
[09/02/16 15:22:40] - Abyss: Scouter patch succeeded.
[09/02/16 15:22:40] - Abyss: Scrapbook patch succeeded.
[09/02/16 15:22:40] - Abyss: Show Item Price patch succeeded.
[09/02/16 15:22:40] - Abyss: Show True Durability patch succeeded.
[09/02/16 15:22:40] - Abyss: Item Color patch succeeded.
[09/02/16 15:22:40] - Finished patching.
[09/02/16 15:22:43] - Previous filter: 0x2272D5EF
[09/02/16 15:22:55] - Menu modification successful.
[09/02/16 15:49:23] -
Exception Address: 0x0842BA47
Exception Code: 3221225477
Exception Flags: 0
Exception Information:
Exception Number Parameters: 2

As an update to this, just tried it again on the new update, thinking perhaps the crash was a precursor of the NGS error that kicked in later on yesterday. But no the crash is still happening reliably after the abyss update, instant CTD with no error message when moving from F1 to F2 alban when using abyss. Some help would be appreciated when you are done putting out fires I've also tried disabling extra threads and more since yesterday, and also running on a totally stock config.

Edit: So, I just tried it with absolutely everything in Abyss disabled except for bitmap font and position fix, floor transition worked. I'll try gradually activating stuff one at a time (or maybe in patches of 2/3) over the next few days but again with alban being 3 times a day and none of my alts being alban capable, its a little awkward to do so.

Edit 2: So a friend just had it happen, good to know its not me atleast, though someone else mentioned it after me here too. I've now tracked it down to one of 6 settings, but I'm all out of alban runs for the day if anyone else would like to thest.

FarAltDisplay
FastNPCText
MoneyString
NoPartnerZoom
ShowTrueDurability
ShowItemColor

Highly leaning towards it being the showtruedurability, that being the most recent feature, so most users probably havent updated their ini to turn it on. But we'll see tomorrow or whenever someone else tests it.

Final update, well until the issue is resolved I guess. I've finished tracking the issue down today, it appears to be ShowItemColor that is causing the crash on Alban Floor 1 to 2 Transition. Currently running with all 5 of the other settings I had narrowed down to it on, after having just true dura and item color caused a crash. Hopefully this makes it somewhat easier to fix, knowing where specifically to look for the problem. I've stuck all the previous info in that quote spoiler above, didnt want the post to be huge.

Thanks for keeping working on Abyss, its very useful, especially with how difficult Nexon are making this for you lately. Looking forward to a fix whenever you get some spare time to look at it

[Fl0rn]

Seems to be related to a gold exploit actually, they just updated the post.

I'm quite curious how they got onto that exploit, it's not like it was public. 

Well logically, i'd assume the exploit is throwing some kind of a flag, if it's bringing in loads of money fast.  Wouldn't all they have to really do is check some logs to see some people skyrocketing in gold?

[「★Ｓ２９★シ」]

As an update to this, just tried it again on the new update, thinking perhaps the crash was a precursor of the NGS error that kicked in later on yesterday. But no the crash is still happening reliably after the abyss update, instant CTD with no error message when moving from F1 to F2 alban when using abyss. Some help would be appreciated when you are done putting out fires I've also tried disabling extra threads and more since yesterday, and also running on a totally stock config.

Edit: So, I just tried it with absolutely everything in Abyss disabled except for bitmap font and position fix, floor transition worked. I'll try gradually activating stuff one at a time (or maybe in patches of 2/3) over the next few days but again with alban being 3 times a day and none of my alts being alban capable, its a little awkward to do so.

Edit 2: So a friend just had it happen, good to know its not me atleast, though someone else mentioned it after me here too. I've now tracked it down to one of 6 settings, but I'm all out of alban runs for the day if anyone else would like to thest.

FarAltDisplay
FastNPCText
MoneyString
NoPartnerZoom
ShowTrueDurability
ShowItemColor

Highly leaning towards it being the showtruedurability, that being the most recent feature, so most users probably havent updated their ini to turn it on. But we'll see tomorrow or whenever someone else tests it.
[/spoiler]


Final update, well until the issue is resolved I guess. I've finished tracking the issue down today, it appears to be ShowItemColor that is causing the crash on Alban Floor 1 to 2 Transition. Currently running with all 5 of the other settings I had narrowed down to it on, after having just true dura and item color caused a crash. Hopefully this makes it somewhat easier to fix, knowing where specifically to look for the problem. I've stuck all the previous info in that quote spoiler above, didnt want the post to be huge.

Thanks for keeping working on Abyss, its very useful, especially with how difficult Nexon are making this for you lately. Looking forward to a fix whenever you get some spare time to look at it

Thats pretty odd. The Color mod shouldnt have an interfearance with Alban Dungeon, But if thats the case then this is a nice find. Im pretty eagered to know why.

Hmm... The first thing I need to do is to get an actual account that can do alban up to floor 2. That might take a while but one of my connections might be able to lend me an account for it

[skylaar727]

Thats pretty odd. The Color mod shouldnt have an interfearance with Alban Dungeon, But if thats the case then this is a nice find. Im pretty eagered to know why.

Hmm... The first thing I need to do is to get an actual account that can do alban up to floor 2. That might take a while but one of my connections might be able to lend me an account for it

Ye, quite frankly I don't know why it is either, but I went around toggling off all the abyss settings, and eventually that turned out to be the switch causing it, I have no idea why though. It certainly wouldn't have been my logical conclusion at the start, I thought at first it might be fastnpctext or even the partnerzoom thing, since alban tends to zoom you when you move floors. But as far as I can tell, that is the switch.

[LunarCore]

Little question regarding the CPU Reduction option.
Is the value how much it will be reduced by or is it what it will to be reduced to?

[Fl0rn]

I believe, not 100% sure, that cpu reduction is how much the cpu is reduce by.  So at 100% cpu reduction, mabi shouldn't be using cpu.  Only applies while minimized.

[axoee]

It seems ijl11.dll always makes my "client.exe has stopped responding" show up, I'm running Windows 7 64bit, any help here guys?

[Dakeda]

So Mabinogi pulls up the old stopped working prompt and I can't figure out why. This happened even before I downloaded in abyss and now with abyss. This use to be an issue with a lot of players from previous Mabi updates. I can't seem to figure out why, so does anyone have a solution?

[「★Ｓ２９★シ」]

For the previous two posters. Did the Injection method worked before for your computers?

[lxWolfxl]

Why  with Abyss working, I can run mabi for hours but then at random i crash alot? i even crash when i put my mouse pointer over Revive Balloons from gacha. Why is that?

[Draconis.Pendragon]

Why  with Abyss working, I can run mabi for hours but then at random i crash alot? i even crash when i put my mouse pointer over Revive Balloons from gacha. Why is that?

The real question is what else is being used aside from Abyss?  Are there any data folder issues to be factored in?  Is mod_sharker being used? If neither of these 2, then the next thing is process of elimination with Abyss to disable features to see what's tripping it.  This is a pretty common troubleshooting thing.  Once it's found, then the solution can be shared with the community and it helps everyone as a whole.  I myself can use these just fine.  I checked again just now.  I'm using Abyss with Tiara and mod_sharker (minimal patches for that).  An outdated itemdb comes to mind.

[lxWolfxl]

i didnt do anything to the Data Folder and i only extracted Abyss in the Mabinogi file and thats it. I just start the game and it works fine. Like right now but i might crash at random which i cant find out why.

[Draconis.Pendragon]

i didnt do anything to the Data Folder

The data folder part is what I'm referring to.  Something is out of whack within it that is causing you issues.  A lot of people don't mention that they're using one along with Abyss, so we're left grasping at straws until the information is volunteered or we ask for it.  I'd start with your itemdb related files as these seem the most relevant place to start due to the recent updates. 

[lxWolfxl]

The data folder part is what I'm referring to.  Something is out of whack within it that is causing you issues.  A lot of people don't mention that they're using one along with Abyss, so we're left grasping at straws until the information is volunteered or we ask for it.  I'd start with your itemdb related files as these seem the most relevant place to start due to the recent updates.

How will i know what files are broken or missing?

[Rydian]

Get rid of your data folder.  Does it still happen?

[Fl0rn]

Get rid of your data folder.  Does it still happen?

and make sure there's only the normal pack files in your package folder if you're gonna do that

[Phrozenfox]

So what does Party Time (BANNABLE) do? I assume it's still there not because it immediately bans you, but because it's only safe with friends.

[The Proffessor]

So what does Party Time (BANNABLE) do? I assume it's still there not because it immediately bans you, but because it's only safe with friends.

It prevents Mabi from naturally taking down a party ad after a while, so it will continue to advertise indefinitely. The reason it says "Bannable" is because it can be blatantly obvious when someone uses it, since people can notice when the ad never disappears. People are known to report that on sight, and Nexon can notice by that fact as well.

[dangame]

Having some trouble getting the September 3 version working. I had no problems previously, but now the "client.exe" that the Injector launches only stays in task manager for less than 5 seconds, then vanishes and nothing happens.

FYI, I've looked up the issue here and added mabinogi.exe, client.exe, etc. to the DEP exceptions. I've also allowed the programs in my firewall settings, but I still get nothing after launching via the Injector. Running a clean client works just fine, but now even the last Abyss version from August doesn't work. Any insight or help would be appreciated!

[Draconis.Pendragon]

Having some trouble getting the September 3 version working. I had no problems previously, but now the "client.exe" that the Injector launches only stays in task manager for less than 5 seconds, then vanishes and nothing happens.

FYI, I've looked up the issue here and added mabinogi.exe, client.exe, etc. to the DEP exceptions. I've also allowed the programs in my firewall settings, but I still get nothing after launching via the Injector. Running a clean client works just fine, but now even the last Abyss version from August doesn't work. Any insight or help would be appreciated!

What if I told you that the latest version of Abyss doesn't need an injector  -insert Morpheus voice here-  It uses a proxy instead like it did before.  Please see the latest version for details...

[Phrozenfox]

It prevents Mabi from naturally taking down a party ad after a while, so it will continue to advertise indefinitely. The reason it says "Bannable" is because it can be blatantly obvious when someone uses it, since people can notice when the ad never disappears. People are known to report that on sight, and Nexon can notice by that fact as well.

But I can do that with a glitch and many people do lol

[dangame]

What if I told you that the latest version of Abyss doesn't need an injector  -insert Morpheus voice here-  It uses a proxy instead like it did before.  Please see the latest version for details...

Wow, I am a jerk. Thank you! I should've known when I saw it wasn't in the zip file. 

[Draconis.Pendragon]

Wow, I am a jerk. Thank you! I should've known when I saw it wasn't in the zip file. 

Naw, you're all good.  Shtuff happens.  No big.  The change was rather recent.  Blade added a readme too mentioning past versions weren't supported too.  Good luck.

[Fl0rn]

It prevents Mabi from naturally taking down a party ad after a while, so it will continue to advertise indefinitely. The reason it says "Bannable" is because it can be blatantly obvious when someone uses it, since people can notice when the ad never disappears. People are known to report that on sight, and Nexon can notice by that fact as well.

emphasis on the can be in there.  If you're dumb enough to go to your market channel and afk with a party ad up over night, yeah you should expect repercussions, as that's just stupidly obvious and asking for trouble.

On that note, i do use the feature, did use when i was playing, and have not had any issues.  For advertising purposes, i wouldn't even bother with this mod.  Just use the glitch to open party, cc to same channel, and then just leave the party ad closed, it will run the advertisement in chat still even though you don't have your party open.  This is far safer than the mod as it's reproducible without mods.  Less worry about someone reporting an obvious mod and you can still afk over night to advertise if you want.

I do however, see girgashiy party leaders use this feature now and then.  It's so easily noticeable cuz girg party closes way too fast normally, like a regular party would.  I've not heard anyone have issues for that either.


But ultimately, as with every mod, it's use at your own risk.  I don't believe nexon's taking any real action against regular mods at this point, other than the occasional patching of something.  However, you are still modifying your game, so it's possible for you to get in trouble at any time.  If you're worried about risk at all, don't mod.  If you want to minimize the risk and still mod, just play smart and don't do things like show off infinite party ad, read people's cp, and stuff like that. 

[TheDanglar]

Probably a noob question, but im fairly new to the modding community so pleas bare with me.. Once i extract the files, I get the option to replace the files (I clicked yes to the options assuming the larger file was the one required to replace the smaller one) Now, once all this has been completed, can i launch the game via the normal nexon launcher, or do i need to launch with the mabinogi launcher in the mabinogi file?