"when kill begin" doesnt work with regen but works with spawned mobs (/m 8001)

[asdasd1234 11]

Hi!

 

I have a bug with my stonemap dungeon quest code.. i have this code:

		when kill with d.getf("nv") == 1 begin
			if pc.get_map_index() >= 4000000 and pc.get_map_index() < 4010000 then
				if d.count_monster() == 0 then
					d.notice("You Killed all Monster. You will teleport in 5 Seconds to Stage 2.")
					timer("get_out_dung_stonea", 5)
					d.setf("nv", 2)
					d.clear_regen()
					d.kill_all()
					clear_server_timer("leave_trt_fv", d.get_map_index())
				end
			end
		end

i kill all the stones and it doesnt trigger the d.notice()

when i spawn one more after ingame that one triggers..

when i spawn one with all the others alive, still not triggers.. what should i use to trigger the kill function?

[Foxxielove 32]

Try it with a short timer

Edited March 17, 2025 by Foxxielove

[Ace 4629]

ChatGPT:

 

Spoiler

Your issue is likely due to how d.count_monster() functions. The problem is that d.count_monster() may still be returning a non-zero value even after you kill all the stones, meaning the condition inside your if statement never evaluates to true.

Possible Solutions:

Use a Debug Notice to Check d.count_monster() Before your if d.count_monster() == 0 condition, add a debug notice:

when kill with d.getf("nv") == 1 begin
    if pc.get_map_index() >= 4000000 and pc.get_map_index() < 4010000 then
        d.notice("Remaining Monsters: "..d.count_monster()) -- Debugging
        if d.count_monster() == 0 then
            d.notice("You Killed all Monsters. You will teleport in 5 Seconds to Stage 2.")
            timer("get_out_dung_stonea", 5)
            d.setf("nv", 2)
            d.clear_regen()
            d.kill_all()
            clear_server_timer("leave_trt_fv", d.get_map_index())
        end
    end
end

This will show the actual monster count in real time.

Introduce a Short Delay Before Checking d.count_monster() Sometimes, Metin2's system does not immediately update d.count_monster(). You can add a small delay:

timer("check_monsters", 1)

And then create a separate event to check if d.count_monster() == 0 after a short delay.

Track Monsters Manually Instead of relying on d.count_monster(), you can track the remaining monsters manually:

when kill with d.getf("nv") == 1 begin
    if pc.get_map_index() >= 4000000 and pc.get_map_index() < 4010000 then
        local remaining = d.getf("monster_count") - 1
        d.setf("monster_count", remaining)
        d.notice("Remaining Monsters: "..remaining)
        if remaining <= 0 then
            d.notice("You Killed all Monsters. You will teleport in 5 Seconds to Stage 2.")
            timer("get_out_dung_stonea", 5)
            d.setf("nv", 2)
            d.clear_regen()
            d.kill_all()
            clear_server_timer("leave_trt_fv", d.get_map_index())
        end
    end
end

At the start of the dungeon, you should initialize d.setf("monster_count", total_monsters_spawned).

Summary:

Use d.notice() to debug d.count_monster()

Add a slight delay before checking d.count_monster()

Manually track monster count using d.setf()

Try debugging first to see if d.count_monster() updates correctly. Let me know what the debug output says!

 

[asdasd1234 11]

debug was a cool idea, the monster count was crazzzzy ..

with a 5sec timer it works perfectly fine

 

thank you for your help