OSBot version number: 2.3.77

Description of the bug/error: Character#getInteracting always returns null

Instructions how to replicate the bug/error: Check what an attacking npc is interacting with

(IF APPLICABLE) SSCCE that causes the bug/error: N/A

(IF APPLICABLE) Script name ran causing the bug/error. Optionally include relevant parts of source code:

FrostBarrows

(IF APPLICABLE) Screenshots:

should be noted that it (for some reason) still works with myPlayer

Can we get an update on this bug? I have been unable to use this bot since that bug came up... 

I'll need to hide my script from the SDN fairly soon if I don't get an update on this..

 

The issue boils down to Client#getMyPlayerIndex being broken (always -1)

Edited July 5, 201510 yr by FrostBug

I was about to report the same bug today.

It does work sometimes for other players though.

 

any news on this?

 

Khaleesi

Edited July 5, 201510 yr by Khaleesi

I was about to report the same bug today.

It does work sometimes for other players though.

 

any news on this?

 

Khaleesi

 

it always works for other players

 

The issue is that the index of the local player is -1; so the thread title is a bit misleading

 

EDIT: I tried hooking the LocalPlayerIndex field according to rsh updater logs; and that too returns -1 .. this is strange

Edited July 5, 201510 yr by FrostBug

it always works for other players

 

The issue is that the index of the local player is -1; so the thread title is a bit misleading

 

Ow I see, I didn't test other players properly.

I just noticed that the monsters returned the right player if it was not my player.

 

Thx for clearing this out.

 

I hope this gets fixed quickly =)

 

Khaleesi

oh wow, no wonder my combat scripts are being heavily posted about, I would like to confirm this happens too with rock crabs

Edited July 5, 201510 yr by Czar

it always works for other players

 

The issue is that the index of the local player is -1; so the thread title is a bit misleading

 

EDIT: I tried hooking the LocalPlayerIndex field according to rsh updater logs; and that too returns -1 .. this is strange

 

 

try

 

myPlayerIndex ~ [FieldNode] Owner: client, Name: hf, Desc: I GetterModifier: 96403577

temp workaround:

 

	public Character<?> getInteracting(Character<?> c) {
		int uid = c.accessor.getCharacterFacingUid();
		if (uid == -1) {
			return null;
		}

		if (uid < 0x8000) {
			return getNpcs().getLocalNPC(uid);
		} else {
			uid -= 0x8000;
			Player player = getPlayers().getLocalPlayer(uid);
			if (uid == getClient().getMyPlayerIndex() || player == null) {
				return myPlayer();
			}
			return player;
		}
	}

 

Note, this temp workaround probably returns the local player in the case of an npc interacting with a player who isn't loaded (offscreen).. But I guess it will have to do for now

try

 

myPlayerIndex ~ [FieldNode] Owner: client, Name: hf, Desc: I GetterModifier: 96403577

 

That is the same as the rsh one. Aka. the one I tried
 

temp workaround:

 

	public Character<?> getInteracting(Character<?> c) {
		int uid = c.accessor.getCharacterFacingUid();
		if (uid == -1) {
			return null;
		}

		if (uid < 0x8000) {
			return getNpcs().getLocalNPC(uid);
		} else {
			uid -= 0x8000;
			Player player = getPlayers().getLocalPlayer(uid);
			if (uid == getClient().getMyPlayerIndex() || player == null) {
				return myPlayer();
			}
			return player;
		}
	}

 

Note, this temp workaround probably returns the local player in the case of an npc interacting with a player who isn't loaded (offscreen).. But I guess it will have to do for now

 

That is the same as the rsh one. Aka. the one I tried

 

 

works in my own private bot

works in my own private bot

 

you certain it isn't just returning -1?

you certain it isn't just returning -1?

 

 

http://i.imgur.com/6EXdart.png nope correct

http://i.imgur.com/6EXdart.png nope correct

 

Strange

 

I'll need to hide my script from the SDN fairly soon if I don't get an update on this..

 

The issue boils down to Client#getMyPlayerIndex being broken (always -1)

 

It was fixed at around 9AM PST.

I was told in the scripters' chat around that time. Sorry for the delay.