Can someone show me an example how to use flymode()? I type it in and then what? flyup(1) does nothing... Thanks.
Last edited by rockman319; 05-17-2009 at 11:27 PM.
FlyMode if part of the client. its the developer fly mode. They left it in the client. Chances are high, that activating it might flag you as a developer, but i've not checked for this. So i suggest you better don't use it on any account you care fore. lucky for you this was only a trial account.
All my trial accounts expired the normal way though and i used to fly alot, so maybe you where just reported.
In Dark Age of Camelot they where sending the fly-bit to the server once my hack was available for it. Its funny how sites took over my hack as 'their hack'.
What I did in DAoC after that was simply change the compare of the fly bit. They never really checked for code-changes in DAoC (dont know why).
Have to say though that it was a ton more useful in DAoC then it ever was in WAR. You could kill monsters while flying, no "target cant reach you" bull.
For those of you who feel like donating:
http://warextdll.prophp.us
Its a free hoster, so it will be a bit slow. I'am thinking about early access for donators after patches.
I just googled for warextdll, seems like some other exploit pages are offering it as well ( who would have guessed ), but charge for membership to download.
Also i just took a quick peek at the testclient for 3.1. Looks like another week of reversing after the patch is released. I'am not gonna start now, i'am sure they fix stuff until the offical release.
Last edited by HansW; 05-18-2009 at 05:08 AM.
great, gonna give this a go![]()
New release - Version 0.97
- Needed for the final release of BotPoc.
- Fixed some outputs and routine
- Added a new WriteMemEx function ( try WriteMemEx(#0xd3d4fc+0x2C,4,15000) )
- ReadMem and WriteMem will crash the client sooner or later (WriteMemEx does not)
Why do ReadMem and WriteMem (have chance to) crash the client but WriteMemEx does not?
I dont know what "WriteMemEx(#0xd3d4fc+0x2C,4,15000)" does... 0x2c offset is player Z is it not? what about the other 2 parameters...
What is the syntax?
WriteMemEx(address as hex, ?? as ??, ?? as ??)
I'm trying to do Wallhack
0x00506F89 0xeb7a
for the syntax to most commands, just use it without any parameters. you will see a help text in the console window.
The "#" means , get the value at that address. so for #0xd3d4fc it reads the actual pointer to the player object.
the second parameter is the type of the value : 1=BYTE 2=WORD,3=DWORD,4=FLOAT.
so the wallhack should work like : WriteMemEx(0x00506F89,3,0xeb7a)
there is no # here, because 0x00506F89 is already the address that we want to write to.
Ok thanks I'll try that... I did use WriteMemEx() but I didn't get any help text in console window (console here means the extender right, not the war, ie: in-game?)
So wouldn't "WriteMemEx(#0xd3d4fc+0x2C,4,15000)" causes your char Z to be 15k (very very high up)?
When I put that in DrifterBars as button four, click it, it does nothing...
Maybe I did something wrong.
This works very well, good work on it. I didn't have any trouble injecting it on Windows Vista 32-bit Home. Hope to see a lot of future addons with this library.