TMP4

Maybe you missing some image file, the tutorial does not include the images. It's in your syserr.txt if that the case. Take them from here: [Hidden Content] (Otherwise still check syserr.txt, it will still writes what your error is)

Please send me your edited char_item.cpp (you can use pastebin.com)

It's disabled by default and It's in game.py def UpdateDebugInfo(self). You probably compiled the binary in debug mode. Use distrubute instead. (Visual studio, select the solution in the right, then change from "debug" to "distribute in the top left.)

@FBSD_1.6 means FreeBSD13.0 (where you compiled the game & db) and your vps have FreeBSD12.2. You have 2 option: Upgrade your vps to FreeBSD13 Since you are using a x32 FreeBSD at your vps, you can compile there too.

I have just 1x so yes that maybe a clue. Dec 2 14:13:14 :: SYSTEM: new connection from [192.168.0.117] fd: 19 handshake 2814155594 output input_len 0, ptr 0x315e4700 Dec 2 14:13:15 :: Handshake: client_time 0 server_time 29308 Dec 2 14:13:15 :: LOGIN_BY_KEY: admin key 617818769 Dec 2 14:13:15 :: LoginSuccess Dec 2 14:13:15 :: player([SA]Admin).job(0) Dec 2 14:13:15 :: player().job(0) Dec 2 14:13:15 :: player().job(0) Dec 2 14:13:15 :: player().job(0) Dec 2 14:13:15 :: success to 192.168.0.169:13002 Dec 2 14:13:15 :: InputDB::login_success: admin Please try to comment out ENABLE_PROXY_IP from common/service.h then recompile, I'm not saying it's bad because it's ok for me, just to make sure. (since I have no other idea)

That is the channel1/game2 syserr? Blue map1 is in game2. Interesting because you made your way in-game then it drops you out. Maybe you used the PROXY_IP when you shouldn't? Only use that feature when your machine have a private/internal ip address and you want to proxy players to the public ip. (virtualbox, aws, google cloud) (Pid init and deinit and shutting down syserrs are normal, it writes there every time you start or close your server so we can consider the upper syserr empty too)

Check if you edited inventorywindow.py and / or GameType.h in the source. (You have to recompile the client binary and take the new exe)

Change the host name from metin2 to metin2.com or metin2.anything so it will be qualified for the sendmail function. Edit: I changed the hostname to metin2.code in the mega folder vm. The serverfile itself has not changed. Ch1 have 3 cores, open them all, not just the first. (Check the CONFIG files for port numbers) Admin character is in blue map1 what is in game2 and thats surely unopened at you.

VM with FreeBSD 12.2: [Hidden Content] Readme.txt Only use this if you really can't use the FreeBSD 13 VM!

I'm not planning to make a video but the steps are: Buy a VPS with FreeBSD13.0 Enable root login in etc/ssh/sshd_config edit "#PermitRootLogin no" to "PermitRootLogin yes", then reboot or /etc/rc.d/sshd restart pkg install mysql55-server python27 (it will ask to install tke pkg itself too, type yes) add mysql_enable="yes" to /etc/rc.conf then reboot or start mysql via service mysql-server start Upload the metin2_server+src.tar.gz to /usr and cd /usr then tar -xf metin2_server+src.tar.gz Stop mysql via service mysql-server stop, delete the empty var/db/mysql folder and upload the metin2_mysql.tar.gz to /var/db and cd /var/db then tar -xf metin2_mysql.tar.gz then start mysql via service mysql-server start or you can reboot too (You can install the database via the provided mysql_dump_too and run queries if you prefer that way) If you have 32bit system then install the packages mentioned in Libs.txt via pkg, if you have 64 bit system then upload libs to /usr/lib32 from Libs.zip Start your server via cd /usr/metin2/server && sh start.sh Notes: Compiling only possible in a x32 system, but the server can run on a x64 system too. The game & db compiled in FreeBSD13 will not run on older FreeBSD like 12 or 11.

It's /usr/metin2/src/common/service.h.

Please read the topic we were just talking about that today ? (And ports to 13000 to 13040 is not enough, what about auth for example or game99)? And no, I suppose you can't comment here in hungarian, it is an english board. And no, I can't provide private help to anyone (in dc or in anywhere). You may want just 15-30mins but that multiplied by everyone (because If I accept your request, I should accept everyone's) would be hella lot time, which I can't afford. Don't forget it's a free release. But you can ask your question in questions & answers or even here if it's closely related to this release and me or someone will probably answer.

It depends what you consider as a root server. Like you can open the ports in your router and set the newly added PROXY_IP, then players can join your server run under Virtualbox. However I don't consider that as a root server, better to call it as home-root. If you use a dedicated machine for the server and run it in your home I would still call it as home-root. Also the PROXY_IP still needed to let players join because your server still have an internal/private ip from your router, and not an external/public ip directly. Lots of people thinks that it's only needed in Virtualbox, but that is wrong and Virtualbox have nothing to do with it, it just about the internal/private ip vs external/public ip.. If you buy a VPS or even dedicated machine from a hosting, then I would call it as a root server. PROXY_IP usually not needed there because the vps gets an external/public ip by default. However there are some platform and service when you still need PROXY_IP like AWS Cloud and Google Cloud platform because there your vms gets an internal/private ip. (Those are very similar as home-root, just your home are actually in the "cloud" ?) But again, for an avarage vps you don't need PROXY_IP or any trick with the networking.

It's ok sorry, I finished the upload like 2 hours ago but forgot to delete that txt ?

There is no extra protection or so for packets. If that multi lang system is free then I suggest you to open a topic in questions & answers providing the code to check, otherwise ask help from the author. ----------------------------------------------------- Little update: 2021.11.28: - Added ENABLE_PROXY_IP. It is for when you have an internal IP and you try to connect with an external IP, you will be kicked after charselect. If you want to use it then set BIND_IP: internal & PROXY_IP: external in the CONFIG files (and uncomment!) + open ports in your router. [Hidden Content] - Fixed some empiredesc_*.txt & jobdesc_*.txt in some locale files. About the ENABLE_PROXY_IP: Use that feature when your server have an internal/private IP address like Virtualbox, AWS, Google Cloud. It will solve the "kick after charselect" issue when you or your friend tries to connect from outside of your local network. For an avarage VPS what does not have internal/private IP, you don't need to use this feature. About the empiredesc & jobdesc: Some locales had those files in a newer format (for newer charselect) that's why it glitched when you clicked the "next" button (see some comments above). Basicly the 4 base languages were good (en/de/hu/fr) other were in the newer format, so if you use those, then redownload the client and get the fixed empiredesc & jobdesc files.

You are looking for this modification: I should add this with today's update?

Yes basicly things you compile in FreeBSD13 are not compatible with older FreeBSD. There is forward compatibility only. (But I wonder how did you compile in x64 system but anyway, glad you managed it) Some locales have the jobdescs and probably empiredesc txts for the newer select design, I wonder why it has only been reported now ? Anyway I'll fix it today and update the Mega drive, thank you that you reported ?

Hello, FBSD_1.6 refers to FreeBSD 13.0. I suppose you are in a vps since I'm 100% sure admin character works in the VM. Does your VPS have FreeBSD13 installed?

That's not how it's works. Install FreeBSD13 (if you can't choose 13, then install 12 and upgrade) Then install mysql55-server, python27 via pkg. Upload metin2_server+src.tar.gz to /usr and metin2_mysql.tar.gz to /var/db then extract both on vps via tar -xf name.tar.gz command If you choose 32bit FreeBSD then install the packages mentioned in Libs.txt to install libs, if you choose 64bit FreeBSD then use the libs in Libs.zip Many people make the mistake of choosing a hosting where they are not able to select FreeBSD as OS or install a custom iso file for their VPS. I'm not saying it's not possible to install FreeBSD even there, but definitely not a beginner level: [Hidden Content]

Download Metin2 Download or Google Drive Don't forget to enable the serverlist image in root/intrologin.py by setting the FULL_BACK_IMAGE variable to True.

So first of all only the 3rd line is a real 'error': 1126 22:25:14406 :: CEffectManager::RegisterEffect - LoadScript(D:\Ymir Work\effect\monster2\yellowred1_big.mse) Error That effect file is missing in every client, Ymir/Webzen forgot to include it. The 1st, 2nd and 4th line is not an error. It is just a notice that it will try to find in another path ("Will Find Another Path." in english). And it actually finds. If you are bothered with that syserrs I suggest you to either comment out from the source or move to logs.txt what are only presents in debug mode. I'm not gonna remove that syserr because it is a reference release. About that effect file, since Ymir/Webzen forgot to include it, I can't really conjure it up for you ? You have 2 option: Remove it from flame_npc.msm: [Hidden Content] Use yellowred1_great.mse because that is exists, but maybe different.

Hi, It does exists: 110100~110199 ÇĎ±Ţ ŔĎąÝ ąé·ćĽ® ITEM_DS DS_SLOT1 1 ANTI_SAFEBOX | ANTI_SELL NONE NONE NONE 0 0 0 0 0 TIMER_BASED_ON_WEAR 86400 LIMIT_NONE 0 APPLY_NONE 0 APPLY_NONE 0 APPLY_NONE 0 0 0 0 0 0 0 0 0 0 Didn't you mess up your vnum range in item_proto.txt or if you installed a notxt tutorial forgot to set your vnum range in sql? If you use this tutorial: You have to set your vnum range to that new vnum_range column, it's not automatic since originally there is no vnum_range column in the item_proto table, just in txt.

Hi, your typing is there, it is just hidden for security reason. Don't ask why FreeBSD don't use * characters like other system do (maybe to hide the length), it is a normal behavior for FreeBSD. Keyboard set to hungarian by default (as I see you are hungarina too) so just type 123456789 then press enter, it should work. (Btw anyone can change they keyboard layout with the kbdmap command) And make sure to use the new release (download it from Mega until M2DL gets updated), I need feedback for the FreeBSD13 migration ?

If you don't like the newer FreeBSD13.0 then download a FreeBSD12.2 x32 iso from here and install it to your vbox or even dedicated machine. And as I said above, install these packages via pkg: -mysql55-server -mysql55-client -python27 -devil (1.7.8) -boost-all (1.72.0) -llvm-devel -cmake -gmake -makedepend -gdb And after that you can compile the sources and start your server.

New Update: FreeBSD13 2021.11.22: - Project migrated to FreeBSD13.0. CryptoPP (8.4.0) included in the /usr/metin2/src/etc folder, and placed all non-main project folders to that 'etc' folder like libmysql, libdevil, teen etc. Here is a patch file if you need: [Hidden Content] - Hackshield commented out from the source, it's lib was not compatible and it was unused anyway. - Googletest code commented out, it was totally unnecessary and mostly unused. (main.cpp) - Changed a return null to return false in bool DSManager::ExtractDragonHeart. (DragonSoul.cpp) - ClientVS19.zip removed, please use ClientVS22.zip and update your Visual Studio to 2022. - Fixed EterLib/NetStream.cpp, if you enable _PACKETDUMP it will work now. - 71051 & 71052 clientside description was swapped, fixed it in itemdesc.txt. The game & db compiled in FreeBSD13 may not run in FreeBSD12. If you don't want to update your VPS to FreeBSD13, I suggest you to compile the source in FreeBSD12.2 x32. If you install these packages via pkg the source should compile without an issue in FreeBSD12.2 x32 too: Please report bugs, it was a big milestone for the project so bugs can happen.