LuaHobo

Alright, here’s the thread on MMOwned. LuaHobo is a program that allows you to execute protected Lua functions remotely, let’s see how long this one lasts.

Features:

• Executes Lua through FrameScript__Execute, thus executing ASM.
• Allows usage of protected Lua functions.

It’s a remote thread, contrary to Cypher’s LuaNinja, which I believe injected a thread and allowed the use of protected Lua functions in-game. This doesn’t, for clarity’s sake.

There is one issue though; it doesn’t always clean up properly.

Anyway, here’s the meat; credits to Shynd, Nesox and JuJu for aHook.

LuaHobo_20100114-2

Banwave ongoing

Right, looks like we have ourselves a proper banwave. This time, the target is presumably LUANinja by Cypher.

At first it was assumed this only affected Windows XP users, since Cypher doesn’t use this, compatibility would’ve been limited. However, Kynox stated:

Clarification (Updated):

Well, after searching around for a while with Harko; he found the culprit. He, being on Windows XP, ran his logger over LuaNinja.dll and found that it was in-fact reporting back detection flags. However, when i ran my logger over LuaNinja, it returned clean flags.

I run Windows 7, as does Cypher; which would appear to be how he missed the Windows XP incompatibility.

Long story short? LuaNinja’s protection only worked on certain operating systems and Warden has been detecting LuaNinja since December 19th.

Personally I have never ran LUANinja, but my own version of it instead. Suffice to say would be that none of the accounts I tested my program one got banned, so it has to be targeted at LUANinja in some way.

DeathKit 1.14

Well, I guess it’s time to throw this one at the public, and let it see some use.

Death Kit is a process managing application which shows the information the Task Manager can’t show you. This includes all the information you ever wanted to find about a process, such as:

• Window Title
• Handle
• Main Module
• Non-Paged Memory Size
• Paged Memory Size
• Peak Paged Memory Size
• Process Name
• Responding?
• Total Processor Time
• User Processor Time
• Virtual Memory Size

Also, it allows you to terminate any application at any given time. Instantly, as well as listing a heap of processes hidden in the Task Manager.

I’m also working on killing processes the hardcore way, through injection, but as that’s quite unstable at the moment, that may have to wait until future releases. However, 1.14 is stable, and even with the injection mode enabled, it won’t harm anything but itself (if things go south).

Download DeathKit 1.14

LUA DoString

Right, first off; credits for this fly out to Nesox and Shynd. They have both contributed greatly to me getting this implemented properly and working as it should. Check out Shynd’s post here on Object.Interact();, and search for Interact in the MES of MMOwned for Nesox’s part.

Now that we have that out of the way, let’s see what we are going to do with the code that comes out of this:

• Target the nearest enemy.
• CastSpellByID
• CastSpellByName
• AttackTarget (Similar to Object.Interact(), but only on mobs)

Find the nearest node

Greetings!

Two posts a few days away from each other, now that’s rare, isn’t it?

Anyway, I’ve seen quite some people having trouble figuring out which node (or any other object) is the closest to them.
As this is quite a substantial part of any proper working Gathering bot, or an addition to a farming bot, I thought we’d cover this subject.

C# login with PHP and MySQL

Greetings,

It’s been a while since I’ve posted here, so I decided it may be a good thing to come up with something proper this time around.
Today we’ll be covering login in C# with PHP and MySQL on a server, rather than implementing MySQL in our program, with all our credentials exposed.

As most of the time, credits for some of the code, and the basic how-to go to Nesox, so don’t forget about him.

Our PHP file will look something like this, it queries the MySQL server, and returns something in it’s main output stream.

Now, we can do several things in our C# project. One of the main things we will need is HttpUtility. This isn’t in your project, so you’ll have to set up an internal reference to it. (It’s in System.Web, and it can’t be inherited)

Personally, I like to set up a class which provides us with the username, password and all other stuff we’ll need in our login stuff, so I make a class which looks something like Class User. I make it internal so other applications which refer to our application can’t nib it off.

Then, we can use something like this to make a stream to the server, submit our credentials, and read from the stream.

When you have all that working, we can call something like _serverReponse.Contains(“AUTH OK”); to take a shortcut and see if the auth succeeded, or if it failed. (If it failed it won’t contain AUTH OK, so yeah) Or you could pull off some nifty stuff which is probably more secure and the lot, but I’m looking at this from an IJW perspective. (It just works!)

Until we meet again!

GSpellTimer

GSpellTimer, which Glider used extensively to measure cooldowns and the lot, has been “replicated” – well, not quite – to be used once more by the general public.

Now, the version by the BabBot team can be found here: http://pastie.org/723230
They implement every requirement for a properly working GSpellTimer, yet it doesn’t work. The main mistake is made in the isReady(); method – it doesn’t return true or false properly.

Now, the fix is quite easy. Make a bool IsReady, and use get/set{} to return true or false according to the situation. Make that go along with a bit of modifications in the core class, and you’re off.

I’ll post up a finite and properly working GSpellTimer class soon.

Move to target

Alright, today’s post is all about moving to your target.

If you’ve read my previous posts, you should already know how to get your target’s object, his position and all other attributes, as well as how to face a target, and determining the distance between you and the target. This method can be applied to mobs, but to waypoints as well. It’s going to be a pretty mandatory part of any functional bot.

The basic idea of it is as follows:

• Obtain our target.
• Obtain our target’s Vector3D location.
• Move to our target.

Oh, this post is pretty much putting the methods from my previous posts to use, nothing special at all.

Distance and facing

Many people are having a hard time on determining the distance and the facing required from one X,Y,Z to another, for example to a mob or to a waypoint.

However, both can be quite easy. We’ll be using Vector3D to determine the distance, and Shynd’s has written an excellent post on movement which includes how to face objects.  I’ll be providing some code to determine the distance between two points today.

Accessing the ObjectManager

So lately I’ve been reading up on every thread I could get my hands on on GD/MMOwned which would point me in the right direction to access WoW’s Object Manager.
If you wonder what the Object Manager – hereinafter OM – is, it’s a linked list which contains information regarding all objects in the game world.

Obviously, we are interested in having some information of the objects around us when making any sort of WoW bot/tool.  There are plenty of threads on MMOwned about people asking how to get their X,Y,Z co-ords. The OM is where you begin, get the OM, iterate through it, and then you will be able to find any object’s X,Y,Z, among other things.

As Shynd said before:

Other people, before you and me, have done the really hard work and we’re privileged enough to simply ride along atop their findings.  Never–and I mean never–let their work go unappreciated.

And I agree to this hands down. We’re in a state of welfare really.