The NPC did not respond. On route.

Private server support - Only post connectivity issues in the subforum!

Moderator: Moderators

Message
Author
Mortimal
Developers
Developers
Posts: 389
Joined: 01 Nov 2008, 15:31
Noob?: No

The NPC did not respond. On route.

#1 Post by Mortimal »

I am plaing in private server and using smsing like that in portals.txt:

Code: Select all

prontera 154 187 comodo 213 141 0 c r2 c r10 c r0
But every time Bot tries to respond to npc i get:

The NPC did not respond.

Strange but doing the same with console commands:

Code: Select all

talk cont
talk resp 2
talk cont
talk resp 10
talk cont
talk resp 0
or using macro like this:

Code: Select all

do talk cont
pause 1
do talk resp 2
pause 1
do talk cont
pause 1
do talk resp 10
pause 1
do talk cont
pause 1
do talk resp 0
is working fine! BUT!

using macro like:

Code: Select all

do talknpc 154 187 c w1 r2 w1 c w1 r10 w1 c w1 r0
I got the same result:

The NPC did not respond.


Logicaly the problem is in Tasks/TalkNPC.pm But i can't understand where it is :(
Please use pin function for uploading your file contents!

Mortimal
Developers
Developers
Posts: 389
Joined: 01 Nov 2008, 15:31
Noob?: No

Re: The NPC did not respond. On route.

#2 Post by Mortimal »

soooo.... i tryed to locate the problem some-how... and i did UNFORGIVEN!!!!!

just kidding. I did this:

Code: Select all

blahblahblah...
} elsif ( $step =~ /c/i ) {
			# Click Next.
			if ($npcTalkType eq 'next') {
				#$messageSender->sendTalkContinue($self->{ID});
				Commands::run("talk cont");
....blahblahblah
ad u know... it freaking worked! i was shoked a little bit o_O...


And than i understand - "OMG this man has incorrect $self->{ID}"

And my Question is Why it has incorrect $self->{ID}? because, i cant understant...
Please use pin function for uploading your file contents!

EternalHarvest
Developers
Developers
Posts: 1798
Joined: 05 Dec 2008, 05:42
Noob?: Yes

Re: The NPC did not respond. On route.

#3 Post by EternalHarvest »

Maybe there is more than one NPC (or more than one NPC ID) in this talk sequence. Every part of NPC dialog from the server includes NPC ID. Commands like "talk cont" would use the most recently received ID ($talk{ID}), but Task::TalkNPC uses one ID for the whole sequence.

Task::TalkNPC should be fixed by making it to send $talk{ID} instead of $self->{ID} everywhere except for "x" step.

Mortimal
Developers
Developers
Posts: 389
Joined: 01 Nov 2008, 15:31
Noob?: No

Re: The NPC did not respond. On route.

#4 Post by Mortimal »

Changed it, all works just fine!!! Thx for your help.
Please use pin function for uploading your file contents!

EternalHarvest
Developers
Developers
Posts: 1798
Joined: 05 Dec 2008, 05:42
Noob?: Yes

Re: The NPC did not respond. On route.

#5 Post by EternalHarvest »

Don't forget to commit fixes.

ever_boy_
Developers
Developers
Posts: 308
Joined: 06 Jul 2012, 13:44
Noob?: No

Re: The NPC did not respond. On route.

#6 Post by ever_boy_ »

EternalHarvest wrote:Task::TalkNPC should be fixed by making it to send $talk{ID} instead of $self->{ID} everywhere except for "x" step.
what line exactly is this?

Mortimal
Developers
Developers
Posts: 389
Joined: 01 Nov 2008, 15:31
Noob?: No

Re: The NPC did not respond. On route.

#7 Post by Mortimal »

fix already comited... 8220
Please use pin function for uploading your file contents!

ever_boy_
Developers
Developers
Posts: 308
Joined: 06 Jul 2012, 13:44
Noob?: No

Re: The NPC did not respond. On route.

#8 Post by ever_boy_ »

oh thanks

Post Reply