Gurgarath

Nice release, really convenient, great job!

Hi, Check your syserr, some effect file is missing

#Moved.

Exactly, that's why I said "2014+" because nova added some bugfixes and a "ratio system" which is interesting but not effective because of the way the game update things. You're completley right

You can already run the server on Windows though

You did a great job and a great service to the community. That's a big thank you!

I said everything in the main post and in the comments, I will try to straighten that out for everyone: I have everything from the latest gf client. Skill_table and msa files included. About your question it must be 750 serverside or something like that. Just read what my code do, if you can shoot it from anywhere, you probably have skill files prior to the patch 17.5. In that case, this "fix" is useless for you as you have, I quote: My fix is for people having the latest client and the latest skill_table. I should have mentioned it but as I already sent a gif and a description of the bug, it's up to everyone to decide whether they need the fix or not. At last but not least, I've never encountered any of the bugs aforementioned, however, I can't try right now. I will try as soon as possible to reproduce the "double triggering" bug. If it happens, I will fix and share it with everyone there. However, our friend OtherChoice already gave us a fix as well as a wonderful explaination. To answer him, the "worked-around" files are probably client skill data files prior to 17.5, which I simply didn't know as I had no way to test. In the meantine, a little NB was added in the main topic. Regards,

I wanted to join the course but he scammed me and took my serverfiles to put systems on WoM² is it a masterclass??? help me pls @ASIKOO @PACI

No you can't, you will walk onto the target and launch the skill. About the double triggering, it has already been stated. It is related to the file "yongpa(_2,_3,_4).msa". if you launch the skill from afar, it's related to this file as well. I stated that this has been tested with the latest official files.

Hey, You better remove these tags really quick, thank you

Really good point here. Even if I like the race. It's true that everytime they add a new race in a modern (or even in a older) MMORPG, it comes with a lore, things to do, a new continent, quests, systems, abilities. The only thing that we had was poison 2.0 and a flying pooch with the ability to buff all of his allies at once. Not even talking about the little bits of lore we have or the map. Even the original lore in Metin2 is not so developped. I completely get your point

Technically, yes, but it's not a porting, good point though. If you want a real porting, you first need to compile all the libraries under linux, then to compile the game and db themselves on Linux. You don't have a lot to change on the architecture itself, but be ready to potentially mess with FDWatch. About the client, you can't. You probably can run it with Wine though. If you want to natively use it on Linux, consider changing DX8 to something like OpenGL (which would, if done correctly, make the game better looking as well).

Can you please give me the answer so that you won't get a warning?

If you speak about an item, just type /i "Name of the item" and it will give it to you! Same goes for mob. Don't forget the ". Also, shortcuts like /m "Orc Ch work as well.

Exactly! I got this crash from this quest but I decided not to mention it because I was unsure if it was sg material or official material. The fact that the check wasn't done quest-wise made me think about sg material. In reality it was ymir who did that shit... I didn't mention the lua fix because as long as the core can crash I prefer fixing the crash, I fixed the quest right after however. But that's a good point you made! Thank you VegaS! Also, nice rewrite and nice usage of ternary conditions, I kept my fix simple but yours is more efficient. Completely... I got two of them in only a few days (including this one). We should maybe keep a global post categorizing all of these. I don't know why they kept all of these flaws.

Hello guys, While trying things on my server, I stumbled accross a weird core-downer. It is really simple but I say "weird" because in litteraly 10 years it has never happened to me nor anyone I know. It probably gets triggered by a malfunctioning quest I had taken from 2012 and forgot to remove (quests were not my concern at the time). I didn't want to only remove the quest but instead I decided to fix the coredowner. It happens because the game is not expected to trigger the function get_leader_vid() without a party. However, there is no check at all if it somehow did and on my server it randomly got triggered without a party and the core simply crashed. So instead of digging further, I thus added a check to avoid the core to crash. Please note that my sources were vanilla at that time. Well, head to questlua_npc.cpp and find the function "npc_get_leader_vid". It should normally look like this: //Function "npc_get_leader_vid" { CQuestManager& q = CQuestManager::instance(); LPCHARACTER npc = q.GetCurrentNPCCharacterPtr(); LPPARTY party = npc->GetParty(); LPCHARACTER leader = party->GetLeader(); if (leader) lua_pushnumber(L, leader->GetVID()); else lua_pushnumber(L, 0); return 1; } Then simply check if "party" exists or not; it should look like this: [Hidden Content] Here you are, note that the coredowner is rare, but it can happen so it's better to avoid it.

Sometimes it seems like people can't get knockbacked anymore. Try to attack mobs from your horse to see if they get pushed when you hit them (not when they die). Otherwise the knowkback will only make the people fall. IsStone() and return false; but it seems that it was already fixed in the original code. if (pkChrVictim->IsRaceFlag(RACE_FLAG_METIN)) fknockbackLength = 0;

In the video it has nothing to do with alpha nor beta skill window. You tried but it is slightly different in reality. Alpha (a bit different, bigger and with slots): [Hidden Content] Beta : [Hidden Content]

King's move, we need more guides like that, I abide, well done friend!

I completely agree with you, and you did a great work, respect! To be fair, the reason I focused my attention on serverside and completely ditched clientside was because of the latest gf client. Using the most recent client containing all of the 17.5 updates and newer, I expected client datas to be tested thoroughly and to be bug-free (as it was working already on official server) and then I just tried to remove every mismatch I got between official clientside and my seemingly outdated serverside. By the way, I think the "worked-around" version is on every client having pre 17.5 skilltable and that's why no one had to worry. The bug described in my post seems to occur only on post 17.5 skilltable. I also want to say that this bug occured with matching serverside and clientside skilltable, that's when I started to look into server sources and found the problem I described. Here's how I came up with this fix (or work-around actually). I will try to test about the double computation of the skill as well, but I didn't see it when I tested it at first.

This is called "ShopEx"

Hello friends, While I was adjusting my skills and doing some updates to them, I encoutered a funny bug I had never noticed. I asked my friends and tried some servers and they either had this bug or they had it "fixed" already. I didn't try the official but they surely patched it in 17.5NB. You will see that when you use this skill, two things can happen based on your server: Your character will walk toward the ennemy and launch the skill. The skill will hit the target but nothing will happen. No processing, no damage, no aggro, simply nothing. The skill will be effective only at point blank range. Screencap below. You will launch the skill as long as you have an attackable opponent targeted. That's the "fix" I talked about, which is more like a workaroundNB. Preview of the bug: [Hidden Content] (Thanks @Veltor88) This is an easy fix that probably anyone can come up with, but I would like to share it with you, let's make the game better for everyone. Open Server/char_battle.cpp and search for the following case in class CFuncShoot: case SKILL_YONGBI: { m_me->OnMove(true); } break; Delete the case. It simply makes you move to the target, launch the skill and that's it. Probably an unfinished piece of code that made it's way to the final game. Search for (in the same class): case SKILL_TUSOK: case SKILL_BIPABU: case SKILL_NOEJEON: case SKILL_GEOMPUNG: case SKILL_SANGONG: case SKILL_MAHWAN: case SKILL_PABEOB: And extend the check with: case SKILL_YONGBI: //Fix for Shooting Dragon Now your character will walk to the ennemy, launch the skill and deal damages as well as triggering the aggro and stuff like that. NB: The bug highlighted in the screecap was made and reproduced on the latest official client (as of February the 20th). A matching 17.5 skilltable (client->server) was also running at that time. The "work-around" I mentioned is surely happening if you have skill datas prior to the patch 17.5 as it was probably how the skill was back then and how it was intended to work. It might seem odd anyway and you might want to fix it. Also, you may encounter a "double-triggering" bug when launching the skill at point black. For those two cases, I forward you to this great post, giving you a fix. I don't know if I have this bug (and will provide you with all the necessary files if I happen to have it). I didn't do any checks on the clientside as I was simply trusting Ymir and using latest (supposedly working and tested) skill datas both serverside and clientside. Enjoy!

Hello fellow M2Dev companions, I come here today to ask you a simple but hard question at the same time. I'm asking for your thoughts about Lycan. I will try to make it short, but I also need to ask you things. From everything I heard it was either neutral, either extremely positive or extremely negative at the same degree. Some people said to me that if Lycan was added on a server, they would simply not try the server. Some others said that the bonuses or the race itself was too unbalanced while the last category of people said that it was really great and added freshness to the game without being too OP or too shitty and that no one is forced to play it. I think the hate from this race came from three things: We all felt weird about this race at first and the lore was weird at first glance, but now that it's fully implemented on official, with his maps, it's just some kind of an alternate start with side lore that is pretty good at what it does without being too much (unfortunately?). The fact that it adds a new race and that hence "perfect pvp stuff" is not a thing anymore made a lot of PvP players upset. The fact that most of these people tried this race at first on horrendous Pservers who were not able to adjust the race properly and did a weird unbalanced OP / Shitty character and therefore people hated the race just because of their first impression. I remember that when I proposed Lycan with the latest official statistics (from early 2015) from beta people were not playing it because of this. Now that the Lycan is 5 years old (Time flies) and that official adjusted it and adjusted the PvP balance in 17.5, some people are still reluctant to play it on Pserver and some owners just simply don't add it. This is one of the most unpopular update from official. Do you have any opinions on this? I also include a poll on the post

LPDIRECT3DTEXTURE8 > LPDIRECT3DTEXTURE9