[Source] Help with Pets

[NickHough]

Hello,

For some reason people past level 59 can't do the quest to raise pet level

As well people can't use their pet feed on their pets, i know there is a fix for this but i couldn't find it anywhere i looked.

There is also another wierd thing that happens, my server is maxed at level 300 (all works fine you can get to it without problems) but when you are level 300 people see your level as only level 44 is this a bug or is it just a mover problem?

If anyone has the same as me please help me to fix them.

Thanks
Nick Hough

[MentaL]

[ShadowDragon]

The pet quest thing can be fixed in propquest.inc
Find the quests and make them available to all jobs.

I don't know about the pet feed thing.

And just a quick thing I noticed about the level problem. 300 - 256 = 44
If you know much about programming, you'd recognize 256 as being the max value for a BYTE variable (technically it's 255, but including 0, it's 256 unique values). I'm guessing the level is getting cast as a BYTE type, which causes a value above 256 to "run over" and restart as 1. If my theory is correct, a level 257 would appear as level 1, 275 would appear as 19, etc.

[NickHough]

yeah that is true, but if your theory is correct then it is just s simple byte to int conversion then?

as for the propquest.inc i will post my current one for MAFL_PETTAMMER01 here

QUEST_PETTAME01 // 알 -> D급
{
    SetTitle
    (
        IDS_PROPQUEST_INC_002010
    );
    
    setting
    {    
    
        SetRepeat(1);
        SetCharacter( "MaFl_PetTamer" );
        SetBeginCondLevel( 1, 350 );
        SetBeginCondParty( 0, 0, 0, 0 );
        SetBeginCondJob( JOB_VAGRANT, JOB_MERCENARY, JOB_ACROBAT, JOB_ASSIST, JOB_MAGICIAN, JOB_KNIGHT, JOB_BLADE, JOB_JESTER, JOB_RANGER, JOB_RINGMASTER, JOB_BILLPOSTER, JOB_PSYCHIKEEPER, JOB_ELEMENTOR, JOB_KNIGHT_MASTER, JOB_BLADE_MASTER, JOB_JESTER_MASTER, JOB_RANGER_MASTER, JOB_RINGMASTER_MASTER, JOB_BILLPOSTER_MASTER, JOB_PSYCHIKEEPER_MASTER, JOB_ELEMENTOR_MASTER, JOB_KNIGHT_HERO, JOB_BLADE_HERO, JOB_JESTER_HERO, JOB_RANGER_HERO, JOB_RINGMASTER_HERO, JOB_BILLPOSTER_HERO, JOB_PSYCHIKEEPER_HERO, JOB_ELEMENTOR_HERO, JOB_LORDTEMPLER_HERO, JOB_STORMBLADE_HERO, JOB_WINDLURKER_HERO, JOB_CRACKSHOOTER_HERO, JOB_FORCEMASTER_HERO, JOB_FLORIST_HERO, JOB_MENTALIST_HERO, JOB_ELEMENTORLORD_HERO );
        SetBeginCondPetLevel( 0 );
        SetEndCondPetLevel( 0 );
        SetEndCondPetExp( 100 );
        SetEndRewardPetLevelup();
        SetHeadQuest( 6004 );
        }

    SetDialog
    (
        QSAY_BEGIN1, 
        IDS_PROPQUEST_INC_002011
    );
    
    SetDialog
    (
        QSAY_BEGIN2, 
        IDS_PROPQUEST_INC_002012
    );

    SetDialog
    (
        QSAY_BEGIN_YES,
        IDS_PROPQUEST_INC_002013
    );

    SetDialog
    (
        QSAY_BEGIN_NO, 
        IDS_PROPQUEST_INC_002014
    );

    SetDialog
    (
        QSAY_END_COMPLETE1, 
        IDS_PROPQUEST_INC_002015
    );

    SetDialog
    (
        QSAY_END_FAILURE1, 
        IDS_PROPQUEST_INC_002016
    );

    state 0
    {

        SetDesc
        (
            IDS_PROPQUEST_INC_002017
        );
        
    }

    state 14
    {

        SetDesc
        (
            IDS_PROPQUEST_INC_002018
        );
        
    }
} 

[ShadowDragon]

Yeah, you just have to find where the problem is and change the type on it.

And about the quest thing, why not just delete the entire line for SetBeginCondJob? I'm pretty sure that would make it be no job requirement.

[NickHough]

Okay i will try that :) thanks