[Request] Client Dev Help
6,799 topics in this forum
-
- 0 replies
- 440 views
-
-
-
- 6 replies
- 1.9k views
-
- 0 replies
- 598 views
-
- 4 replies
- 692 views
-
- 0 replies
- 936 views
-
- 2 replies
- 1.4k views
-
- 8 replies
- 3.1k views
-
- 1 reply
- 755 views
-
- 2 replies
- 1.4k views
-
- 2 replies
- 1.8k views
-
- 1 reply
- 968 views
-
- 3 replies
- 1.4k views
-
- 0 replies
- 959 views
-
- 11 replies
- 2.1k views
-
- 20 replies
- 4.4k views
-
- 3 replies
- 1.2k views
-
- 4 replies
- 1.6k views
-
- 4 replies
- 1.2k views
-
- 0 replies
- 475 views
-
- 0 replies
- 794 views
-
- 0 replies
- 683 views
-
- 0 replies
- 751 views
-
- 7 replies
- 1.4k views
-
- 1 reply
- 957 views
-
- 1 reply
- 611 views
-
- 5 replies
- 2.5k views
-
- 4 replies
- 1.1k views
-
- 10 replies
- 1.9k views
-
- 2 replies
- 1k views
-
- 0 replies
- 754 views
-
- 3 replies
- 1.4k views
-
- 6 replies
- 2.1k views
-
- 2 replies
- 1.1k views
-
- 3 replies
- 924 views
-
- 4 replies
- 1k views
-
- 4 replies
- 1.4k views
-
- 5 replies
- 3.2k views
-
- 3 replies
- 1k views
-
- 2 replies
- 717 views
-
- 3 replies
- 858 views
.thumb.jpeg.e31b56275d89d28924c19d901aab4670.jpeg)
_full.1355798.thumb.jpg.f79098ebd29ce2342600ea05690a4d4d.jpg)
-
Posts
-
There are a billion things that can cause this. Fucked up custom map, fucked up custom NPC, fucked up custom weapon, etc. There's no straightforward way to find out what exactly is causing it. And it is unrelated to memory itself. My advice: make a backup of your system first of all. Then, one by one, replace the dats on your system for the retail ones. First change: npcgrp, npcname run l2.exe and log in if it keeps crashing, go etcitemgrp, weapongrp, armorgrp, itemname if it keeps crashing, replace lineageeffect / lineageskilleffect, try again if it keeps crashing, replace 22_22.unr with the retail one in the maps folder etc etc etc that way you identify where the problem comes from. If it gets fixed when replacing npcgrp/npcname? then it's a custom npc fucking you up. Another, faster way, delete your whole system and try the retail system with modified l2.ini to be able to log in. If it still crashes, then it is an issue outside of the system folder. Replace the external folders one by one (animations, systextures...) -
-
By TheDarknessFear · Posted
Try edit l2.exe to use more memory. Should fix your issue. -
-
anyone work solution critical errors interlude? pm me discord @johnatainacio
-
-
Topics
-
