Search results

We will check this out shortly, thanks for the report! :)

Thank you for your patience! We're looking into the problem.

We're here and we're taking all of your suggestions and complaints into account! We're currently working on some bugfixes which will be implemented soon. Thank you for your patience and understanding - all we want is to develop and improve AdenaBuddy - and we need all of you to help us create...

The log that you've sent starts with an error but it seems like the repair algorithm has fixed the progress? I mean the log as you sent it doesn't end with an error. Does the problem still persist?

Thank you for the detailed information. It helped us identify and fix the problem - an update has been rolled out. If you have any other questions or issues you can ask here or in the general section of the forum. Have a nice day! :)

We've identified the issue and the problem has been fixed, an update has been rolled out. Have a nice day! :)

Okay, can you walk me through the process of repairing? What happens from the moment you get the "Repairing quest chain. Please do not interfere." message and the error message. Is your character talking to an NPC when the bot crashes? If yes - which NPC?

Okay so let's go through the problem one more time - you start the bot, repair algorithm starts, the character goes to sel mahum and once he gets there you get the "Quest chain has been stopped." message and the bot stops?

Can you please tell me the current file and current command from the .json file with the name of your character?

Hey! The chain isn't supposed to stop unless it's been stopped manually or the character finishes the quest chain. Did you try to restart the bot and the L2 client? Does the problem still persist?

The bot is 100% AFKable and "one-click" to 85. If you think your character is stuck - give it a couple of minutes. If the problem with the chain is serious a repair algorithm triggers and fixes the quest. You don't need to manually "fix" and "redirect" it because if you play manually while the...

No, currently AdenaBuddy supports just the NA official servers.

Did the problem get fixed by the repair algorithm by any chance? If not, could you please copy/paste the error from the log tab?

As of now we have no ETA for support for other servers than NA. If I could help you with anything else feel free to ask here or in the general section of the forum. :)

I'm glad I was able to help. About asi win, as I said in another thread, the AdenaBuddy staff is not affiliated in any way with other 3rd party software. We cannot guarantee that it will work with AdenaBuddy and we have no information regarding the chance of ban when using said 3rd party...

In order to start multiple clients with bots you need to: Step 1. Start AdenaBuddy from the .exe Step 2. Start Lineage 2 from the shortcut Step 3. Log in Step 4. Start 2nd instance of AdenaBuddy from the .exe again Step 5. Start 2nd instance of Lineage 2 Step 6. Log in your 2nd toon Step...

The problem has been identified and fixed. An update has been rolled out. The Shillien Saint should now continue questing as normal.

I'm sorry you're encountering problems - the bug with the no available desired classes on the Shillien Saint is already fixed, the update has been rolled out. About the other problems - I will need you to work with me so we can identify and fix the bugs if there are any or just get you back...

Okay, could you give me a bit more info on what happened. Did they crash and couldn't repair? Can you upload a .txt file with the error message from the log?

Hey, 1. I replied to your other thread about that question. 2. The Lineage 2 client iteslf has a restriction on running multiple boxes to three. If you search the web there are tools out there that remove that restriciton, but AdenaBuddy and our staff isn't affiliated with them in any way...