KrzychuG

I'd rather say it's due to XP x64 which is like a beta OS. TILEMACHOS .dll aint perfect and might simply not work in some cases. Most likely your OS just closes client while there's an error.

I doubt they even care at the moment. They have some serious issues with x15 server at the moment.

Well, the opposite. The L2 Tower or Clockmans Remote Tools as it was called previously worked and works fine under Windows 7. It's RPG-Club (and similar servers) problem only and it's the cracked nwindow.dll that causes the problem. As TILEMACHOS already said it's because of missing functions being called by system.dll that stays original by now. Suggesting to play with VMWare or VirtualBox is kinda pointless since you'll lose all of the performance and L2 already works like crap. So far hadrware acceleration on VMs is far from perfect. It's a matter of time till new protection goes live and possible to get some full "crack".

@TILEMACHOS, as far as i remember there was some ASM debug only and it was related to kernel32.dll. It actually crashes even without l2ul.dll in system/ dir, but yea, it's better to wait for new antibot and try to break it then.

Well, the software (.dll) works fine on Windows 7 (well, worked before updates). There's something wrong with "cracked" nwindow.dll TILEMACHOS provided and unless he figures out what can be wrong it won't work. I can eventually provide some debug info from Visual Studio, but not sure if it's worth too since RPG is going to update their antibot soon. As for TILEMACHOS, you can always virtualize Vista/Win7 for testing purposes only ;-)

What i said is based rather on OOG version and you won't be able to log and chat/move with that at the moment. Never really cared about IG version but i wouldn't exlclude that it has something to do with that packet changes as well. BTW, did you managed to get "clean" system.dll file as well or so far nwindow only? Just wondering if that rumours about l2r working with unpacked system.dll are true.

They changed some vital packets server-side which regular walker can't handle now. That's why trade/craft still work but nothing beside it. Even if you'll make l2w to "work" here again, you'd need a new script to wicked patcher. Don't wanna start a flame war for OS, but keeping a 10 years old, no longer supported OS isn't a better option, getting familiar with something new is fine, Win7 aint really that bad ;-)

Don't take posts on rpg forum seriously. If there would be working l2r you'd notice that on zranger forum as well. So far they're going into who brings the worst excuse of loosing some pvp.

BTW, adding a way to skip attacking flagged chars automatically would help as well.

Change the way drops pickup works (like pick all the drops then move to next mob or smth) cause with current version char running to mob and going back to pickup a drop is easy to spot and mark. Also adding some random delay to mob targeting would be fine since current version does that almost instantly and can look suspicious to other players. Not sure if anything can be done to chars stucking on trees/rocks but that's the issue as well. An admin manually checking chars will always find a bot tho, so still if you don't wanna get banned you should watch what your char is doing and react properly to situation (ie. admin porting you behing some obstacle). If it comes to ban, you were probably banned due to those shares here rather than for being detected in-game. I told you that releasing it under same name as account on rpg might end up like that. They were probably checking how's the progress with l2walker going, saw your soft working and boom.

Yet they found you and banned so either someone reported you or they checked that forums like i told you before. It's preety easy for players to spot a bot due to how it picks up items for example. Anyway, software is nice but it's missing few features like a summon auto attack for instance ;-) @Lain, no, there is no auto-spoil in it. In fact is preety simple fighters only bot with pet attack, drops pickup and auto hp pots features if it comes to exping. It has few more usefull functions usefull in pvp and they're posted here.

Well, the way you're going is much more complex and chronicle/throne dependant due to changes in the client and new features, skills and so on that has be added each time NCSoft adds something. What i thought sounds easier and a bit more complatible since these basic functions doesn't change that often. Just letting people to access client from the outside. If for example someone would like to have a CP clicker only he could read a max and current CP value and then tell the client to use a cp potion if needed, similiar thing for target change and so on. It would be an API with access to basic function that could be expanded in the future with new functions.

Actually, i never really got into l2walker and thought that in-game version uses rather packet snifing/modifying like l2net, l2r/l2c and similair. OOG version simply replaces the client so it's easier as well. What i mean, is to create a lib that could be a brige between client and some outside user interface. You could connect to that and control the game with that. You'd be able to read every info client has and run every function client allows. If someone wants a L2Walker like GUI, fine, if someone want's to control it via autohotkey/autoit for example, let's just allow him to connect and do that. Concept is simple if you got what i mean.

Wonder if it would be possible to create a lib that could work as an interface (with some protocol) that could be controlled by either some outside gui or from in-game. It could just give access to most important client functions/variables from outside and then preety much unlimited possibilities to be used with any language, even the scipting ones.

@TILEMACHOS, take a look at that post. There's a link do scode.zip that contain parts of code with hooking to client/onEvent function with two small examples. Code is incomplete but can be used to make something more usefull. You'll also need an easyhook lib.

I may be wrong on that one, but wouldn't patching the client to not load any custom, unndedded libs do the job? That software uses a name of some leftover .dll file that's not normally in the client and is loaded just because NCSoft was lazy and did not cleaned up the code.

There's some problem with installer: