[Development] Source Mu Main 1.03.35 [Season 5.1 - Season 5.2]

[dsw_pool]

To view the content, you need to sign in or register

To view the content, you need to sign in or register

To view the content, you need to sign in or register

Link:

To view the content, you need to sign in or register

Credits:

Webzen

 

[kirdzar0r]

Re: SRC Mu 1.03.35 [Season 5.1 - Season 5.2]

woww. good release. amazing.

 

[solarismu]

Re: SRC Mu 1.03.35 [Season 5.1 - Season 5.2]

GOLD is here.

 

[SmileYzn]

Re: SRC Mu 1.03.35 [Season 5.1 - Season 5.2]

And the third war begins, nice share anyway

 

[Kiosani]

Good Release dsw_pool

 

[xakumm]

finally, waited so long. thanks. tt1:

 

[SmallHabit]

OMG! This can’t be true, waited way too long for this to happen

 

[profesor08]

MU is back

 

[psychedelic]

love it

 

[rejor]

it's great. MU is back

 

[Sam3000]

Someone tried to compile this source?

 

[RacRac]

Someone tried to compile this source?

Use vs2010 toolset v90

 

[mauka]

sorry for offtopic, but where to down a fakin vs2010 express?

 

[RacRac]

sorry for offtopic, but where to down a fakin vs2010 express?

Torrent i guess ????

 

[SmallHabit]

Use vs2010 toolset v90

Why use such an old toolset? Everything compiles excellent on latest VS 2019 edition, only jpeglib was causing problems, but still, if you can write hello world application and know how build works on Windows, there should be no problem at all.

 

[solarismu]

Why use such an old toolset? Everything compiles excellent on latest VS 2019 edition, only jpeglib was causing problems, but still, if you can write hello world application and know how build works on Windows, there should be no problem at all.

It depends on ... (maybe luck)... and C++ STL in pre built library. If the library & program does not use STL stuff from each other, then you will be fine. On the other hand, there will be problems...
(Complier may give warning ??? maybe)

Because the objects' structures change in different version of VS / toolsets / or even between DEBUG & RELEASE modes . (Simple check: sizeof(...))

(std::string , std::map are 2 common data structures using in Webzen source)

example:
Program A (VS2017 RELEASE) <- linked with -> Lib B,C (VS2008 RELEASE/DEBUG)

#include <string>
#include <map>
using namespace std;

Program A VS2017 / toolsets v141 RELEASE build string s; map<...> m foo(&s, &m) sizeof(string); // = 24 sizeof(map); // = 8

Lib B VS2008 / toolsets v90 RELEASE build void foo(string*, map<...>*); sizeof(string); // = 28 sizeof(map); // = 32

Lib C VS2008 / toolsets v90 DEBUG build void foo(string*, map<...>*); sizeof(string); // = 32 sizeof(map); // = 28

 

[RacRac]

Why use such an old toolset? Everything compiles excellent on latest VS 2019 edition, only jpeglib was causing problems, but still, if you can write hello world application and know how build works on Windows, there should be no problem at all.

Compiled with vs2019 and had issues with the cashshop .

 

[Sam3000]

Same, i have errors with libs:

FileDownloader_VS2008_MB_MT_d.lib(FTPConnecter.obj) : error LNK2001: unresolved external symbol "void * __cdecl operator new[](unsigned int,struct std::_DebugHeapTag_t const &,char *,int)" (??_U@YAPAXIABU_DebugHeapTag_t@std@@PADH@Z)
...
FileDownloader_VS2008_MB_MT_d.lib(FTPConnecter.obj) : error LNK2001: unresolved external symbol "struct std::_DebugHeapTag_t const & __cdecl std::_DebugHeapTag_func(void)" (?_DebugHeapTag_func@std@@YAABU_DebugHeapTag_t@1@XZ)
...
ShopListManager_VS2008_MB_MT_d.lib(ListManager.obj) : error LNK2001: unresolved external symbol "public: static void __cdecl std::_String_base::_Xran(void)" (?_Xran@_String_base@std@@SAXXZ)
...
ShopListManager_VS2008_MB_MT_d.lib(ShopPackage.obj) : error LNK2001: unresolved external symbol "public: __thiscall std::exception::exception(char const * const &)" (??0exception@std@@QAE@ABQBD@Z)
...
ShopListManager_VS2008_MB_MT_d.lib(ShopList.obj) : error LNK2001: unresolved external symbol "public: void __thiscall std::_Mutex::_Lock(void)" (?_Lock@_Mutex@std@@QAEXXZ)

Dunno how to fix this.

 

[wermanhme1990]

Same, i have errors with libs:

Dunno how to fix this.

you should use visual studio 2008 sp1 to build client.

 

[d8yte]

vs 2008 sp1 compiles it like native.. no problems at all!
what about srv'files for this version, wanna test it.
would be great to downgrade it at s2~s3 version like old interface with cool things..
Has anyone found anything interesting in the code?