-
Posts
82 -
Joined
-
Last visited
-
Days Won
1 -
Feedback
0%
Content Type
Forums
Store
Third Party - Providers Directory
Feature Plan
Release Notes
Docs
Events
Posts posted by Destiny
-
-
Wasn't a good ideea , but with >50 works fine now ;
I'm pretty sure if you play ninja with daggers you will get banned
The ninja character is the most secured , even you use hack you won't get ban so fast .
i dont know why...
-
If you hate the dropped yang you can delete vnum 1 from item proto and you done
it doesn't make any error and is tested by me for more than 5-6 months without problems.
-
Un român dăruitor ; Nu te scuza la engleză , te descurci foarte bine
ps : Thank you for share us
- 1
-
I changed if (ch->m_speed_hack_count > 50) with if (ch->m_speed_hack_count > 5)
And works verry good .
I work on mainline sg ,pvm hard server ;
This protection can cause fake result and ban a fair player ?
-
In what file cpp we edit this ?
I want to , it is something nice
-
-
char_item.cpp: In member function 'bool CHARACTER::IsEmptyItemGrid(TItemPos, BYTE, int) const': char_item.cpp:640: warning: comparison is always false due to limited range of data type char_item.cpp:666: warning: comparison is always false due to limited range of data type char_item.cpp: In member function 'bool CHARACTER::UseItemEx(CItem*, TItemPos)': char_item.cpp:2387: warning: format '%d' expects type 'int', but argument 6 has type 'long int' char_item.cpp:2391: warning: format '%d' expects type 'int', but argument 6 has type 'long int' char_item.cpp:2403: warning: format '%d' expects type 'int', but argument 5 has type 'long int' char_item.cpp:2407: warning: format '%d' expects type 'int', but argument 5 has type 'long int' char_item.cpp:2434: warning: format '%d' expects type 'int', but argument 6 has type 'long int' char_item.cpp:2442: warning: format '%d' expects type 'int', but argument 5 has type 'long int' char_item.cpp:5096: warning: comparison between signed and unsigned integer expressions char_item.cpp: In member function 'bool CHARACTER::UseItem(TItemPos, TItemPos)': char_item.cpp:5168: warning: unused variable 'wDestCell' char_item.cpp:5169: warning: unused variable 'bDestInven' char_item.cpp: At global scope: char_item.cpp:5685: error: ISO C++ forbids initialization of member 'is_allowed' char_item.cpp:5685: error: making 'is_allowed' static char_item.cpp:5685: error: ISO C++ forbids in-class initialization of non-const static member 'is_allowed' compile crc32.cpp char_item.cpp:5974: error: 'NPartyPickupPermission' has not been declared char_item.cpp:5974: error: expected constructor, destructor, or type conversion before 'funcCompareOwnershi p' char_item.cpp:5975: error: expected constructor, destructor, or type conversion before '->' token char_item.cpp:5976: error: expected constructor, destructor, or type conversion before '=' token char_item.cpp:5977: error: expected unqualified-id before 'if' char_item.cpp: In member function 'bool CHARACTER::EquipItem(CItem*, int)': char_item.cpp:6201: warning: array subscript has type 'char' char_item.cpp: In member function 'void CHARACTER::BuffOnAttr_AddBuffsFromItem(CItem*)': char_item.cpp:6265: warning: comparison between signed and unsigned integer expressions char_item.cpp: In member function 'void CHARACTER::BuffOnAttr_RemoveBuffsFromItem(CItem*)': char_item.cpp:6277: warning: comparison between signed and unsigned integer expressions char_item.cpp: In member function 'bool CHARACTER::CanEquipNow(CItem*, const TItemPos&, const TItemPos&)': char_item.cpp:7463: warning: unused variable 'itemType' char_item.cpp:7464: warning: unused variable 'itemSubType'
fail to compile -
It is not a diff , you have to learn how to make a lib.
-
Vanilla have the most strangest crashes i have ever seen , you can move to mainline sg if you want something stable.
-
You didn't have to give the actual link to this kick hack.. now i have to make lib for 34k coz kids are playing around^
Having the information public is the fastest way to get people to take action against it and the fix is in the thread. If you're able to create libs then it should be no problem for you
Also having the hack we could test if the c++ fix works
-
Thanks for share , all works fine.
-
Replace the ACMD(do_messenger_auth) method to this: in what cpp file ?
-
It didn't work .
-
-
Right Denis
-
How can i stop from source the drop hack ?
Thank you !
-
Is not there
Edit : Thank you , it works.
-
-
-
I have this error since ago 1 year , it doesn't make any problem.
-
How can i change the chance of upgrading the alchemy ?
Example : Antic to Legendary .
Thanks.
-
Make your special drop item .txt at that vnum item .
-
I made the edits of lines 2278 , 2354 with //pkVictim->RemoveAffect(pkSk->dwVnum); and it still make problems.
-
https://www.youtube.com/watch?v=iJ_8JAqlR8o&feature=youtu.be
Please help .
Anti Wait Hack Damage
in Bug Fixes
Posted
Metod log > more secure :
Create in database log a table with name : wait_hack
It is more secure now .