Jump to content


  • Posts

  • Joined

  • Last visited

  • Days Won

  • Feedback


TMP4 last won the day on March 11 2022

TMP4 had the most liked content!

About TMP4

  • Birthday July 21


  • Gender
  • Country

Recent Profile Visitors

14198 profile views

TMP4's Achievements


Perfect (15/16)

  • Great Content Rare
  • Well Followed Rare
  • Posting Machine Rare
  • Reacting Well
  • Dedicated

Recent Badges



  1. It's not a bug. It comes from the PM Flood kick hack fix. I believe It does not affect normal players, since a normal player does not send a lot of messages in such speed. "two or more messages at high speed" It's actually 4 if you check the src or your gif.. Do not uninstall completely this fix. If you edit "ch->GetPMCounter() > 3" in input_main.cpp to something bigger then you can flood other players more before the disconnect happens, if your players are typing champions
  2. Thank you so much! I downloaded it and uploaded it to the mega.nz archive.
  3. In the source files the language texts are in korean. If you open the file with a text editor with a bad character encoding, the korean letters will be converted to something else and it won't find their translation in locale_string. That's happened to you. Once you saved the file you can't fix it, the korean letters are gone. Take a backup and be sure next time you edit it with keeping the encoding. You can turn off auto character encoding in Notepad++ settings, or use other editor, for example Visual Studio.
  4. The problem I don't have backup of the video file and youtube won't let you download it if it's striked. If I have backup, I would reupload it to somewhere else.
  5. 2023.08.05: - New freshly installed VM with FreeBSD 13.2. - Installed a fix about an exploit: [Hidden Content] - Expect this as the last update unless there will be some serious problem. What's left on my todo list is MySQL8 compatibility, sadly don't expect it from me, lately I am interested in other things than Metin2. If anyone do it and wanna share it (I will include the credit), contact me.
  6. Yes. It is a 60 second loop timer, not a 1-2 second one. But you're free to modify, and events_automation.quest is optional, if you don't wanna use it then don't use it, or do it in another way.
  7. [Hidden Content] There's a readme inside. Tested on 13.1 and 13.2. Probably won't work on 14.x
  8. Is it RO? Re-extract mob_proto.txt & mob_names.txt and try again. Here's an example: 10001 Ţinutul_Yayang 4002 8995 10001 ??? 4002 8995 PAWN WARP SPECIAL 70 NOMOVE 0 STUN,SLOW,CURSE,TERROR 0 0 0 0 0 0 0 0 3954 3 1 0 0 562 79 100 100 0 2000 175 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 I just checked it and it worked.
  9. It's because of MySQL5.6 have STRICT_TRANS_TABLES on by default. Change sql_mode from sql_mode=NO_ENGINE_SUBSTITUTION,STRICT_TRANS_TABLES to sql_mode=NO_ENGINE_SUBSTITUTION in /usr/local/my.cnf
  10. Yes they were 32bit packages since the vm is 32bit. Luckily I have an x64 vm too where I had the packages so here you are: [Hidden Content] FAQ.txt also modified about this MySQL5.6 deprecation issue. (I may have a look in MySQL5.7 in the future but not promising anything.)
  11. I just edited my comment and your quote contains how you can install it: "Then install with the command: pkg add /path/to/package.txz for example pkg add /var/cache/pkg/mysql56-server-5.6.51.pkg" So basicly upload and extract to anywhere then use pkg add command with route for the file.
  12. You missed this part isn't you? "check if your ports are opened succesfully here: [Hidden Content]" Anyway in vps you'll be okey. I don't know if it will work with 5.7. Probably not or at least there will be some anomaly. You can install 5.6 if you take the cached package files from /var/cache/pkg from the vm. Then install with the command: pkg add /path/to/package.txz for example pkg add /var/cache/pkg/mysql56-server-5.6.51.pkg
  13. It is not a bug and it has nothing to do with the 4 inventory. Item flush to db (save to db) time is every 7 minute by default in Metin2. If you reboot the whole operating system (why tho? close.sh is enough to close the server..) then of course the save is not happening. If you wanna close the server and let items save to db you can do the following: /shutdown then wait at least 7 minute then sh close.sh (or reboot..) Type 'killall game' to the terminal, then with the 'ps' command you keep checking if all cores stopped, then type 'killall db'. Latter is way faster then waiting 7 minute. You can do the latter with a script if you will, save it as close2.sh or something and use that... clear echo -e "\033[31m \n The server is shutting down.. \033[0m" while pgrep "game"; do echo -e "Waiting for game to stop.." killall game sleep 3 done while pgrep "db"; do echo -e "Waiting for db to stop.." killall db sleep 3 done clear echo -e "\033[31m \n The server shut down successfully!\033[0m"
  • 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.