Lazarus1988

notice_all(string.format("Player %s is now banned", player_name_variable))

Try with my Exp Generator (source included, Run with Windows XP compability and with Admin rights) [Hidden Content]

If you have it in item_proto I assume it also is in item_proto in client, but You didn't tell if there laying coins any coins on ground when kill, or you have third hand (de)activated. Check now game client's item_proto for yang and try with third hand. If both fails you can do an override like this: quest drop_yang begin state __FUNC__ begin function DropYang(factor) return math.abs(npc.get_level()*number(factor, factor+100)) end end state start begin when kill witn not npc.is_pc() begin -- This will give you gold automaticly calculated by formula MobLevel * 1000 (e.g) -- from stray dog you will gain min:1000 yang and max 1100 yang local yang = drop_yang.DropYang(1000) pc.change_gold(yang) syschat(string.format("You have recieved %d yang"), yang) end end end

Check if you have in item_proto record "yang" with vnum = 1

This bug occurs when map dimmensions or base coordinates are diffrent on client side and server side. Check settings.txt of this map on server and compare with this in client, then you should check (usualy you can find it in root or locale package (depending of client version)) atlasinfo.txt for proper entries. ALL ENTRIES MY BE THE SAME in order to proper working map.

Tried with abs(int x) ? And this is my personal opinion, and question. Why you use so high values? Currently this looks... not nice. When I check the level how many exp I have to gain I can easly got lost when I see 189332244 or something like that. Try to write it that exp will looks like that 10000000. Write some constant base exp and increase it by some cool formula

Hello again... Yesterday I decided to test out guild wars on my server and I noticed strange thing. A player character sometimes when joins battle is not send directly to battlefield but send as Spectator (observer) thus game tells "There are no opponents and war will soon end" I wrote this function to join battle See full function. I've done some testings and this bug occurs when characters relogs after seeing a message about guild war... Let me describe more detailed: Guild "A" declares battle against Guild "B" and when war begins is so far ok, player can enter battle, but when player warps to other map (on the same channel) and then decides to enter war, he is sent as observer (Spectator). In order to enter battle he must quit observer mode and then he is correctly send to battle (and not always...) What is wrong with my function or this is internal game bug? I'm using game 34k from This server files

I gues you use game 34k or unbugged source, so I give you a tip, metin2 src doesn't like high values, so I suggest to use as low values as possible. It has some disadvantages, but it will prevent your project from unexpected "surprises"

It's definitly map's ID to high value. I had exact same problem.

Change map id to lower value. In my case this helped me. Try id lower than 150.

Just Add show/hide button and everyone will have option whetter to show coins or not.

when login with pc.get_map_index() == ox_map_id begin if pc.is_mount() then pc.unmount() end end

Hello again... Today I noticed my game client is missing horse skills... Of course as you can see only support skills are in non-standard positions and I'm 100% sure replacing support skills positions has absolutly nothing to do with it. Did any one had similar problem? I checked my playersettingsmodule.py file in root in function DefineSkillIndexDict() and all skills ID are in place, here's whole function PS for test purposes I added one horse skill into support skills section, but still with no results. def DefineSkillIndexDict(): global NEW_678TH_SKILL_ENABLE global SKILL_INDEX_DICT NEW_678TH_SKILL_ENABLE = locale.IsYMIR() if NEW_678TH_SKILL_ENABLE: SKILL_INDEX_DICT = { JOB_WARRIOR : { 1 : (1, 2, 3, 4, 5, 0, 0, 0, 137, 138, 139, 0, 0, 0,), 2 : (16, 17, 18, 19, 20, 0, 0, 0, 137, 138, 139, 0, 0, 0,), "SUPPORT" : (121,129,130,131,124,122,0,0,123,), }, JOB_ASSASSIN : { 1 : (31, 32, 33, 34, 35, 0, 0, 0, 137, 138, 139, 140, 0, 0,), 2 : (46, 47, 48, 49, 50, 0, 0, 0, 137, 138, 139, 140, 0, 0,), "SUPPORT" : (121,129,130,131,124,122,0,0,123,), }, JOB_SURA : { 1 : (61, 62, 63, 64, 65, 66, 0, 0, 137, 138, 139, 0, 0, 0,), 2 : (76, 77, 78, 79, 80, 81, 0, 0, 137, 138, 139, 0, 0, 0,), "SUPPORT" : (121,129,130,131,124,122,0,0,123,), }, JOB_SHAMAN : { 1 : (91, 92, 93, 94, 95, 96, 0, 0, 137, 138, 139, 0, 0, 0,), 2 : (106, 107, 108, 109, 110, 111, 0, 0, 137, 138, 139, 0, 0, 0,), "SUPPORT" : (121,129,130,131,124,122,0,0,123,137,), }, } else: SKILL_INDEX_DICT = { JOB_WARRIOR : { 1 : (1, 2, 3, 4, 5, 0, 0, 0, 137, 138, 139, 0, 0, 0,), 2 : (16, 17, 18, 19, 20, 0, 0, 0, 137, 138, 139, 0, 0, 0,), "SUPPORT" : (121,129,130,131,124,122,0,0,123,), }, JOB_ASSASSIN : { 1 : (31, 32, 33, 34, 35, 0, 0, 0, 137, 138, 139, 140, 0, 0,), 2 : (46, 47, 48, 49, 50, 0, 0, 0, 137, 138, 139, 140, 0, 0,), "SUPPORT" : (121,129,130,131,124,122,0,0,123,), }, JOB_SURA : { 1 : (61, 62, 63, 64, 65, 66, 0, 0, 137, 138, 139, 0, 0, 0,), 2 : (76, 77, 78, 79, 80, 81, 0, 0, 137, 138, 139, 0, 0, 0,), "SUPPORT" : (121,129,130,131,124,122,0,0,123,), }, JOB_SHAMAN : { 1 : (91, 92, 93, 94, 95, 96, 0, 0, 137, 138, 139, 0, 0, 0,), 2 : (106, 107, 108, 109, 110, 111, 0, 0, 137, 138, 139, 0, 0, 0,), "SUPPORT" : (121,129,130,131,124,122,0,0,123,137,), }, }

Yes. I suggest to use in quests with biolog additional flags like pc.setqf("BiologDone", 1) (wich means the quest is done) at the end of mission so you could use query like this: DELETE FROM `player`.`quest` WHERE `szName` LIKE "%Biolog%" OR `szName` LIKE "%biolog%" AND `szState` = "BiologDone" AND `szValue` = 1; There is also another way, probably you're using navicat, so running custom query like this one: SELECT * FROM `player`.`quest` WHERE `szName` LIKE "%Biolog%" OR `szName` LIKE "%biolog%"; will show all quests related to "biolog" and you can simply select with your mouse records wich you want to delete and do it with simple DEL key stroke (preferable way) Another think, any third party modifications on database should be done on killed "game" and "db" processes. PS witam kolegę z Polski

Nope, I have few players and nobody reached even 30lv, thanks @VegaS for update