Recent content by lafreak

Yes, and if I remember correctly, there was plenty of kal mechanics implemented in this repository, but not even close to full kal support

You must be registered for see element.

Here is yet another take on my emulator for kal: You must be registered for see element.

Dude, you're the guy who stole my website htmls/css which I have stolen from lineage2 private server. Then you've been spamming my fanpage to remove the site because I rip it from you. You couldnt even see there are still lineage references in html... xD I don't think people should take you...

Since I'm in possession of VPS, I came up with idea to open test server based on emu files. :p It's running on files from branch You must be registered for see element. so you could test packet handling with one thread before merge with master. Download 18.10.2017 client: You must be registered...

What "Start" you talk about? Just tested it again and it still works for me, inix did not change anything: You must be registered for see element. Do packets reach mainserver? What does mainserver say? It should look like this when you select server: You must be registered for see element.

Inix changed packet headers once again. Should not be hard to fix it. I've managed to get old packet headers client with shaman, because they released it by mistake. xD But it's good to update headers anyway, for further client updates.

It's \r\n / \r line ending differences, madnight wants to fix it with his latest commit he did 1h ago

@spicman I was trying to reproduce your error, and the only time I get it, it's when I do not specify schema: You must be registered for see element. You must be registered for see element. You must be registered for see element. You must be registered for see element. You must be...

Looks like a problem with mysql connection string. I've made small change here: You must be registered for see element. Pull latest commit, rebuild and tell me if it's working. Your error comes from libzdb: You must be registered for see element. Looks like it cannot find schema? Are you sure...

@RevEngKal Justei madnight Threadless packet handling, using You must be registered for see element.. You must be registered for see element. Still needs improvements, refactoring and few fixes, but works as proof-of-concept.

Yes I agree with you, threads need to be replaced. Purpose of light client was not to prove threads work, I made it in 2016 and I think it's still nice to have. :P madnight asked me to release it, he wants to move it to linux and make automated client-server tests.

I've made command line client that connects with my emulator (some call it clientless?). You can stress/load test this emulator now, looks like it handles 90 clients very well. :P It makes random movement and auto accepts party. Repository: You must be registered for see element. You must be...

What am I missing here? What would be another aproach? Maybe its not that much of restructuring. :p

Animal transformation restricted area?