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 (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

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.


×
×
  • Create New...