Jump to content
  • 0

Crash on cube_Renewal



  • VIP

Hy guys !

I have a problem with cube renewal


First i modify in cuberenewal.cpp/ cuberenewal.h on source game this function 

iEmptyPos = ch->GetEmptyDragonSoulInventory(pItem

into this 

iEmptyPos = ch->GetEmptyDragonSoulInventory(dwVnum, bSubType, bSize)

Bcs i cant compiled, now my server is working but when i try to crafting something is throwing  me back to login, 

All error i have is this 

SYSERR: Jan  3 14:18:05 :: Process: UNKNOWN HEADER: 174, LAST HEADER: 0(0), REMAIN BYTES: 28, fd: 22

But in my packet.h ( binary and source) i dont have this value ( 174 ) 

Some ideas?

Ty :3

Link to post

5 answers to this question

Recommended Posts

  • 0

You're not really expecting someone to help you, use a system from Worldard which got leaked or?

Edited by Kafa
Link to post
  • 0
  • VIP


My opinion would be to buy the system, or if you bought it to talk to the owner of this system it will definitely help you. But a small leak, check the packages from the binary source and the game source may be attached over others or you did not add them correctly.

Link to post
  • 0
1 minute ago, FALLEN1 said:

I solved, in packet_info.cpp i put false.


There is a exploit where you can duplicate items with public one. WorldArd fixed it, but gl. :) 

Link to post

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Answer this question...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

  • Create New...

Important Information

Terms of Use / Privacy Policy / Guidelines / We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.