Jump to content

Recommended Posts

Posted
7 hours ago, eressea said:

 

Yes, but don't forget to run both server and client without cliext protection enabled.

 

As for malformed crests it's not so easy to test (the easiest way I've found is by using patched engine.dll that just cripples the crest data enough before sending them to server) and it doesn't do anything wrong on the server itself (you even won't see any error message, server doesn't check what's in crest data, it just saves it and later sends it to other players) - it just crashes all clients that try to load the malformed crest as a texture via D3D (e.g. chars who see someone from that clan) - also it's easier to fix by patching the client d3ddrv.dll to not throw exception but ignore the texture error and leave crest white.

 

EDIT: Oh crap, I forgot this is about Vanganth IL, not GF - the skill enchant type error isn't present there (because there were no skill enchant types in C4 core, it's implemented in the extender). But the second bug with crests exists and can be fixed with this patched d3ddrv.dll (Interlude).

 

Thanks for you shares and insights !

Posted
3 hours ago, sepultribe said:

@eressea I am continuously amazed by your broad knowledge of things, not only coding, also networking and driver patching :) Thanks for being here and sharing it with us

 

d3ddrv.dll isn't driver, it's just rendering interface for Unreal Engine (it can also render via opengl or software renderer if I remember correctly, but NCsoft used only Direct3D interface)

  • Upvote 1
Posted
22 hours ago, eressea said:

 

d3ddrv.dll isn't driver, it's just rendering interface for Unreal Engine (it can also render via opengl or software renderer if I remember correctly, but NCsoft used only Direct3D interface)

 

yes I didn't mean device driver, meant a "3d graphics API" driver, as even the filename implies (Direct3d driver). It's the exact version of the D3D library the developers of L2 targeted isnt't it? I have seen people call them drivers for the post dx8 versions of the dlls (d3dx9_xx/d3dx11_xx)

  • 3 weeks later...
Posted (edited)

Hello guys. I've got a question, in order to replace the DLL file that Pulentolento was talking about, what do i have to compile? Little help here, i'm new in L2OFF developing. Thanks guys. 

Edited by rutake
  • 2 weeks later...
Posted

first - you take cliext.dll, throw it in the trash, and never speak of it again cuz its a garbage dll which vanganth should be ashamed of creating

 

alternatively you set the MD5Checksum in IlExt.ini for your new dll

  • 2 weeks later...
Posted
On 2/15/2018 at 8:53 AM, Anarchy said:

first - you take cliext.dll, throw it in the trash, and never speak of it again cuz its a garbage dll which vanganth should be ashamed of creating

 

alternatively you set the MD5Checksum in IlExt.ini for your new dll

It's better than completely nothing.

But it's not good enough for decent server.

Posted
On 15.02.2018 at 5:53 PM, Anarchy said:

first - you take cliext.dll, throw it in the trash, and never speak of it again cuz its a garbage dll which vanganth should be ashamed of creating

 

alternatively you set the MD5Checksum in IlExt.ini for your new dll

It's not a trash, you're missing the point of this dll, first of all this dll isn't an anti bot, it's main goal was to extend l2 client functionality (example auto potions, new shots, custom packets, version control etc), the antibot was just an add-on (due to it's popularity it got cracked pretty fast, same as every single other anti bot engine). This dll is a mess (that's the word that describe it better) never had a time for refactoring it so there's a lot of chaotic/unused code, anyway it did it's job perfectly (with such low costs). @Anarchy feel free to fix it up and share your great results with community ;)

 

KeyGenerator engine has been made just for one customer so i know who leaked it, no hard feelings wish you best.

 

As i can see it's been almost half year since these sources were shared. How many public patches are there to fix it up ? I found just ONE fix in this thread (thx to eressea). That's pretty sad, it perfectly describes the community - everyone would like to take but so few would give. I don't remember adding any backdoor to the sources, that would be just unfair in my opinion. The thing that server crashes upon some circumstances means there's a bug that needs to be fixed, just it. So if it crashes for you just fix it, it's easy (you can find 90% of crash issues in LinError.txt, the other 10% can be fixed with windbg or other debugger attached to l2server), if you don't know how to fix it even with the extender source code then you shouldn't play with L2OFF platform.  If you want to you can always rent a developer with asm/c++ experience (+reverse engineering), pay him 45+$ per hour and he'll make you brand new extender (maybe with less amount of bugs) after ~1050 hours.

 

Wish you all the best, have a nice days!

 

  • Like 1
  • Thanks 2
  • Upvote 3
Posted (edited)

I knew Vanganth for some time and he always delivered excellent results, his extender was very stable on those old days with more than 3000 online people and must say without restarts in weeks, maybe the code is a bit messy as he say but his logic is excellent. Thanks for the good times!

Edited by Nisker
  • 2 weeks later...
Posted
On 04/03/2018 at 4:46 PM, Vanganth said:

It's not a trash, you're missing the point of this dll, first of all this dll isn't an anti bot, it's main goal was to extend l2 client functionality (example auto potions, new shots, custom packets, version control etc), the antibot was just an add-on (due to it's popularity it got cracked pretty fast, same as every single other anti bot engine). This dll is a mess (that's the word that describe it better) never had a time for refactoring it so there's a lot of chaotic/unused code, anyway it did it's job perfectly (with such low costs). @Anarchy feel free to fix it up and share your great results with community ;)

 

KeyGenerator engine has been made just for one customer so i know who leaked it, no hard feelings wish you best.

 

As i can see it's been almost half year since these sources were shared. How many public patches are there to fix it up ? I found just ONE fix in this thread (thx to eressea). That's pretty sad, it perfectly describes the community - everyone would like to take but so few would give. I don't remember adding any backdoor to the sources, that would be just unfair in my opinion. The thing that server crashes upon some circumstances means there's a bug that needs to be fixed, just it. So if it crashes for you just fix it, it's easy (you can find 90% of crash issues in LinError.txt, the other 10% can be fixed with windbg or other debugger attached to l2server), if you don't know how to fix it even with the extender source code then you shouldn't play with L2OFF platform.  If you want to you can always rent a developer with asm/c++ experience (+reverse engineering), pay him 45+$ per hour and he'll make you brand new extender (maybe with less amount of bugs) after ~1050 hours.

 

Wish you all the best, have a nice days!

 

many envious will always look for defects in everything you do instead of doing something better so never stand out at all because they spend their time waiting for the other to fall to be on the same level.

  • 3 weeks later...
Posted

1>------ Build started: Project: KeyGenerator, Configuration: Release Win32 ------
2>------ Skipped Build: Project: NpcExt ------
2> 
1>Linking...
1>fatal error C1900: Il mismatch between 'P1' version '20060201' and 'P2' version '20050411'
1>LINK : fatal error LNK1257: code generation failed
1>Build log was saved at "file://c:\Users\victo\Downloads\Vanganth_Sources_ILExt\KeyGenerator\Release\BuildLog.htm"
1>KeyGenerator - 1 error(s), 0 warning(s)
3>------ Skipped Build: Project: IlExt ------
3> 
========== Build: 0 succeeded, 1 failed, 2 up-to-date, 2 skipped ==========

 

alguém sabe como resolver?

Posted
19 hours ago, victor33 said:

1>------ Build started: Project: KeyGenerator, Configuration: Release Win32 ------
2>------ Skipped Build: Project: NpcExt ------
2> 
1>Linking...
1>fatal error C1900: Il mismatch between 'P1' version '20060201' and 'P2' version '20050411'
1>LINK : fatal error LNK1257: code generation failed
1>Build log was saved at "file://c:\Users\victo\Downloads\Vanganth_Sources_ILExt\KeyGenerator\Release\BuildLog.htm"
1>KeyGenerator - 1 error(s), 0 warning(s)
3>------ Skipped Build: Project: IlExt ------
3> 
========== Build: 0 succeeded, 1 failed, 2 up-to-date, 2 skipped ==========

 

alguém sabe como resolver?

 

Did you try "Rebuild Solution"?

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



  • Posts

    • rly swired...leave low npcmakers ,its worked..not crash L2server.exe.   A:I:S:E:PE:DI:DE:BO=1.000000:1.000000:1.000000:1.000000:1.000000:0:0:0 L:Y:X:H=0:0:0:0:0 Crashed Thread[6]. Server Up Time : Wed Oct 15 13:11:08 2025 Current Time : Wed Oct 15 13:13:35 2025 Elapsed Time : 0 days 0 hours 2 minutes 27 seconds IOBufferPool - 39989 / 40000, PendingWrite 0 bytes [0] =============== object report user[0/0], npc[820/0], item[0/0], usersocket[0] =============== npc server connection log Connect : Wed Oct 15 13:13:34 2025 [(16328) 2025/10/15 13:13:35]: ======================= an Access Violation in module L2Server.exe at 0033:00518eef. start at 2025/10/15 13:11:08 Read from location ffffffff caused an access violation. Registers: EAX=0003dc7b CS=0033 EIP=00518eef EFLGS=00010207 EBX=a2228c44 SS=002b ESP=7da7f870 EBP=00000000 ECX=0003dc7b DS=002b ESI=00000000 FS=0053 EDX=00400000 ES=002b EDI=0c200dc0 GS=002b Bytes at CS:EIP: 48 8b 0c f0 80 79 5d 00 74 23 44 39 69 10 7f 1d Stack dump: 7da7f870: a2228c44 00000000 0004c158 00000000 009b2a10 00000000 00400000 00000000 7da7f890: 00000001 00000000 00000000 00000000 fffffffe ffffffff 00000000 40cae180 7da7f8b0: 00000000 40d11740 00000000 c0b1be00 00000000 00000000 00000000 00000000 7da7f8d0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 7da7f8f0: 3b19e2dc 00000000 0078e4c8 00000000 3b19e2dc 00000000 00400000 00000000 7da7f910: 0004c158 00000000 00000000 00000000 00000000 00000000 006c688a 00000000 7da7f930: a2228c44 00000000 00000000 00000000 00000000 00000000 00a2aa10 00000000 7da7f950: 012e6dc0 00000000 9beaee10 00000000 00000000 00000000 0004c158 00000000 7da7f970: 00000000 00000000 00a12d50 00000000 fffffffe ffffffff 0064dd24 00000000 7da7f990: fffffffe ffffffff 00000000 00000000 00000000 00000000 00000000 00000000 ver = Dec 16 2005_22:03:13 GuardInfo : IOThread [0][63] (good): void IOThread_common(void *arglist) -> bool NpcEnterWorldPacket(NpcSocket* pSocket, const unsigned char *pPacket) Lock Stack : IOThread [1][63] (good): void IOThread_common(void *arglist) -> bool NpcEnterWorldPacket(NpcSocket* pSocket, const unsigned char *pPacket) Lock Stack : IOThread [2][78] (good): void IOThread_common(void *arglist) -> bool NpcEnterWorldPacket(NpcSocket* pSocket, const unsigned char *pPacket) Lock Stack : IOThread [3][47] (good): void IOThread_common(void *arglist) -> bool NpcEnterWorldPacket(NpcSocket* pSocket, const unsigned char *pPacket) Lock Stack : IOThread [4][78] (good): void IOThread_common(void *arglist) -> bool NpcEnterWorldPacket(NpcSocket* pSocket, const unsigned char *pPacket) Lock Stack : IOThread [5][78] (good): void IOThread_common(void *arglist) -> bool NpcEnterWorldPacket(NpcSocket* pSocket, const unsigned char *pPacket) Lock Stack : IOThread [6][78] (ahehe): void IOThread_common(void *arglist) -> void CIOObject::TimerDispatch(bool bRootLoop) -> void CThreadLocalTimer::Dispath -> void CEnterWorldSerializer::TimerExpired(int id) -> void CNPC::EnterWorld(bool bSetDefaultParam, int nHP, int nMP) -> CCreature::EnterWorld Lock Stack : .\NpcSocket.cpp(278[116]) IOThread [7][78] (good): void IOThread_common(void *arglist) -> bool NpcEnterWorldPacket(NpcSocket* pSocket, const unsigned char *pPacket) -> void Push(int index, int x, int y, int z, int dir, int nSetDefaultParam, int nHP, int nMP) Lock Stack : .\NpcSocket.cpp(389[185]) ListenThread [13][141] (good): void ListenThread_common() -> unsigned __stdcall WaitThread(void *) Lock Stack : MainThread [12][156] (good): Lock Stack : GuardInfo end [(16328) 2025/10/15 13:13:35]: *.\ioc.cpp:648(Tue Dec 13 02:52:40 2005) exception  
    • We can help your Telegram channel, group, bot, or account appear first in Telegram search.   Our safe Telegram SEO service helps you rank your Telegram channel or bot for any keyword in just 72 hours.   No spam, no fake traffic — only real Telegram keyword ranking using premium user signals and smart optimization.   ✅ What We Offer • Top 1 Telegram Search Ranking Service (Channels · Groups · Bots · Accounts) • Rank Telegram channel, group, or bot safely with real engagement • Appear first in Telegram search for your target keyword • Pay-per-keyword with refund-backed guarantee • Global targeting (USA, EU, India)   🧩 Works Best For • Projects that need to appear first in Telegram search • Brands, crypto/NFT groups, trading or SaaS communities • Bot owners who want ranked visibility for their bot • Channels and groups needing more exposure   💡 Why Choose Us   We use safe Telegram SEO techniques — not spam — to deliver fast, stable Telegram top search results.   Our process helps your project gain organic visibility and steady traffic from real Telegram users.   📩 To Get More Information   Telegram: @TeleLoopPulse   Website : https://telegramgrowthstudio.com/telegram-search-ranking.html
    • leave only Npcpos the gremlins (for testing).
  • 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