Enlighten me, please :) explain how it won't work. How different is it from dynamic tilesQuote:
Originally Posted by drags111
Printable View
Enlighten me, please :) explain how it won't work. How different is it from dynamic tilesQuote:
Originally Posted by drags111
The reason they have dynamic tiles is because it's what's called an instance location. They have static locations such as the entire world map, and this allows for allthe users to be together in the world. If they sent you to an instance every time yOu logged on then you wouldn't be able to see anyone else. It just doesn't make sense that they would so that.
They could potentially change the tile IDs every day or so, though.
You're suggesting dynamic everything. Now, if it was dynamic everything, how would the client even know when you clicked something? If the location the object was on must have moved by the time you clicked it, I suppose the client thinks you're walking now...Very good, you've managed to shut down all bots. Color and reflection alike. Heck, even legit players can't play properly. (Obviously this is an exaggerated case of dynamicness)
The client still needs to have way ways to determine an event. Jagex can create new fields for identifying objects (they'll still need to be able to get information from the cache), but it means reflection can still get it...
If the client "knows" something, reflection can get it (provided its not a local field).
This.Quote:
Originally Posted by pyroryan
EDIT: @Flight: Current bots that use injection: powerbot, rsbuddy, runedev, and epicbot.
Oh wow. I wonder how they're planning to get that information and what they're going to do with it. Didn't they already try to take down Impsoft and lost? Seems like the usual exaggerated Jagex bullshit that they pull out of their ass to keep legit players happy.Quote:
we have also taken steps to acquire the details of all players who have purchased bots.
Nicely stated pyroryan :) Rep+Quote:
Originally Posted by pyroryan
~BraK
You told me earlier Powerbot was reflection.
I guess I've misspoke then, not so much doing something about reflection but an obtained client that's directly loaded rather than through the Runescape website.
As far as Awkwardsaw's points, I can back him up in that. I've noticed in a few places both Object tiles and Object IDs are dynamic. Take the Abyss for example, say the ID for the crawl space (Agility) is... 4321 at tile 3200,4300..., the next time you enter the abyss that same tile might have no object at all, and that specific ID (4321) might be the ID for distraction eyes, so nothing is static, the only definite way to search for what you're looking for is Model ID's, if you can track those on the mini-map then that'd be great...
This is also done in the Livid Farm and I assume it's the same in the newly release Jadinko Lair.
Right and like I said, those are Instances. That can exists within instances because its not the static "world of runescape." Outside an instance, find me a dynamic object.Quote:
Originally Posted by Flight
EDIT: Also when did i tell you powerbot was reflection...
If we can't search by ID or Tile, how would we find them? Can we find an object on the mini-map by searching just for the model ID?Quote:
Originally Posted by drags111
Ah i meant to say injection, typo. And what you said earlier was you were going to stop using object finding all together. You didn't say only in this scenario. And there are probably some wall objects that are static in there you could use as a reference. Remember, there are more than just interactables you could search for.Quote:
Originally Posted by Flight
I'm working on a solution to the abyss issue (should also apply to Livid Farm). Drags111 is testing the fix atm.
Edit:
SecondLevelObject.getChangingIDs (modelReferenceID? I need a better name) should solve the issue. Preliminary testing is successful for abyss.
Edit 2:
Abyss eyes:
Trip 1: changingID = 7168;
Trip 2: changingID = 7168;
Looking good.
Edit 3:
All of them match according to Drags.
Hooks file updated.
I guess if by "dynamic" you mean that the objects' appearance can be changed during runtime, you're correct. Many npcs and objects have varying appearances based on the value of a particular setting. Farming patches work that way, and your objects in the abyss are no different.Quote:
Originally Posted by Flight
No, they're not.Quote:
Originally Posted by drags111
I was saying the Object ID and Tile will vary, for example, every trip into the Abyss. Are you referring to that or to their Model ID as being the appearance?Quote:
Originally Posted by Method
You load the area up and things are loaded dynamically (even just the portals) so what you see isn't exactly what everyone else sees, so in a way, kind of is.Quote:
Originally Posted by Method
@Flight: At any rate we found the solution so you can once again not worry about using objects. Pyro found a hook that stays static even on those "dynamic" objects.
In all likelihood, neither will change. Here's the information you should need to figure out which object is which:Quote:
Originally Posted by Flight
Code:7142:
-- name: "Blockage" or "Rock" or "Tendrils" or "Boil" or "Eyes" or "Gap" or "Passage" or "Broken rock" or "Chopped tendrils"
-- 21 parent(s): [7156, 7158, 7161, 7165, 7168, 7164, 7154, 7164, 7168, 7165, 7161, 7158, 7159, 7160, 7162, 7163, 7166, 7167, 7169, 7170, -1]
--- Blockage, Rock, Tendrils, Boil, Eyes, Gap, Passage, Gap, Eyes, Boil, Tendrils, Rock, Rock, Broken rock, Tendrils, Chopped tendrils, Boil, Boil, Eyes, Eyes, null
-- vbidx: 625
--- vb: bits 18 to 29 of setting [491]
-- sidx: -1
7143:
-- name: "Rock" or "Blockage" or "Tendrils" or "Boil" or "Eyes" or "Passage" or "Broken rock" or "Chopped tendrils"
-- 21 parent(s): [7158, 7156, 7158, 7161, 7165, 7168, 7158, 7154, 7158, 7168, 7165, 7161, 7159, 7160, 7162, 7163, 7166, 7167, 7169, 7170, -1]
--- Rock, Blockage, Rock, Tendrils, Boil, Eyes, Rock, Passage, Rock, Eyes, Boil, Tendrils, Rock, Broken rock, Tendrils, Chopped tendrils, Boil, Boil, Eyes, Eyes, null
-- vbidx: 625
--- vb: bits 18 to 29 of setting [491]
-- sidx: -1
7144:
-- name: "Tendrils" or "Rock" or "Blockage" or "Boil" or "Passage" or "Broken rock" or "Chopped tendrils" or "Eyes"
-- 21 parent(s): [7161, 7158, 7156, 7158, 7161, 7165, 7161, 7158, 7154, 7158, 7161, 7165, 7159, 7160, 7162, 7163, 7166, 7167, 7169, 7170, -1]
--- Tendrils, Rock, Blockage, Rock, Tendrils, Boil, Tendrils, Rock, Passage, Rock, Tendrils, Boil, Rock, Broken rock, Tendrils, Chopped tendrils, Boil, Boil, Eyes, Eyes, null
-- vbidx: 625
--- vb: bits 18 to 29 of setting [491]
-- sidx: -1
7145:
-- name: "Boil" or "Tendrils" or "Rock" or "Blockage" or "Passage" or "Broken rock" or "Chopped tendrils" or "Eyes"
-- 21 parent(s): [7165, 7161, 7158, 7156, 7158, 7161, 7165, 7161, 7158, 7154, 7158, 7161, 7159, 7160, 7162, 7163, 7166, 7167, 7169, 7170, -1]
--- Boil, Tendrils, Rock, Blockage, Rock, Tendrils, Boil, Tendrils, Rock, Passage, Rock, Tendrils, Rock, Broken rock, Tendrils, Chopped tendrils, Boil, Boil, Eyes, Eyes, null
-- vbidx: 625
--- vb: bits 18 to 29 of setting [491]
-- sidx: -1
7146:
-- name: "Eyes" or "Boil" or "Tendrils" or "Rock" or "Blockage" or "Passage" or "Broken rock" or "Chopped tendrils"
-- 21 parent(s): [7168, 7165, 7161, 7158, 7156, 7158, 7168, 7165, 7161, 7158, 7154, 7158, 7159, 7160, 7162, 7163, 7166, 7167, 7169, 7170, -1]
--- Eyes, Boil, Tendrils, Rock, Blockage, Rock, Eyes, Boil, Tendrils, Rock, Passage, Rock, Rock, Broken rock, Tendrils, Chopped tendrils, Boil, Boil, Eyes, Eyes, null
-- vbidx: 625
--- vb: bits 18 to 29 of setting [491]
-- sidx: -1
7147:
-- name: "Gap" or "Eyes" or "Boil" or "Tendrils" or "Rock" or "Blockage" or "Passage" or "Broken rock" or "Chopped tendrils"
-- 21 parent(s): [7164, 7168, 7165, 7161, 7158, 7156, 7164, 7168, 7165, 7161, 7158, 7154, 7159, 7160, 7162, 7163, 7166, 7167, 7169, 7170, -1]
--- Gap, Eyes, Boil, Tendrils, Rock, Blockage, Gap, Eyes, Boil, Tendrils, Rock, Passage, Rock, Broken rock, Tendrils, Chopped tendrils, Boil, Boil, Eyes, Eyes, null
-- vbidx: 625
--- vb: bits 18 to 29 of setting [491]
-- sidx: -1
7148:
-- name: "Passage" or "Gap" or "Eyes" or "Boil" or "Tendrils" or "Rock" or "Blockage" or "Broken rock" or "Chopped tendrils"
-- 21 parent(s): [7154, 7164, 7168, 7165, 7161, 7158, 7156, 7164, 7168, 7165, 7161, 7158, 7159, 7160, 7162, 7163, 7166, 7167, 7169, 7170, -1]
--- Passage, Gap, Eyes, Boil, Tendrils, Rock, Blockage, Gap, Eyes, Boil, Tendrils, Rock, Rock, Broken rock, Tendrils, Chopped tendrils, Boil, Boil, Eyes, Eyes, null
-- vbidx: 625
--- vb: bits 18 to 29 of setting [491]
-- sidx: -1
7149:
-- name: "Gap" or "Passage" or "Eyes" or "Boil" or "Tendrils" or "Blockage" or "Rock" or "Broken rock" or "Chopped tendrils"
-- 21 parent(s): [7164, 7154, 7164, 7168, 7165, 7161, 7164, 7156, 7164, 7168, 7165, 7161, 7159, 7160, 7162, 7163, 7166, 7167, 7169, 7170, -1]
--- Gap, Passage, Gap, Eyes, Boil, Tendrils, Gap, Blockage, Gap, Eyes, Boil, Tendrils, Rock, Broken rock, Tendrils, Chopped tendrils, Boil, Boil, Eyes, Eyes, null
-- vbidx: 625
--- vb: bits 18 to 29 of setting [491]
-- sidx: -1
7150:
-- name: "Eyes" or "Gap" or "Passage" or "Boil" or "Blockage" or "Rock" or "Broken rock" or "Tendrils" or "Chopped tendrils"
-- 21 parent(s): [7168, 7164, 7154, 7164, 7168, 7165, 7168, 7164, 7156, 7164, 7168, 7165, 7159, 7160, 7162, 7163, 7166, 7167, 7169, 7170, -1]
--- Eyes, Gap, Passage, Gap, Eyes, Boil, Eyes, Gap, Blockage, Gap, Eyes, Boil, Rock, Broken rock, Tendrils, Chopped tendrils, Boil, Boil, Eyes, Eyes, null
-- vbidx: 625
--- vb: bits 18 to 29 of setting [491]
-- sidx: -1
7151:
-- name: "Boil" or "Eyes" or "Gap" or "Passage" or "Blockage" or "Rock" or "Broken rock" or "Tendrils" or "Chopped tendrils"
-- 21 parent(s): [7165, 7168, 7164, 7154, 7164, 7168, 7165, 7168, 7164, 7156, 7164, 7168, 7159, 7160, 7162, 7163, 7166, 7167, 7169, 7170, -1]
--- Boil, Eyes, Gap, Passage, Gap, Eyes, Boil, Eyes, Gap, Blockage, Gap, Eyes, Rock, Broken rock, Tendrils, Chopped tendrils, Boil, Boil, Eyes, Eyes, null
-- vbidx: 625
--- vb: bits 18 to 29 of setting [491]
-- sidx: -1
7152:
-- name: "Tendrils" or "Boil" or "Eyes" or "Gap" or "Passage" or "Blockage" or "Rock" or "Broken rock" or "Chopped tendrils"
-- 21 parent(s): [7161, 7165, 7168, 7164, 7154, 7164, 7161, 7165, 7168, 7164, 7156, 7164, 7159, 7160, 7162, 7163, 7166, 7167, 7169, 7170, -1]
--- Tendrils, Boil, Eyes, Gap, Passage, Gap, Tendrils, Boil, Eyes, Gap, Blockage, Gap, Rock, Broken rock, Tendrils, Chopped tendrils, Boil, Boil, Eyes, Eyes, null
-- vbidx: 625
--- vb: bits 18 to 29 of setting [491]
-- sidx: -1
7153:
-- name: "Rock" or "Tendrils" or "Boil" or "Eyes" or "Gap" or "Passage" or "Blockage" or "Broken rock" or "Chopped tendrils"
-- 21 parent(s): [7158, 7161, 7165, 7168, 7164, 7154, 7158, 7161, 7165, 7168, 7164, 7156, 7159, 7160, 7162, 7163, 7166, 7167, 7169, 7170, -1]
--- Rock, Tendrils, Boil, Eyes, Gap, Passage, Rock, Tendrils, Boil, Eyes, Gap, Blockage, Rock, Broken rock, Tendrils, Chopped tendrils, Boil, Boil, Eyes, Eyes, null
-- vbidx: 625
--- vb: bits 18 to 29 of setting [491]
-- sidx: -1
pssshh.. my script is almost entirely math based... lets see if they can break that:P
lolz...Quote:
Originally Posted by Jagex
Yay Jagex is cleaning up the bots so more $$$ and EXP for us! :D
IF they actually clean up the bots. Chances are they wont succeed :P