ds_aim

Dude. Stop saying mainline server / novaline client. There is no difference between packets.

[Hidden Content]

You must make packet comunication with client if you want to get exactly the mapindex vnum.

You can get mapnampe from altlasinfo.txt

Okay, follow my tutorial. 1. Open novaline source. 2. Make a folder to desktop. Example: "src_vs2013" . 3. Drag from novaline Client and Exter folder to "src_vs2013" . 4. Copy in extern/include/Python27/22 stuffs. 5. Recompile cryptopp with vs2013 toolset. 6. Move library in extern/lib (New Cryptopp) 7. Open .sln from "src_vs2013" he will update all solutions. 8. Select Distribute/Build It was hard? Fuck. IT WAS HAAAAAAAAAAAARD ? EHHHH ? You don't need include_stuff and lib_stuff shit. You know only copy/paste ? Just do what i said.

Never upgrade to vs2013 /2015. Belive me. Just don't do this. Use 2008

32BIT -FREEBSD 32BIT - WINDOWS 64BIT -WINDOWS -> 32BIT FREESD = ERROR.

#Reported

Here you have two video. Video 1 Video 2 Who can solve this , contact me. I will pay

It's an atachment. I think it's a forum issue. This forum go down down, evry day. Here it's a link. [Hidden Content]

Hello, i'am reboot. Here is lib folder. Lib.rar

WHat python use you client? Desktop.rar

It's better to block from main.cpp

no, not really. Just some bugs fixed. And necessary for cython.

As of MySQL 5.7.4, the ERROR_FOR_DIVISION_BY_ZERO, NO_ZERO_DATE, and NO_ZERO_IN_DATESQL modes are deprecated. From MySQL 5.7.4 though 5.7.7, these modes do nothing when named explicitly. Instead, their effects are included in the effects of strict SQL mode (STRICT_ALL_TABLES or STRICT_TRANS_TABLES). In other words, strict mode means the same thing in those versions as the pre-5.7.4 meaning of strict mode plus ERROR_FOR_DIVISION_BY_ZERO, NO_ZERO_DATE, and NO_ZERO_IN_DATE. The MySQL 5.7.4 change to make strict mode more strict by including ERROR_FOR_DIVISION_BY_ZERO, NO_ZERO_DATE, and NO_ZERO_IN_DATE caused some problems. For example, in MySQL 5.6 with strict mode but not NO_ZERO_DATE enabled, TIMESTAMP columns can be defined with DEFAULT '0000-00-00 00:00:00'. In MySQL 5.7.4 with the same mode settings, strict mode includes the effect of NO_ZERO_DATE and TIMESTAMP columns cannot be defined with DEFAULT '0000-00-00 00:00:00'. This causes replication of CREATE TABLEstatements from 5.6 to 5.7.4 to fail if they contain such TIMESTAMP columns. But i suggest you to upgrade dbcache and gamecore too.

Use last gdb version.

this don't help. You core don't have debug symbols.

what ?

// FUCKING START { DWORD dwPID; LPCHARACTER ch = CHARACTER_MANAGER::instance().FindByPID(dwPID); if (ch->GetMapIndex() == 111) { if(ch->GetLevel() >= 90) { return; } } } // FUCKING END

edited. :

// FUCKING START { DWORD dwPID; LPCHARACTER ch = CHARACTER_MANAGER::instance().FindByPID(dwPID); if (ch->GetMapIndex() == 111) { if(ch->GetLevel() >= 90) { return; } } } // FUCKING END Add this in char_item case POINT_EXP PS: Don't tested.

Hy, nice to meet you. My name is Ira. Directx? Nice.. some news about updating metin directx to 11? I started to upgrade to dx11 but so fucking much bugs

Oh , then why you ask if u already know that ? VS2008 it's old dude. It's primitive. VS2008 have so much bugs. If vs2015 say it's an error in code then it's an error. I already said you the solution.