Jump to content

Recommended Posts

  • 9 months later...
Posted

Hello. When you disable autoloot and select items from the ground, sometimes an error with the server message “Push item fail” may occur. The item is not displayed in the inventory, but when performing a relog, the items appear in the inventory. Has anyone encountered this?

  • 2 months later...
Posted (edited)

Hello @Hitcher. Could you please clarify the scenario in which this happened?

Was it on GF server?

The drops that were on the ground were from the same character? These fell with autoloot off, then you activated autoloot and tried to pick? Please provide more details so we can replicate it.

Edited by MoikaCL
Posted (edited)
On 11/21/2024 at 3:19 PM, MoikaCL said:

Hello @Hitcher. Could you please clarify the scenario in which this happened?

Was it on GF server?

The drops that were on the ground were from the same character? These fell with autoloot off, then you activated autoloot and tried to pick? Please provide more details so we can replicate it.

Hello. You may encounter the Push item fail error when trying to pick up an item dropped on the ground by a mob.
or
You can throw something out of your inventory and pick it up again, several times.
Probably this is a quantum dependency) I don't understand at what point this happens, sometimes two items one after another experience push item errors, and sometimes I don't have enough thousands of attempts to repeat this trick)
In any case, this is just a visual error and after the relog, the item appears in the inventory. I think first i need to disconnect the extender and check it on a bare server. I still need time to check this, maybe it's not even about the autoloot function.
https://youtu.be/6mcfmdImofE
-----------
In general, I would like to thank our wonderful Emca Eressea for her deep knowledge in programming and reverse engineering. And for the fact that her work is open to everyone, this is very amazing, and incredibly valuable.

Edited by Hitcher
  • 3 weeks later...
Posted

I would like to highlight one more observation: 
Myext.ini:
[autoloot]

; Whether autoloot drop from mobs
AutoLootMobDrop = False

- It is impossible to call the trade function with another player.

  • 2 weeks later...
Posted

Hey all,

Those of you which are actively using/working on the extender, do you encounter server crashes when using any GM chat command?
For example if i use //say or //announce or //critannounce the server crashes with no obvious error being shown on the logs.
Using the God's Voice command from the L2Server itself works just fine, the server crashes only when i do i with a builder level 1 account in game.
For context, i've built de extender from source, and i'm using the patched .exe(s) CachedMyExt64.exe / L2ServerMyExt64.exe shared on this thread.
Using ProtocolVersion = 152 in the MyExt64.ini (all settings to default as per repository).
I've been scratching my head to understand where the error comes from for the last 2-3 days.
If anyone has had this issue and knows where to look at please share.
I'm not asking for the solution itself, just pointing in the right direction.
Thanks a lot!

I know it might not make any sense but here's how i solved this:
I've had the L2Server folder named Server.
As soon as i've renamed Server back to L2Server, the server does not crash anymore when using GM chat commands.
Just for testing, i renamed it couple of times more.
It seems that if the L2Server folder (where the L2ServerMyExt64.exe resides in) is named anything else but L2Server, it will cause a crash.
Has anyone else encountered this issue?
I'm happy the issues is solved but i'm intrigued about what caused it.
Regards. 

7 hours ago, JamesW said:

Hey all,

Those of you which are actively using/working on the extender, do you encounter server crashes when using any GM chat command?
For example if i use //say or //announce or //critannounce the server crashes with no obvious error being shown on the logs.
Using the God's Voice command from the L2Server itself works just fine, the server crashes only when i do i with a builder level 1 account in game.
For context, i've built de extender from source, and i'm using the patched .exe(s) CachedMyExt64.exe / L2ServerMyExt64.exe shared on this thread.
Using ProtocolVersion = 152 in the MyExt64.ini (all settings to default as per repository).
I've been scratching my head to understand where the error comes from for the last 2-3 days.
If anyone has had this issue and knows where to look at please share.
I'm not asking for the solution itself, just pointing in the right direction.
Thanks a lot!
EDIT:

I know it might not make any sense but here's how i solved this:
I've had the L2Server folder named Server.
As soon as i've renamed Server back to L2Server, the server does not crash anymore when using GM chat commands.
Just for testing, i renamed it couple of times more.
It seems that if the L2Server folder (where the L2ServerMyExt64.exe resides in) is named anything else but L2Server, it will cause a crash.
Has anyone else encountered this issue?
I'm happy the issues is solved but i'm intrigued about what caused it.
Regards. 

 

For some reason i cannot edit my own post...

Posted

I apologize for my incompetence. The ability to trade is limited only for builder 1. Ordinary characters can trade with each other, and this has nothing to do with auto loot.)

Posted (edited)

If you pay attention to only one decompiler-compiler AiNasc, which was shared by Emca Eressea. A compiler that other developers want thousands of dollars for. This can already be fully considered a huge contribution to the development of the development community of our beloved great game Lineage 2.

Edited by Hitcher
Posted
20 hours ago, JamesW said:

@Hitcher I agree 100%! Are you running a live server using MyExt64 or just experimenting? I'm currently creating my IDA db's so i can start adding more stuff into the extender.

I'm just testing the extender) I couldn't find any critical issues.
 

I found my own error due to which the autoloot function was not active:
just a syntax error, case-sensitive. You can't use a capital letter in the Myext.ini settings.
AutoLootMobDrop = true. (parameter true must necessarily be with a lowercase letter)

Posted

@Hitcher what i found is that rates from MyExt64.ini are somehow ignored.
For example, if i set:

in L2Server.ini
 

[event]
adenaamount=0
itemrate=0
spoilrate=0
exprate=0
aiadenarate=0
aiexprate=0


and in MyExt64.ini
 

[rate]

; Adena rate
AdenaRate = 1.0

; Drop rate
DropRate = 1.0

; Spoil rate
SpoilRate = 1.0

; RB drop rate
BossDropRate = 1.0

; Herb drop rate
HerbRate = 1.0

; For highrate servers turn this on, lowers drop for mobs lvl 19- so you don't get 40 small shields
FixupLowLevel = false

; Items that are not affected by rate change
IgnoredItems = 6656,6657,6658,6659,6660,6661,6662,8191

; Whether dump drop/spoil to a file in DUMP folder
Dump = false

; Seal stone amount rate (multiplier)
SealStoneAmountRate = 1.0


The rates from MyExt64.ini are ignored.
Does anyone know what is the issue here?


I've also tried with the below setting as i read somewhere that 100 would be 1x

[event]
adenaamount=100
itemrate=100
spoilrate=100
exprate=100
aiadenarate=100
aiexprate=100


However, when i set this, the exp/sp/adena is somehow 3x in-game.
I've tested with killing 1 gremlin with lvl 1 char and the exp and sp is x3 the amount in acquire_exp_rate=382.07    acquire_sp=26.

  • 1 month later...
Posted

There is one bug. When the character is running and you try to use frenzy, the server does not send the character's stop packet to the client. You'll get a knockback loop.
(same thing when using summon pet without a crystal) or calling a friend outside the zone. We need a specialist who understands packages.

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.




  • Posts

    • hello, do you have maybe source nwindow.u for protocol 24?
    • Now begins your final fall, you don't know who you messed with and who I am, nor can you imagine what awaits you. Dragon Network will have to answer for its actions before the FBI, and thus begins its downfall.
    • This post originally appeared on zupyak. The EA FC 26 Closed Beta is almost here, giving select players an exclusive first look at the game before its official release. Running from August 6 to August 26, 2025, this beta will let testers try out key gameplay changes and provide feedback to EA. If you're eager to secure a beta code, this guide will walk you through everything you need to know—from eligibility requirements to how to maximize your chances of getting an invite.   How to Get an EA FC 26 Beta Code 1. Beta Codes Are Account-Locked (No Sharing!) • If you receive a beta code, it will be tied to your EA account and cannot be shared or sold. • Attempting to share or buy a code is against EA's NDA (Non-Disclosure Agreement) and will result in a ban. 2. Check Your EA Account Settings • Log in to the EA website and go to Account Settings. • Navigate to Communication Preferences and ensure you're opted in for: • All EA Sports games, including FC 25 and FC 24 • The platform you actually play on • Promotional emails 3. Sign Up for EA Playtesting • Visit the EA Playtesting portal and register. This increases your chances of being selected for beta access. 4. Play FC 25 Regularly EA prioritizes active players, especially those who compete in Division Rivals and FUT Champions. The more you play, the higher your chances of receiving an invite. 5. Check Your Email (Including Spam!) If you don't receive one immediately, check again on August 13, as EA sometimes sends codes in waves.   What Game Modes Are Available in the Beta? • Kickoff (available to all testers) • Ultimate Team (FUT) • Clubs • Career Mode Your access to modes beyond Kickoff depends on your past gameplay history in FC 25.   Important Beta Rules & Restrictions Do: • Test the game and provide feedback in the official EA beta forums. • Keep all beta details confidential—no streaming, screenshots, or social media posts. Don't: • Share or sell your beta code (it won't work for anyone else). • Discuss the beta publicly—breaking the NDA can lead to account bans. • Expect progress to carry over—the beta is for testing only.   Final Tips to Improve Your Chances • Play FC 25 frequently—active players get priority. • Only select platforms you own—only available for consoles. • Check your spam folder—beta emails sometimes land there. • Avoid VPNs—EA may restrict access based on region (US & UK have higher priority).   What If You Don't Get a Beta Code? The beta code has been released on Augest 4. If you didn't receive one, don't worry, as EA sometimes sends codes in waves. Final Thoughts The EA FC 26 Closed Beta is a fantastic opportunity for dedicated fans to shape the future of the game while enjoying early access. By following these steps and staying active in FC 25, you can maximize your chances of securing a coveted beta code. Remember, confidentiality is key—so keep all details private and abide by EA's rules. And when the full game officially launches, consider buying FC 26 coins to give yourself an edge in building your Ultimate Team and dominating the competition! Are you ready for EA FC 26? Let us know your thoughts in the comments below!
    • https://maxcheaters.com/topic/253284-⭐l2off-h5-gx-ext⭐/
  • Topics

×
×
  • Create New...

AdBlock Extension Detected!

Our website is made possible by displaying online advertisements to our members.

Please disable AdBlock browser extension first, to be able to use our community.

I've Disabled AdBlock