Jump to content

Crash d.unique_is_dead


Recommended Posts

  • Active Member

Hey everyone! 

I am having an error with dungeons that have d.unique_is_dead() function, in this case the catacombs, when clicking the 30103 (after destroying the doors).

This is the debug core crash:
spacer.png
 

Edited by Metin2 Dev International
Core X - External 2 Internal
Link to comment
Share on other sites

  • Developer

It seems a bad use from quest, anyway, you can check the ptr before use

bool CDungeon::IsUniqueDead(const std::string& key)
{
	auto it = m_map_UniqueMob.find(key);
	if (it == m_map_UniqueMob.end())
	{
		sys_err("Unknown Key or Dead : %s", key.c_str());
		return true;
	}

	return it->second ? it->second->IsDead() : false; // 0x0 check
}
  • Good 1

503953077003354113.png

Link to comment
Share on other sites

  • Active Member
11 hours ago, Endymion said:

But this is not a problem in this case. Is CHARACTER removed from the unique map when killed?

This is the case when I destroy the gates that are set to unique d.set_unique in the catacombs quest aswell when spawned and then when click in 30103 (turtle), it checks if they are dead and its in that point that crashes.

Link to comment
Share on other sites

  • 4 months later...
  • Active Member

Solved! 

Was a problem on the dead function, was deleting the mob from the dungeon before I check if exists and then he was on the map of the dungeon declared but the mob it self didint have anything causing crash on game.

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.