Any chance you could fix the abyss objects? By fix I mean the client doesn't pick them up at all.

 

I used this to determine whether the objects were there:

@ScriptManifest(name="randObjectLogger", author="Rand", version=1.0D, info="Logs all object names")
public class logObjects extends Script{

	public int onLoop() {
		try {
		for (RS2Object obj : this.client.getCurrentRegion().getObjects()) {
			log(obj.getName());
			Thread.sleep(1000L);
		}
		} catch (Exception e) {
		}
		return 100000;
	}
	
}

And this was the return:

 

http://gyazo.com/0f3d5119a9f5410d7932775485f88d4d

 

Hopefully you can implement these fixes as fast as possible.

 

Thanks.

 

- Rand.

 

EDIT: Forgot to add that it seems like the ID's alternate and here is the entity debugger printscreen of one of the passages: 

 

Edited June 10, 201312 yr by Rand

Don't they still have id's attached to them? So just use the id's?

Don't they still have id's attached to them? So just use the id's?

 

Should have added, the ID's alternate, from what I see anyway.

The ID's alternate because they use so called configs to be set, this is for them to alternate the objects and also a nice feature to prevent botting. You will have to work out the bits in the bitset of the configs to find out the pattern to determine the actual identity of the objects. Also, their names are actually the string "null". Nothing of what you posted are errors or bugs, the names are stored as "null" strings in the cache and their id's and appearance are shuffled by configs.