911reg

Go ingame > alt + g > UI > look for the windows: PCViewerWnd for items, MSViewerWnd for skills

try this one instead. The one he shared affects every single NPC/player character in the game, the one I posted only affects player characters https://drive.google.com/file/d/1UtccbD9e50x3WEnQBab2PTZnBHwpcGYM/view?usp=sharing or perhaps i misunderstood; if you could please post a full explanation of the problem you're having with the files, unfortunately i think whatever you're using to translate to english is a bit bad nevermind, i got what you mean, here's the fix https://drive.google.com/file/d/1av7OHaGSdnVQtcBgb9MhtiIkxVXy3P2y/view?usp=sharing CanIngnoreCollision=True CanBeIngnoredCollision=True

yup basically another one just in case https://drive.google.com/file/d/1UtccbD9e50x3WEnQBab2PTZnBHwpcGYM/view?usp=sharing LineageWarrior.FMagic (CollideActors = True; > False) LineageWarrior.FOrc (CollideActors = True; > False) LineageWarrior.FShaman (CollideActors = True; > False) LineageWarrior.MDarkElf (CollideActors = True; > False) LineageWarrior.MDwarf (CollideActors = True; > False) LineageWarrior.MElf (CollideActors = True; > False) LineageWarrior.MFighter (CollideActors = True; > False) LineageWarrior.MMagic (CollideActors = True; > False) LineageWarrior.MOrc (CollideActors = True; > False) LineageWarrior.MShaman (CollideActors = True; > False) LineageWarrior.FDwarf (CollideActors = True; > False) LineageWarrior.FElf (CollideActors = True; > False) LineageWarrior.FFighter (CollideActors = True; > False)

i'll give it a shot in a few hours and post it here

I believe this can be achieved with a client mod actually. What client are you using?

I have it but kim jong un won't let me share it

This is actually very interesting, i've seen similar concepts applied to different games (even single-player games such as skyrim with PrismaUI Prisma UI - Next-Gen Web UI Framework at Skyrim Special Edition Nexus - Mods and Community ) if it works seamlessly with the client then it would be insane. I believe everyone is tired of getting cancer with xdat/flash/.uc edits

HAHAHAHAHAHAHAHAHAHAH

There was an urgent l2.exe update some days ago from the aac team regarding a new w11 update that breaks l2.exe

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...)

i'm in

even the fucking post is AI, insane

fixed in dms

if it's in newer clients you need a mix of both server and interface work, since the CollidingActors function was removed from the game apparently (if i'm not mistaken) ? so you can make a small interface implementation that just sends a server bypass to the server, and the server activates an abnormal either way you'll probably need: 1. Interface work 2. Server Source work 3. new emitters in .u files / abnormal dat changes (in case you want new effects) should be able to make it fully client-sided in pre-h5 clients though

i was playing around with this a while back, it's pretty nice, and since it's mostly .ini configs i'm pretty sure it could be integrated into interface.u easily what i'm not sure about is wether or not reshade is safe to use in older hardware (i.e. if the client would crash on startup on an old shitty pc like it tends to happen with dxvk) Imgur: The magic of the Internet

Aguante lulú

you need to move the contents of the staticmeshes/maps/textures folders of the respective screens and replace your existing files. If you are using interlude, you need to rename the .unr file to lobby.unr first. Or conversely if the file is already named lobby.unr and you wanna use it on h5, you rename it to lobby01.unr. Some might work, some might not, it's trial and error. Make backups of your client.

@Vraekar

Sadly we gotta choose between poop and shit, it is what it is.

I'm on that same situation, but hey after almost 3600 commits it's almost playable!

(a bit ironic that you're writing these comments using AI lmao)