Syreldar

Despite what the OP put as a solution, it's not possible for mysql to be at fault here. Lua errors are usually always quest-related, or at most source-related. In this case, he's attempting to call two missing functions from two different quests, so there's only two possible reasons for this. If the functions are locally implemented within the quests, he either called them as globals or with a wrong (different) name, or they don't exist altogether. If the functions are implemented source-side, he either called them using a wrong class or, again, with a different name, or they don't exist altogether. Either way, mysql has absolutely nothing to do with the likes of problems like these.

./qc path/to/quest/questname.extension

Because the number you see represents a quarter of the real drop percent. If you want an item to always drop, its drop pct should be 400, not 100.

Adapt your qc's sourcecode to support functions within trigger chat strings.

Metin2Dev's community doesn't offer support to leechers.

Insert a .quest file anywhere within the /quest folder. From there you may compile it singularly via terminal (./qc PATH/QUESTNAME.EXT), or you may batch-compile all of them by inserting them into the quest_list and using the make file. In order for a quest to work you may want to restart the server, however if it's not a new quest and you just made changes to it, you may also use the in-game command "/reload q" without running into issues.

special_item_group.txt Group 스폐셜 { Vnum 10050 -- type special -- 1 71148 100000 1 --Ring of Will Power 2 71149 100001 1 --Ring of Deadly Power 3 71158 100002 1 --Hero's Medal 4 71135 100003 1 --Crescent Moon Ring 5 71136 100004 1 --Mighty Lolly 6 71143 100005 1 --Ring of Joy 7 71145 100006 1 --Amulet of Eternal Love 8 71188 100007 1 --Magic Lolly 9 71199 100008 1 --Chocolate Amulet 10 71202 100009 1 --Nazar Amulet 11 72054 100010 1 --Amulet of the Guardians 12 76030 100011 1 --Power Lolly 13 76047 100011 1 --Power Lolly (3D) 14 72062 100012 1 --Experience Ring +200 15 72062 100012 1 --Experience Ring +200 16 72703 100015 1 --Tiger Bone Earring 17 72709 100015 1 --Tiger Bone Earring 18 72704 100016 1 --Dragon Bone Earring 19 72710 100016 1 --Dragon Bone Earring 20 72705 100017 1 --Tiger Bone Bracelet 21 72711 100017 1 --Tiger Bone Bracelet 22 72706 100018 1 --Dragon Bone Bracelet 23 72712 100018 1 --Dragon Bone Bracelet } -> 3 71158 100002 1 --Hero's Medal Group 속성3 { Vnum 100002 -- type ATTR -- 1 66 50 -- 2 64 30 -- 3 7 20 -- 4 9 20 -- 5 69 10 -- 6 70 10 -- effect d:\ymirwork\effect\etc\buff\buff_symbol1.mse -- }

I stumbled upon a customer that had this issue today. I was not aware that you posted a solution for it almost a year ago. This is the full Lua workaround I used for the guy, posting it here just for the sake of doing it. From my functions.lua: New functions: Usage example: You could also do this upon d.new_jump* call instead of onLogin.

Contact me on discord.

You either aren't compiling your stuff properly or forgot to reset the flag on your character.

pc.setqf("duration", ..) Remove this line.

Never bought a plane ticket faster.

when kill with not npc.is_pc() and math.random(100) < X begin game.drop_item_with_ownership(vnum, quantity); end -- when

send_letter_ex("Wow, this quest blinks!", "blink,ex", "scroll_open.tga");

"Lua is nice and good, but if you have bugs, you might need C++ to resolve the problem" It's true that certain complex bugs might require C++ work (They're so rare that the only example that comes to my mind over 10 years of development is this:) But you just cannot use that as a matter of fact when such an occurrence is that rare. I literally cannot think of any other issue that can't be solved directly without C++ work. "You can cause important errors in Lua and memory problems just like in C++" No. Unless you override entire classes like pc.* by assigning them to global variables and giving them arbitrary values, that's simply not possible. And such a gigantic mistake that can STILL be fixed in the blink of an eye, you can't say the same about C++ core crashes/memory issues. We both know that solving a generic Lua error (which still lets the game run with no issues) is much simpler than solving a core crash caused by shit C++ code made by people like you who force themselves to use it when they can't just cause "C++ is cooler / harder to use". "C++ is faster than Lua" Yes, but that doesn't matter on Metin2, due to the game's limitations, speed is not a factor: Two dungeons written in these two languages with identical code functionality will run exactly the same way and at exactly the same pace. Thus, you're wrong, you can't apply generic logic in this case. Also, while C++ is known for its speed, which again, is not a factor to take into account on Metin2, Lua offers remarkable flexibility, and C++ should be used to that end: To help assemble functions useable in Lua in order to write more complex stuff while maintaining Lua's ease to update/use; that's the whole point of scripting languages and it's the reason why YMIR adopted this design, why do you think they don't make dungeon in C++? The entire quest system has been made exactly to handle such things, and it's very much stable and safe to use, not to mention easy to use, as you said, but apparently for you "easy to use = bad" (?). Lua's straightforward syntax and semantics allow developers to implement features quickly and with fewer lines of code -> faster development cycles -> more productivity. Writing something in a harder way doesn't make it better at all. I don't know you but given the message I quoted, this doesn't seem a design choice/preference on your end to me, not as much as it seems a sorry attempt to flex and feel superior.. which you failed at miserably from what I see. I've coded much more complex stuff than this in Lua for Metin2 during my lifetime, stuff that I'm sure you can't even fathom, (For example, do you even know what a coroutine is and how to apply it on a Metin2 quest?) While this.. stuff that you made, once I remove the python UIs I get one of the most basic, boring and plain dungeons ever conceived. Be humble, and try to learn rather than trying to put other people down when you can't even defend your own competences properly. "Only Lua is easier to learn and anyone can be a Lua developer." True, it's easier to learn. You might want to start learning it, given your show of C++ knowledge today.