[September 3, 2023]Abyss Patcher

[Draconis.Pendragon]

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?

Make your own shortcut (for example if you use Steam.  Make sure the version: matches the current release, with what's in the code box in your "target" for the shortcut).  There's a universal setting that can be used, but it's been awhile since I've done that one.

Code: [Select]

"C:\Program Files (x86)\Steam\steamapps\common\Mabinogi\Client.exe" code:1622 ver:234 logip:208.85.109.35 logport:11000 chatip:208.85.109.37 chatport:8002 setting:"file://data/features.xml=Regular, USA"
or MabiDirectLaunch in Blade's thread (first post) are recommended.

[axoee]

I believe back when you had to inject abyss, it was working fine for me, but now it's just not allowing the client to open up. (Client.exe has stopped responding) it's the ijl11.dll file causing these problems with my client.exe, any method on fixing this at all ?

[Draconis.Pendragon]

I believe back when you had to inject abyss, it was working fine for me, but now it's just not allowing the client to open up. (Client.exe has stopped responding) it's the ijl11.dll file causing these problems with my client.exe, any method on fixing this at all ?

In Blade's FAQ/Readme he mentions that older Abyss versions are no longer supported.  He's revising the Readme some, but that's the gist of it.  So that's currently not a route available.  I'd suggest checking that readme out for some tips as well as his first post for more info.   Once you've tried some of the options there, I can only suggest you try running without Abyss and see how it behaves as an objective view point.  Then, depending on what version you use for Mabinogi you want to repair your install via Steam or the Nexon Launcher before adding Abyss in again (this means you need to remove it first before repairing).  You need a good install/foundation before you can use any patcher/mods.  This is paramount.  Many are able to use the latest version just fine, so this has to be some sort of configuration or file issue within your Mabi directory itself.  Whether it worked before isn't what should be the focus, it should be the here and the now.  Fix your "foundation" and all should be well. 

[axoee]

I've read the readme file but still have the problems, i'll try making a fresh foundation like you've mentioned and see how that treats me, thank you.

[Fl0rn]

Many are able to use the latest version just fine, so this has to be some sort of configuration or file issue within your Mabi directory itself.  Whether it worked before isn't what should be the focus, it should be the here and the now.  Fix your "foundation" and all should be well. 

I strongly encourage this.  Not necessarily do all the troubleshooting yourself, to get normal mabi working, but do make sure mabi works without mods before you blame abyss.  If you have trouble getting normal mabi to work, or getting abyss to work after that point, by all means post in tech support or in a relevant thread, just don't hijack someone else's thread as that'd be rude.


Everyone will need to try to keep an open mind.  Tried and tested is all well and good, but nexon's been on this anti-mod kick for a while now, and while i don't expect them to do anything that'd seriously break abyss on the user end, i also didn't expect them to put in effort against mods for as long as they've been doing.  Fool me once...  I don't view it as wise to completely dismiss that things may go screwy for some people at any point now, but users who want to report problems do need to make sure they're doing basic procedures and checks, so that they do have some idea of what they're talking about.  Cuz just coming in posting 'my mods are broke, pls fix' won't really help anyone.

[「★Ｓ２９★シ」]

I believe back when you had to inject abyss, it was working fine for me, but now it's just not allowing the client to open up. (Client.exe has stopped responding) it's the ijl11.dll file causing these problems with my client.exe, any method on fixing this at all ?

Aha, so im not the only one then. If I can take a guess. Windows 8.1, crashes after pleione finishes loading. Correct?

[axoee]

Aha, so im not the only one then. If I can take a guess. Windows 8.1, crashes after pleione finishes loading. Correct?

No. Windows 7, I run Mabinogi, click game start. -> Client Has Stopped Responding

I'm not using injected version, i'm just saying it used to work back in the day, and this version of non injecting doesn't seem to be working for me.

[「★Ｓ２９★シ」]

No. Windows 7, I run Mabinogi, click game start. -> Client Has Stopped Responding

I'm not using injected version, i'm just saying it used to work back in the day, and this version of non injecting doesn't seem to be working for me.

Oh..if it's that one
try disabling ExtraThreads?

[axoee]

Oh..if it's that one
try disabling ExtraThreads?

Still getting the problem 

[thisisdope]

So os this version of abyss currently working, I have a fee friends saying that they're able to play without NGS?

[deutonight]

For my case, everything works fine. Except when I click on dressing room, the game closes.
DataFolder=0
ExtraThreads=0
SecondaryPass=0

[Rydian]

Screenshot your packages folder.

[Chacha]

Well... this certainly seems to be an interesting situation...

Seems that, hovering over any type of revival balloon (the NPC character ones, the paper lanterns, etc.) will cause the client to stop responding and close.

This appears to be caused by the ShowTrueDurability mod. I can only guess it's because the balloons have 0 dura? If that is the case, I wonder if this also happens with a 100% broken item, too...

[Draconis.Pendragon]

Well... this certainly seems to be an interesting situation...

Seems that, hovering over any type of revival balloon (the NPC character ones, the paper lanterns, etc.) will cause the client to stop responding and close.

This appears to be caused by the ShowTrueDurability mod. I can only guess it's because the balloons have 0 dura? If that is the case, I wonder if this also happens with a 100% broken item, too...

I have no issue with this, and as far as I know Blade hasn't either but...  Do you have anything data folder related?  I'd eliminate that for a bit by renaming the folder or setting it to off in the ini.  This is just for diagnostic purposes. We heard about this earlier as well.  The dilemma is replicating the issue with the main dev machine and others that also dev.  We don't have this problem.  Let us know please how you make out on this.

[Chacha]

I have no issue with this, and as far as I know Blade hasn't either but...  Do you have anything data folder related?  I'd eliminate that for a bit by renaming the folder or setting it to off in the ini.  This is just for diagnostic purposes. We heard about this earlier as well.  The dilemma is replicating the issue with the main dev machine and others that also dev.  We don't have this problem.  Let us know please how you make out on this.

No, I have no data folder, and the Abyss option disabled. I have created a custom pack, though.

I've removed the custom pack, re-enabled TrueDura, and it still caused me to crash when hovering over a revive balloon.

*edit* Seems that ShowItemColor and ShowTrueDurability can't be enabled/disabled with slash commands?

[Draconis.Pendragon]

I've removed the custom pack, re-enabled TrueDura, and it still caused me to crash when hovering over a revive balloon.

*edit* Seems that ShowItemColor and ShowTrueDurability can't be enabled/disabled with slash commands?

When you crash is there anything in the Abyss patchlog?  skylaar727 has been having issues as well.  I'm trying to nail down origins.

[Blade3575]

When I use direct launch or power patcher, since I can no longer use injector to launch, my clients randomly crash without warning and do not give me any kind of error. If I successfully launch a client that has not crashed within the first 30 seconds of fully logging in (it happens consistently every other client, without fail), I will either crash when changing channels, going on a new character, or cont warping. Does anyone have any idea what could be happening since I am not receiving any kind of mabi errors? This didn't happen with the injector, and for someone who likes to multi-client (a lot) with all their alts for shops, this is extremely frustrating. Please help

Abyss doesn't use an injector anymore.

No, I have no data folder, and the Abyss option disabled. I have created a custom pack, though.

I've removed the custom pack, re-enabled TrueDura, and it still caused me to crash when hovering over a revive balloon.

*edit* Seems that ShowItemColor and ShowTrueDurability can't be enabled/disabled with slash commands?

The problem is almost definitely caused by the custom code written to force the durability string to show. I'll have to take a look at it. I also don't think I added it to the slash commands. Completely slipped my mind.

[Chacha]

@Draconis:
No, nothing added in the patchlog when I crash. And when launching, everything enabled is shown to be successful.

Code: [Select]

[09/10/16 09:03:53] - Source created by Blade3575 and Plonecakes for MabiMods
[09/10/16 09:03:53] - Credits: kotarou3, spr33 and whoever made mod_kirisame.
[09/10/16 09:03:53] - Initialization successful.
[09/10/16 09:03:53] - ijl hook installation successful.
[09/10/16 09:03:53] - Applying patches..
[09/10/16 09:03:53] - Abyss: Allow Monitor Sleep patch succeeded.
[09/10/16 09:03:53] - Abyss: Alt Name Color patch succeeded.
[09/10/16 09:03:53] - Abyss: Anti Flashy patch succeeded.
[09/10/16 09:03:53] - Abyss: Channel Move Description Cut patch succeeded.
[09/10/16 09:03:54] - Abyss: Clear Dungeon Fog patch succeeded.
[09/10/16 09:03:54] - Abyss: Clock Minute patch succeeded.
[09/10/16 09:03:54] - Abyss: Deadly Life patch succeeded.
[09/10/16 09:03:54] - Abyss: Disable Alt+Enter patch succeeded.
[09/10/16 09:03:54] - Abyss: Disable Barehand Msg patch succeeded.
[09/10/16 09:03:54] - Abyss: Disable Chat Filter patch succeeded.
[09/10/16 09:03:54] - Abyss: Disable Map Position Marker patch succeeded.
[09/10/16 09:03:54] - Abyss: Disable Quake patch succeeded.
[09/10/16 09:03:54] - Abyss: Enable FSAA patch succeeded.
[09/10/16 09:03:54] - Abyss: Enable Multi-Client patch succeeded.
[09/10/16 09:03:54] - Abyss: Exception Hook patch succeeded.
[09/10/16 09:03:54] - Abyss: Far Alt Display patch succeeded.
[09/10/16 09:03:54] - Abyss: Fast NPC Text patch succeeded.
[09/10/16 09:03:55] - Abyss: Ignore Maintain Frame patch succeeded.
[09/10/16 09:03:55] - Abyss: Infinite Dye Time patch succeeded.
[09/10/16 09:03:55] - Abyss: Interface While Dead patch succeeded.
[09/10/16 09:03:55] - Abyss: Item Hotkey patch succeeded.
[09/10/16 09:03:55] - Abyss: Last Position patch succeeded.
[09/10/16 09:03:55] - Abyss: Money String patch succeeded.
[09/10/16 09:03:55] - Abyss: No CleanUp patch succeeded.
[09/10/16 09:03:55] - Abyss: NoDMP patch succeeded.
[09/10/16 09:03:55] - Abyss: No Partner Zoom patch succeeded.
[09/10/16 09:03:55] - Abyss: Ping patch succeeded.
[09/10/16 09:03:55] - Abyss: Quiet Pet patches succeeded.
[09/10/16 09:03:56] - Abyss: Scouter patch succeeded.
[09/10/16 09:03:56] - Abyss: Scrapbook patch succeeded.
[09/10/16 09:03:56] - Abyss: Secondary Password patch succeeded.
[09/10/16 09:03:56] - Abyss: Show Item Price patch succeeded.
[09/10/16 09:03:57] - Abyss: Show True Durability patch succeeded.
[09/10/16 09:03:57] - Abyss: Item Color patch succeeded.
[09/10/16 09:03:57] - Abyss: Slash Command patch succeeded.
[09/10/16 09:03:57] - Abyss: Talk To Unequipped Ego patch succeeded.
[09/10/16 09:03:57] - Abyss: Uncap Auto Production patch succeeded.
[09/10/16 09:03:57] - Abyss: View NPC Equipment patch succeeded.
[09/10/16 09:03:57] - Finished patching.


The problem is almost definitely caused by the custom code written to force the durability string to show. I'll have to take a look at it. I also don't think I added it to the slash commands. Completely slipped my mind.

Thought I'd add onto this, I did modify the string so that it'd show the normal in-game dura BEFORE the true dura:

Code: [Select]

ShowTrueDurability_str="Durability {0}/{2} ({1}/{3})"
However, changing back to the default value doesn't stop the crashing caused by revival balloons.

Also, some interesting behavior I've noticed with the TrueDura and ItemColor mods...
With TrueDura enabled, it'll show the dura for items that don't normally have dura (potions, feathers, dungeon passes, etc).
With TruaDura disabled BUT ItemColor still enabled (yes, I know it won't work without TrueDura enabled), it'll STILL show dura for ALL items, but the items that DON'T have dura will show it in red.
In other words... in the first situation, a potion will show with 0/0 dura in white, but the second situation will have the potion's dura display as 0/0 in red.

[The Proffessor]

Also, some interesting behavior I've noticed with the TrueDura and ItemColor mods...
With TrueDura enabled, it'll show the dura for items that don't normally have dura (potions, feathers, dungeon passes, etc).
With TruaDura disabled BUT ItemColor still enabled (yes, I know it won't work without TrueDura enabled), it'll STILL show dura for ALL items, but the items that DON'T have dura will show it in red.
In other words... in the first situation, a potion will show with 0/0 dura in white, but the second situation will have the potion's dura display as 0/0 in red.

What I'm wondering might be happening is the show color patch might be activating certain aspects of the dura patch (hence the dura display numbers being shown), but doesn't use the entire code sequence that the dura patch uses. This might lead to Mabi's default coding seeing 0/X and go ok, this is a dura reading, and it's 0, so we need to color the text red, whereas having the dura patch active might overwrite that part, preventing the text from being changed from white to red.

Just my guess based on how things worked in the past.

[reanseih]

It says it cannot find ijl11.dll... help?

I just dragged and replaced the ijl11.dll in Mabi folder with Abyss's. I on Win 10 using Steam btw.

[jakeinhd]

When I run the directlauncher I still get "mabi is already running"

[gate3648]

having NGS problems

[Oranges]

Assuming NGS updated for the crook island that's coming.

[hotgluegun56]

Assuming NGS updated for the crook island that's coming.

Lol, crook island.

And same with others, NGS kicked me out of fishing :c

[Draconis.Pendragon]

NGS issues are known and passed on to Blade and the rest of staff.

An update likely won't be issued until after the upcoming maintenance.
Any troubleshooting or tech related stuff done on Abyss doesn't make sense to do until after the update, as things will change.   I'll be locking this thread until the update occurs to cut down on spam (repeated postings of NGS issues--since we're aware).  Any urgent issues feel free to PM one of us otherwise please.