Would it be possible with OpenGL to dump a list of all item ids? And if so would they be the same as the reflection ID's? Like tomato = 1982
Just curious :)
Printable View
Would it be possible with OpenGL to dump a list of all item ids? And if so would they be the same as the reflection ID's? Like tomato = 1982
Just curious :)
I'm not sure, but you can get item ID's from the runescape site on the grand exchange. They were the same as reflection id's when I lasted scripted for reflection bots, though it might be different now. I can actually see how I could extract every item id matched with a name, if it would be useful I would do it for you.
The problem with that is it only has Item that can be traded on the GE. Other Items suck as the Charms and quest Items can't.
You could generate a checksum of the item image, and use that as an ID. You cannot connect the items with OGL to their actual (reflection) ID though.
I'm currently working on this with my TRiBot OGL hook.
TribotOGL hook sounds like sexy stuff, talk to me about dis shiz?
When will that be working? Going to be publicly released and stuff?
So far, I've made it able to identify screen models, and get colours of pixels. I wrote some code to somewhat identify inventory items, but its not fully functional yet, since I only had a few hours to work on it. I'm going to be working on it a lot during Christmas break (starting tomorrow) though, so I should get a lot done. I'm not planning on releasing my work, but I'll probably make posts about how to do stuff.
Is it called tribot because you're TRileZ!?
Was this ever released before? I've heard of a tribot bot before was that also you?
So not releasing it as in not releasing the souce?
Gonna have a website for it And let users use it? Or not releasing it at all?
Was an RS OGL bot ever released? Nope, all I have as a reference is Silentwolf's interception source.
Before the bot nuke, TRiBot (developed by me) was a fully functional - public - reflection bot, but I'm now making it an OGL + colour bot.
I will be releasing this at http://tribot.org once I'm able to get a beta going, but I won't be releasing the source.
Nice! That sounds awesome, and I totally agree with you not releasing the source.
I'd keep it contained to a small # of people and authed.
You might create another reflection era! Exciting though!!!
Not to totally derail this thread, but how do you propose Jagex isn't going to easily detect your ogl hook? Would it not be easy for them to see what modules you have injected into the game and then kick you out if you're using anything that's accessing "private" information? Or change the offsets every update?
I'm not gunna say I'm a pro at OpenGL hooking.. But I've done it before.. The way it works is that you redirect the functions your hooking, into a memory location.. Then you MUST re-write the bytes back or else you get detected.
So.. lets say you read a value of 5 into memory..
you must then write that value back.. There's different ways to hook really. Depends what your trying to do.. I know nothing of the RS client :S But for counterstrike and stuff I can hook that.
I've only done d3d hooking on source engine, no ogl though. Both are able to be detected no matter what you do, only VAC scans for signatures and uses delayed ban methods. They can't just block every module (like PB tries to do), but with RS being on Java there shouldn't be many 3rd party modules loaded unless the user has a very broken PC, am I right? And they still could change the offsets (or whatever ogl calls them) every 6 hour update if they don't want to bother with detecting stuff?
Yah your absolutely right that they can detect it no matter what.. Well as far as I know anyway.. They can change whatever they want.. the thing with OpenGL is that they'd actually have to change their models and objects.. which is quite a tedious job for game developers.. thats quite a lot of work to do just because someone smart hooked their client. They can prob just do what vac does..
Every time I've ever hooked, I've gotten my steam account banned except one time which I don't know why :S The reason I said you'd have a harder time being detected by writing back is because jagex can easily read back the data and check to see what's different or what not.. It's kinda why I'm scared to test Silent Wolf's plugin because of the Overlay thing.. He even said it's detectable but not at the time in which he wrote it.
Process attach
Hook Function
WriteBack
Detach.
I've been looking around and this method is said to hide the DLL (works with VAC). http://www.openrce.org/blog/view/844/How_to_hide_dll
I am pretty sure that method is detected by "VAC3". Not that Jagex would have the time/care to make such an anticheat.
Though how do you plan to handle the offsets (or whatever they are called in OGL)? Jagex could change those every update, just like how I assume they do with Reflection (mixing along with their other methods). Some simple seds throughout the code automatically every automatic update they force.
Keep me posted on any updates, seems interesting :)
Yes it indeed has offsets.. but I don't think you need to hook those. Just hook the functions that get called.. I guess for Finding NPC's you'd actually have to hook an offset. Then again they can just hook the models and thats all thats needed as offsets can change any time jagex wants and that would be hell for botters to re-compile a plugin every update for new offsets.
See Here: http://www.opengl.org/sdk/docs/mangl...herOffsets.xml
Here's my progress with identifying inventory items:
http://img705.imageshack.us/img705/9...ldec312011.png
It generates constant IDs, and is based on shape detection since the colours of items shift. Therefor, items with the same shape will have the same ID.
Would that not mean that two players looking the exact same with the same clothes n skin colour and what not would have the same ID?
P.S. Those ID's are HUGE!!! Lol..
Sum the colors of the IDs and add that as an "extra" ID next to the original ID separated by a : or something? :) or have the average R value of the colors after the : or whatever
multiple solutions to the common ID problem