Jump to content

Input: no quest running for pc, cannot process input : (char ID)


Go to solution Solved by Pepineitor,

Recommended Posts

Hi dear mt2 comunity i just want to know if someone knows this issue:


 

Input: no quest running for pc, cannot process input :

It appears when i kill another char. After that, no quest functions works for that char.


Here you have a bit more of the syserr.txt

 

SYSERR: Dec 11 18:35:57 :: Input: no quest running for pc, cannot process input : 61543
SYSERR: Dec 11 18:36:28 :: Input: no quest running for pc, cannot process input : 60963
SYSERR: Dec 11 18:36:30 :: Input: no quest running for pc, cannot process input : 60963
SYSERR: Dec 11 18:36:51 :: Input: no quest running for pc, cannot process input : 60275
SYSERR: Dec 11 18:37:06 :: Input: no quest running for pc, cannot process input : 59709
SYSERR: Dec 11 18:37:06 :: Process: UNKNOWN HEADER: 156, LAST HEADER: 254(2), REMAIN BYTES: 8, fd: 40
SYSERR: Dec 11 18:37:08 :: Process: UNKNOWN HEADER: 159, LAST HEADER: 254(2), REMAIN BYTES: 8, fd: 41
SYSERR: Dec 11 18:37:13 :: GetUniqueHpPerc: Unknown Key : fake6
SYSERR: Dec 11 18:37:13 :: PurgeUnique: Unknown Key or Dead: fake6
SYSERR: Dec 11 18:37:21 :: Input: no quest running for pc, cannot process input : 61743
SYSERR: Dec 11 18:37:23 :: GetUniqueHpPerc: Unknown Key : fake2
SYSERR: Dec 11 18:37:23 :: PurgeUnique: Unknown Key or Dead: fake2
SYSERR: Dec 11 18:37:23 :: GetUniqueHpPerc: Unknown Key : fake3
SYSERR: Dec 11 18:37:23 :: PurgeUnique: Unknown Key or Dead: fake3
SYSERR: Dec 11 18:37:33 :: IsUniqueDead: Unknown Key or Dead : real
SYSERR: Dec 11 18:37:53 :: Input: no quest running for pc, cannot process input : 60963
SYSERR: Dec 11 18:37:53 :: Input: no quest running for pc, cannot process input : 60963

The quest that im running for the player kill is something like this:

 

if npc.is_pc() then
	if pc.getqf("muertes1"..npc.get_vid()) == 3 then
		pc.setqf("delay", get_time()+60*5)
		pc.setqf("muertes1"..npc.get_vid(), 0)
		chat("Has matado 3 veces al mismo personaje.")
		chat("Ahora has de esperar 5 minutos!")
	else
		pc.setqf("muertes1"..npc.get_vid(), pc.getqf("muertes1"..npc.get_vid())+1)
		tienda_pvp.give_kill_event_price()
		if pc.level >= 80 then
			pc.give_exp2(390271992)
		end
          	if pc.get_empire() == npc.get_empire() then
       			local Achievement = "Enhorabuena!"				 
                        pc.setqf("muertes2", pc.getqf("muertes2")+5) 
	           	pc.setqf("muertes_totales", pc.getqf("muertes_totales")+1) 
	                cmdchat("achievement ".. Achievement .."_+_".. pc.getqf("muertes_totales") .."%".. pc.getqf("muertes2") .."")
		end

	end
end

I did "/reload q" before test the quest fucntion again.
If someone knows soemthing, i will be glad to listen to him/her <3





PD: The strange thing is that if i logout to the login window, and log in again, it doesnt work neither any quest function.
but when i log out completly, closing the metin2 client, and i open a new connection, it works all again perfectly... I really doesnt know where the hell the issue is :/

PD²: Is it possible that the PID of the bugged char is killed and that way the server says "no quest running for pc"?
cause only when i log completly again it works. When i kill somebody after that, it get bugged again :x

Link to comment
Share on other sites

  • Solution

You don't know how to use the npc.get_vid() function, here you have an example
 

quest test begin
	state start begin
		when kill with npc.is_pc() begin
			local vid = npc.get_vid()
			local old_pc = pc.select(vid)
			if old_pc != 0 then
				local lev = pc.get_level()
				local name = pc.get_name()
				pc.select(old_pc)
				chat("You killed: "..name..", level: "..lev)
			end
		end
	end
end

You want pc.get_player_id()

  • Love 1
Link to comment
Share on other sites

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now

Announcements



×
×
  • Create New...

Important Information

Terms of Use / Privacy Policy / Guidelines / We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.