Wade

Items grade's ( server and client side ) must be 7. Check that first.

I wanna tell a story. You can also share if something similar happened to you. I was working for an official rf online publisher from home. Dont want to go into detail. I didn't have an access to the machine cause i dont go to office. I have a good friendship with my manager so he gave me bunch of files to check. We were testing. Project was over and those files were still in my possession. Most private servers have some basic problems for example honor guilds. Honor guilds function was working perfectly. Race leader can change honor guild every day and guilds get money depens on the % of their share. This is actually valuable. Also files come with lots of fixes you dont really need a zone protection. I didn't actually think about giving out or keep it for something else i just deleted all of them. Now im actually a bit sad. I dont care how much those files worth it. If i still had them probably i would leak instead of selling. You dont think that way when you work for the company but when its over things change. Note : Server version was 2.2.3.2 TLDR : I got some valuable rf online documents & files from officials. Instead of keeping them i deleted all of them. Now im sad Lets chit chat about leaks. Its been more than 2 years since the age of patron ( version 4.15 ) came around. Also there are lots of offical servers running around here like ru us ph id tw cn jp kr. I dont remember how many years have been passed between grand update and the leaks of those files but one way or another 4.15 leak will happen eventually we are all sure about that. But when will the 4.15 leaks happen and which country is going to leak those files in your opinion ? Dont you think we have had enough of 2.2.3.2 servers and projects ?

1- Gather those items in the same category ( grade ). Simply make them majestic grade ( red ). 2- Edit red grade upgrade chances ( success, fail and destroy ) look inside zoneserver.exe

First find an original cashshop.dat file. Make sure those your server and client cashshop files must be in sync. Also change all m_bview values 0 to 1 while you editing cashshop.dat

can we see the exact error message ?

Probably you're missing a .msh file. I don't know which file contains gold capsules but you can solve this problem by using another client.

Thank you it worked

GU

Couldn't find the offset for https://mega.nz/#!qFEAEKJB!qGWPrgy6OqRRZ10sqv9UzN9UEPhMolCEtwaTD0Hs0Vk this file This file is rfonline.bin indo version

I don't think you can go higher then 65535

I'll give you an example I deleted everything inside quest.dat then i make the file same size as it used to be (6,255,996 bytes). Tested with different zoneserver. None of them give error. Worked normally but when i use yorozuya's zone it crashes cause it sees an unusual file unlike the other zones. ( in my opinion ) So the best thing you can do is use clean files always. Do not delete anything directly inside of script files. If you delete something and try to trick the yorozuya's zone with simply adding byte is not going to work. It'll crash. If you want to edit something. Use working structure, edit carefully and always use datcutter. If you use clean script files you'll see the difference.

This never happened to me. But i figured it out what is happening with Yorozuya's zone. Yorozuya's zone is very sensitive about script files. I've tested some other zone files. Sometimes zoneserver just ignores corrupted script files ( extra bytes or empty script files etc ) but yorozuya's zone is not tolerating any errors so i fixed script files and almost 5 days my zone never crashed.

My zone is crashing lately since i've been editing script files. Do you want to check .dmp files yorozuya ? I cand send it to you if you want. I've got two .dmp files right now each one is 3.7GB

/RFBin/Initialize/ActionPointSystem.ini Open it select all and change with this. Then restart your zone. Reason is your gold point system is closed. 2 Reason. Your action points are not active or you have been passed the end year. I think this will work. ;0 ќчки обработки ;1 ќчки убийства ;2 «олотые очки [Action_Select_0] Use = 1 Reset = 0 Action_Code = 0 BEGIN_YEAR = 2010 BEGIN_MONTH = 10 BEGIN_DAY = 01 BEGIN_HOUR = 12 BEGIN_MINUTE = 00 END_YEAR = 2036 END_MONTH = 01 END_DAY = 01 END_HOUR = 00 END_MINUTE = 00 [Action_Select_1] USE = 1 Reset = 0 Action_Code = 1 BEGIN_YEAR = 2010 BEGIN_MONTH = 10 BEGIN_DAY = 01 BEGIN_HOUR = 12 BEGIN_MINUTE = 00 END_YEAR = 2036 END_MONTH = 01 END_DAY = 01 END_HOUR = 00 END_MINUTE = 00 [Action_Select_2] USE = 1 Reset = 0 Action_Code = 2 BEGIN_YEAR = 2010 BEGIN_MONTH = 10 BEGIN_DAY = 01 BEGIN_HOUR = 12 BEGIN_MINUTE = 00 END_YEAR = 2036 END_MONTH = 01 END_DAY = 01 END_HOUR = 00 END_MINUTE = 00

Is it possible to increase accuracy or dodge of a monster ? If its possible. Are there any information about monster accuracy and dodge inside monstercharacter.dat ? Im using this structure . [filemask="MonsterCharacter.dat"] struct MonsterCharacterFile { u32 MonsterCharacterBlocks; u32 MonsterCharacterColumns; u32 MonsterCharacterBlockSize; Child MonsterCharacter [count=MonsterCharacterBlocks]; } struct MonsterCharacter [preload=1] { u32 m_dwIndex; cstr[len=64] m_strCode; cstr[len=64] m_strName; cstr[len=64] m_strEffectCode; i32 m_nMobGrade; i32 m_nRaceCode; i32 m_nMobRace; i32 m_nKillPoi32; i32 m_nToCombatTime; i32 m_nPincerCnt; i32 m_nPreAttRange; i32 m_nMinMoveDistance; i32 m_nMaxMoveDistance; i32 m_nMobAlienation; i32 m_nMinMoveArea; i32 m_nMaxMoveArea; i32 m_nGuardRecallTimeMS; i32 m_nGuardingArea; float m_fTarDecType; i32 m_nAPTime; i32 m_nAPReset; i32 m_nUglierType; float m_fLevel; i32 m_bMonsterCondition; i32 m_nCriticalTol; i32 m_bExpDown; i32 m_nUpLooting; i32 m_nDnLooting; float m_fExt; float m_fAttFcStd; i32 m_nAttack_DP; i32 m_nProperty; float m_fAttGap; i32 m_bAttRangeType; i32 m_nAttType; float m_fMinAFSelProb; float m_fMaxAFSelProb; float m_fAttSklUnit; float m_fDefSklUnit; float m_fWeakPart; i32 m_bUseDefence; float m_fStdDefFc; float m_fDefGap; float m_fDefFacing; i32 m_nShieldBlock; i32 m_nBlockPer; float m_fFireTol; float m_fWaterTol; float m_fSoilTol; float m_fWindTol; repeat 15 { cstr[len=64] m_strSPCode; } float m_fForceLevel; float m_fForceMastery; float m_fForceAttStd; cstr[len=64] m_strAttTechID1; float m_fAttTech1UseProb; float m_fAttTechID1MotionTime; cstr[len=64] m_strAttTechID2; float m_fAttTech2UseProb; float m_fAttTechID2MotionTime; cstr[len=64] m_strAttTechID3; float m_fAttTech3UseProb; float m_fAttTechID3MotionTime; cstr[len=64] m_strPSecTechID; float m_fPSecTechIDMotionTime; cstr[len=64] m_strMSecTechID; float m_fMSecTechIDMotionTime; i32 m_nInjuryLimit; float m_fMaxHP; float m_fHPRecDelay; float m_fHPRecUnit; float m_fAttSpd; float m_fAttMoTime1; float m_fAttMoTime2; float m_fCrtMoTime; i32 m_nViewAngle; i32 m_nViewAngleCap; i32 m_nCapacityValue; float m_fViewExt; float m_fAttExt; float m_fMRefExt; float m_fCopTime; float m_fMovSpd; float m_fWarMovSpd; float m_fScaleRate; i32 m_bScaleChange; float m_fWidth; float m_fWaitTime; i32 m_nAsitReqRate; i32 m_nAsitAptRate; i32 m_nAsitType; repeat 3 { cstr[len=64] strChildMon; i32 nChildMonNum; } float m_fEmoType; float m_fOffensiveRate; i32 m_nOffensiveType; float m_fDamHPStd; float m_fEmoImpStdTime; float m_fGoodToOrdHPPer; float m_fOrdToBadHPPer; float m_fBadToWorseHPPer; float m_fEspTFProb; float m_fTypeCompTerms; float m_fPSecTechChat; float m_fPAttTechChat; float m_fEmo0Chat; float m_fEmo0ChatProb; float m_fEmo1Chat; float m_fEmo1ChatProb; float m_fEmo2Chat; float m_fEmo2ChatProb; float m_fEmo3Chat; float m_fEmo3ChatProb; float m_fEmo4Chat; float m_fEmo4ChatProb; float m_fAsitReqSteEspChat; float m_fAsitReqSteEspChatProb; float m_fAsitReqSteHelpChat; float m_fAsitReqSteHelpChatProb; float m_fAsitReqSteCopChat; float m_fAsitReqSteCopChatProb; repeat 5 { i32 m_nEmotionCon; i32 m_nEmotionClass; cstr[len=64] m_strEmotionCode; } i32 m_nAttEffType; i32 m_nDefEffType; }