Rena 1 Posted March 19, 2017 Share Posted March 19, 2017 Does anyone know the solution for this errors to game.core? GNU gdb 6.1.1 [FreeBSD] Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i386-marcel-freebsd"...(no debugging symbols found)... Core was generated by `gamefile'. Program terminated with signal 11, Segmentation fault. Reading symbols from /lib/libmd.so.5...(no debugging symbols found)...done. Loaded symbols for /lib/libmd.so.5 Reading symbols from /lib/libz.so.6...(no debugging symbols found)...done. Loaded symbols for /lib/libz.so.6 Reading symbols from /lib/libstdc++.so.6...Error while reading shared library symbols: Dwarf Error: wrong version in compilation unit header (is 4, should be 2) [in module /lib/libstdc++.so.6] Reading symbols from /lib/libm.so.5...(no debugging symbols found)...done. Loaded symbols for /lib/libm.so.5 Reading symbols from /lib/libgcc_s.so.1...(no debugging symbols found)...done. Loaded symbols for /lib/libgcc_s.so.1 Reading symbols from /lib/libthr.so.3...(no debugging symbols found)...done. Loaded symbols for /lib/libthr.so.3 Reading symbols from /lib/libc.so.7...(no debugging symbols found)...done. Loaded symbols for /lib/libc.so.7 Reading symbols from /libexec/ld-elf.so.1...(no debugging symbols found)...done. Loaded symbols for /libexec/ld-elf.so.1 #0 0x0811b5a4 in std::basic_string<char, std::char_traits<char>, std::allocator<char> >::basic_string<char*> () [New Thread 28c05500 (LWP 100428/gamefile)] [New Thread 28c05200 (LWP 100424/gamefile)] [New Thread 28c04f00 (LWP 100423/gamefile)] [New Thread 28c04300 (LWP 100256/gamefile)] (gdb) Quit (gdb) Quit (gdb) Quit (gdb) Quit (gdb) bt #0 0x0811b5a4 in std::basic_string<char, std::char_traits<char>, std::allocator<char> >::basic_string<char*> () #1 0x0811cd6b in std::basic_string<char, std::char_traits<char>, std::allocator<char> >::basic_string<char*> () #2 0x080dee32 in std::basic_string<char, std::char_traits<char>, std::allocator<char> >::basic_string<char*> () #3 0x080cdf03 in std::basic_string<char, std::char_traits<char>, std::allocator<char> >::basic_string<char*> () #4 0x0814ce8e in std::basic_string<char, std::char_traits<char>, std::allocator<char> >::basic_string<char*> () #5 0x0814e116 in std::basic_string<char, std::char_traits<char>, std::allocator<char> >::basic_string<char*> () #6 0x08136e1b in std::basic_string<char, std::char_traits<char>, std::allocator<char> >::basic_string<char*> () #7 0x08100373 in std::basic_string<char, std::char_traits<char>, std::allocator<char> >::basic_string<char*> () #8 0x08259dc4 in std::operator+<char, std::char_traits<char>, std::allocator<char> > () #9 0x0825a7f1 in std::operator+<char, std::char_traits<char>, std::allocator<char> > () #10 0x0825be4c in std::operator+<char, std::char_traits<char>, std::allocator<char> > () #11 0x0804ec6a in ?? () #12 0x00000001 in ?? () #13 0xbfbfdc6c in ?? () #14 0xbfbfdc74 in ?? () #15 0xbfbfdc50 in ?? () #16 0xbfbfdc68 in ?? () #17 0x00000000 in ?? () Link to comment Share on other sites More sharing options...
Vanilla 1454 Posted March 21, 2017 Share Posted March 21, 2017 most of the stuff is in the client source as the colors are defined by the damage type. For example if the damage you're dealing is marked as a critical strike, the client chooses different files for displaying the damage. You need to change that in the source, it's not too difficult once you've found it. We are the tortured. We're not your friends. As long as we're not visible. We are unfixable. Link to comment Share on other sites More sharing options...
Rena 1 Posted March 21, 2017 Author Share Posted March 21, 2017 12 minutes ago, Vanilla said: cele mai multe lucruri este în sursa de client ca culorile sunt definite de tipul de deteriorare. De exemplu, în cazul în care prejudiciul pe care îl ocupă este marcat ca fiind o grevă critică, clientul alege diferite fișiere pentru afișarea prejudiciului. Trebuie să schimbați că în sursa, nu e prea greu, odată ce ați găsit-o. If you know how make, tell me direct what to do. Link to comment Share on other sites More sharing options...
Tasho 243 Posted March 21, 2017 Share Posted March 21, 2017 12 hours ago, Rena said: If you know how make, tell me direct what to do. //Source/Client/InstanceBase.cpp Search and delete "//" from: //rkEftMgr.CreateEffect(ms_adwCRCAffectEffect[EFFECT_DAMAGE_CRITICAL],v3Pos,v3Rot); Location effect: d:/ymir work/effect/affect/damagevalue/critical.mse Download effect: This is the hidden content, please Sign In or Sign Up Also is here: Link to comment Share on other sites More sharing options...
Rena 1 Posted March 21, 2017 Author Share Posted March 21, 2017 1 hour ago, Tasho said: Typical romanian guys.. //Source/Client/InstanceBase.cpp Search and delete "//" from: //rkEftMgr.CreateEffect(ms_adwCRCAffectEffect[EFFECT_DAMAGE_CRITICAL],v3Pos,v3Rot); Location effect: d:/ymir work/effect/affect/damagevalue/critical.mse Download effect: This is the hidden content, please Sign In or Sign Up Also is here: I don't want that, idiot. I want the throw criticize to be color like in image of above not a effect with critical. Link to comment Share on other sites More sharing options...
AlexKenT 17 Posted March 21, 2017 Share Posted March 21, 2017 16 minutes ago, Rena said: I don't want that, idiot. I want the throw criticize to be color like in image of above not a effect with critical. PM Link to comment Share on other sites More sharing options...
Vanilla 1454 Posted March 21, 2017 Share Posted March 21, 2017 10 hours ago, Rena said: I don't want that, idiot. I want the throw criticize to be color like in image of above not a effect with critical. But he is absolutely right. The Client normally doesn't handle damage values if there's a critical hit. Though there's still something implemented which you can use for your needs. The client is able to display different styles depending on the damage types. For example poison could possibly be showed in a different style - and critical hits too. He even showed you the line which does that. Normally it's commented so the client doesn't use it. If you remove the comment, the client will use the critical.mse to determine the way it shows critical hits. And in effect\affect\damagevalue you can find everything you need, even the critical.mse with which you can display different colors. In your case that is violet. I think both of you need to calm down a bit... There's no need for insulting each other. We don't need prejudices against romanian people and we also do need to insult others as idiots.. especially when they present you the solution to your problem. 6 We are the tortured. We're not your friends. As long as we're not visible. We are unfixable. Link to comment Share on other sites More sharing options...
Tasho 243 Posted March 21, 2017 Share Posted March 21, 2017 (edited) //Soure/Client/UserInterface/InstanceBaseEffect.cpp //Search for: strDamageType = "target_"; //Replace with: strDamageType = (flag & DAMAGE_CRITICAL) ? "target_crit_" : "target_"; d:/ymir work/effect/affect/damagevalue/ This is the hidden content, please Sign In or Sign Up !VnROSw-OlAv1BT_DtavewoJ2EQn7PZBCeX6hL0Y36j8 Edited August 24, 2022 by Metin2 Dev Core X - External 2 Internal 1 Link to comment Share on other sites More sharing options...
Honorable Member pollux 811 Posted March 22, 2017 Honorable Member Share Posted March 22, 2017 You're bumping your topic too fast.. You're insulting members.. You removed your question.. Can you tell me why eactly you're using this board if you don't give a damn about our rules? 1 Link to comment Share on other sites More sharing options...
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now