Rumor

i like that one plechito !

oh sorry you said 40k, I haven't tried 40k+ yet.

could you be more specific about a color bug on these functions? I haven't seen this.

It is, and I've proven it ^^

maybe before, but now it's garbage.. It has a broken about page, says DDoS protection but no details, and too cheap to be real or work well. Network status is broken, forum link is broken, 3 more footer links are broken. The terms are copied from OVH so it's likely an OVH reseller. A WHOIS shows that some of it is involved with RamNode (trusted US-Based VPS seller) and some with WeServIt (lying host in NL).

I told you why I thought it would work but yeah you ended up to be correct

Update: OVH IS TOTAL CRAP. Don't bother.. OVH FR: Server failing to mitigate 5-33 Mbit attacks at 3-15k packets per second despite their claims to be able to mitigate 480Gbps. They are bragging on twitter about blocking a 350Gbps attack and how they are successful. Success doesn't mean allowing your customer's servers to be ruined so you can block an 350/480Gbps of your supposed protection. Success doesn't mean advertising something you cannot give. Everything here is French and they have an option on registration to change the language but it doesn't work. All the emails are in French despite the fact it would be terribly easy for them to translate them as they are automated and very short. They don't care at all about the customers. I should have not expected so much from a French host. It's also nearly impossible to get in contact with them. They only allow forum support at kimsufi and they don't even provide that support. When you create a thread you instead get a bunch of ignorant normal users saying that you should use iptables. There is no ticket system, no live chat, no way to talk to them on the phone. I'll definitely be getting a refund and if they don't let me I will be charging the funds back. Avoid at all costs...

but what is the importance of the letters on each level ?

then it appears whatever bin WOM uses has the bug, 34669 has the bug, and 36469 has the bug.. atleast these ones for sure.

I don't fully understand how the user does the quest, or what the significance of the N,M,G,P levels are.. but I appreciate a quest in English which is actually readable. Would love to see more posts by you.

no it's enigma's fault.. it works fine but not on Windows 8 or 8.1. It has nothing to do with AV, it's a Windows 8 specific problem :/. The ifle isn't missing either.. it's a wrong error caused by Enigma. The EXACT same client on any other OS works flawlessly. Adding that file into the physical directory of the client on a Win 8 system doesn't fix the issue. It's 100% a Win8 issue based on this information.

8 did in-fact have problems, because I've been using this since August and people have been having the issue since August. 8.1 was released in October. You can see one of the examples here:

I've confirmed this will work (according to Enigma) on Windows 8 by using the latest version. I plan to purchase it soon. - Virtual Box: Bug fixed loading virtual dll files under Windows 8 x64 - Virtual Box: Bug fixed running some virtual exe files on Windows 8

yeah it doesn't matter what month really..

These files were on sale by some guy pretending to be a chick on Skype. Turns out they had a virus in them attached to the client binary. For this reason and to eliminate useless downloads, I've taken the share folder, player database, and pack folder and compressed them. This is pretty much so that you can grab things you want from the client/db/share folder for your own use. It's using the 2166 Alessa game core and has some things from Metin2Undead/UndeadEmpire and some things from M2M, and valkryiemt2 and other stuff from Puru. I ofcourse didn't pay for these, a friend got someone to give it to them free and then gave them to me. To prevent you from wasting your time if you already have these, they're known as "meteora files" and came in several password protected archives. If you ran the client you have infected your PC :/. Downloads are at the bottom underneath all the images. I just copied the images from another forum and posted them here. There were more images but some links are dead and I didn't want to post all of them because it wasn't necessary. pack: [Hidden Content] mysql: [Hidden Content] share: [Hidden Content]

Also would be great if that bug can be fixed where you teleport with over 32,000 HP and you end up with negative HP.

I forgot about another host I've used.. called RaptorNode. Operated by some cocky British kid.. RaptorNode: This host was full of downtimes and letdowns. Broken agreements after making payments were a normal occurrence for this host. Blaming the customer when the host is at fault is not acceptable for any host. The owner told me that he would get a GRE tunnel setup to filter all the traffic and avoid DDoS and finding the real IP of the server. He wanted a fee for the setup but never actually setup the tunnel because he lacks experience in FreeBSD. A friend fixed it on the FreeBSD side and it still wasn't working because it was improperly configured on the CentOS side. A total nightmare. The forum would go down all the time (separate shared hosting with same company). He would wait until hours later or the next day to say there aren't any issues or say they are resolved. This would happen on a daily basis. Even after indisputable evidence that there was a network issue he continued to say that there's no problem with the network. See below... traceroutes NL MKD Romania 1 <1 ms <1 ms <1 ms 192.168.1.1 2 14 ms 13 ms 17 ms 10.115.0.1 3 16 ms 17 ms 19 ms 24.144.0.193 4 39 ms 24 ms 27 ms 66-194-86-233.static.twtelecom.net [66.194.86.233] 5 30 ms 33 ms 33 ms dal2-pr2-xe-2-3-0-0.us.twtelecom.net [66.192.240.90] 6 38 ms 41 ms 44 ms sl-st30-dal-.sprintlink.net [144.228.250.85] 7 41 ms 61 ms 88 ms 144.232.0.161 8 50 ms 41 ms 46 ms 144.232.9.54 9 50 ms 62 ms 51 ms be2031.ccr21.dfw01.atlas.cogentco.com [154.54.7.45] 10 57 ms 51 ms 54 ms te0-0-0-2.ccr21.iah01.atlas.cogentco.com [154.54.25.218] 11 76 ms 65 ms 80 ms te0-1-1-2.ccr22.atl01.atlas.cogentco.com [154.54.7.237] 12 244 ms 254 ms 263 ms te2-1.ccr01.clt01.atlas.cogentco.com [154.54.0.97] 13 71 ms 66 ms 68 ms dacentec.demarc.cogentco.com [38.104.168.10] 14 70 ms 70 ms 76 ms dct-ds42-ve.dacentec.com [199.191.57.194] 15 70 ms 71 ms 74 ms dct-ds08-vl-41.dacentec.com [199.241.190.230] 16 70 ms 86 ms 70 ms nc12.raptornode.com [192.254.73.254]

Enjoy! Use at will, no copyright/linkback required.

1. Extract root archive and open intrologin.py search for: loginFailureMsgDict={ It should look something like this: self.loginFailureMsgDict={ #"DEFAULT" : locale.LOGIN_FAILURE_UNKNOWN, "ALREADY" : locale.LOGIN_FAILURE_ALREAY, "NOID" : locale.LOGIN_FAILURE_NOT_EXIST_ID, "WRONGPWD" : locale.LOGIN_FAILURE_WRONG_PASSWORD, "FULL" : locale.LOGIN_FAILURE_TOO_MANY_USER, "SHUTDOWN" : locale.LOGIN_FAILURE_SHUTDOWN, "REPAIR" : locale.LOGIN_FAILURE_REPAIR_ID, "BLOCK" : locale.LOGIN_FAILURE_BLOCK_ID, "WRONGMAT" : locale.LOGIN_FAILURE_WRONG_MATRIX_CARD_NUMBER, "QUIT" : locale.LOGIN_FAILURE_WRONG_MATRIX_CARD_NUMBER_TRIPLE, "BESAMEKEY" : locale.LOGIN_FAILURE_BE_SAME_KEY, "NOTAVAIL" : locale.LOGIN_FAILURE_NOT_AVAIL, "NOBILL" : locale.LOGIN_FAILURE_NOBILL, "BLKLOGIN" : locale.LOGIN_FAILURE_BLOCK_LOGIN, "WEBBLK" : locale.LOGIN_FAILURE_WEB_BLOCK, "BANNED" : locale.LOGIN_FAILURE_BLOCK_ID, } After the last line add a new line and enter a code for a custom ban reason (you will use this later so keep it easy to remember): self.loginFailureMsgDict={ #"DEFAULT" : locale.LOGIN_FAILURE_UNKNOWN, "ALREADY" : locale.LOGIN_FAILURE_ALREAY, "NOID" : locale.LOGIN_FAILURE_NOT_EXIST_ID, "WRONGPWD" : locale.LOGIN_FAILURE_WRONG_PASSWORD, "FULL" : locale.LOGIN_FAILURE_TOO_MANY_USER, "SHUTDOWN" : locale.LOGIN_FAILURE_SHUTDOWN, "REPAIR" : locale.LOGIN_FAILURE_REPAIR_ID, "BLOCK" : locale.LOGIN_FAILURE_BLOCK_ID, "WRONGMAT" : locale.LOGIN_FAILURE_WRONG_MATRIX_CARD_NUMBER, "QUIT" : locale.LOGIN_FAILURE_WRONG_MATRIX_CARD_NUMBER_TRIPLE, "BESAMEKEY" : locale.LOGIN_FAILURE_BE_SAME_KEY, "NOTAVAIL" : locale.LOGIN_FAILURE_NOT_AVAIL, "NOBILL" : locale.LOGIN_FAILURE_NOBILL, "BLKLOGIN" : locale.LOGIN_FAILURE_BLOCK_LOGIN, "WEBBLK" : locale.LOGIN_FAILURE_WEB_BLOCK, "BANNED" : locale.LOGIN_FAILURE_BLOCK_ID, "BOT" : "Banned for use of SwitchBot", } You can see that the reason is for switchbot, this is the message that will be displayed to the user who's banned. 2. Banning users with the custom ban reason: Go into the account.account database and find the user's account. Go to the status column and change "OK" to "BOT".

that's really nice, alot better than using custom ban reasons in the client and setting the word in status of account.account db

Can you fix the invisibility bug that happens when a player revives or logs in please?

Would you mind explaining?