Jump to content

How can TRAIT POINTS be activated in the 3rd job?


takechi

Recommended Posts


  • Group:  Members
  • Topic Count:  2
  • Topics Per Day:  0.00
  • Content Count:  4
  • Reputation:   0
  • Joined:  08/30/13
  • Last Seen:  

I need to activate the Trait points in the 3rd job, since it is only active in the 4th, thank you very much

Link to comment
Share on other sites

  • 2 months later...

  • Group:  Members
  • Topic Count:  77
  • Topics Per Day:  0.02
  • Content Count:  462
  • Reputation:   61
  • Joined:  08/28/12
  • Last Seen:  

This would be nice to know, same for 2nd class. 😄

 

Link to comment
Share on other sites

  • 2 months later...

  • Group:  Members
  • Topic Count:  3
  • Topics Per Day:  0.00
  • Content Count:  14
  • Reputation:   0
  • Joined:  05/02/18
  • Last Seen:  

There's this line in pc.cpp

void PlayerStatPointDatabase::loadingFinished(){
	const uint16 trait_start_level = 200;
	std::shared_ptr<s_statpoint_entry> level_one = this->find( 1 );

Maybe change the 200 to any level ? 🤔
------------------------------------------------------------------------------------------------------------------------------------
Also in statpoint.yml starting from 201 we can see there's TraitPoints: x .

  - Level: 200
    Points: 4099
  - Level: 201
    Points: 4099
    TraitPoints: 3
  - Level: 202
    Points: 4099
    TraitPoints: 6
  - Level: 203
    Points: 4099
    TraitPoints: 9

Maybe also insert the TraitPoints: x to desired level ? 🤔

Edited by aspd197
adding more thoughts
Link to comment
Share on other sites

  • 2 months later...

  • Group:  Members
  • Topic Count:  0
  • Topics Per Day:  0
  • Content Count:  1
  • Reputation:   0
  • Joined:  06/13/23
  • Last Seen:  

Just changing the trait_start_level and the statpoint.yml didn't work for me. Therefore, I looked through the code and found a way to do this. However, I am not sure if all of these changes are necessary.

First, I added TraitPoints: x in statpoint.yml from level 101 onward and changed the trait_start_level to 100 like mentioned above:

void PlayerStatPointDatabase::loadingFinished(){
	const uint16 trait_start_level = 100;

Then in pc.cpp, you can find JOBL_FOURTH branches and remove the JOBL_FOURTH check. Here are the ones that I changed:

if ((sd->class_&JOBL_FOURTH) != 0) {
	sd->status.trait_point += battle_config.trait_points_job_change;
}
if ((b_class & JOBL_FOURTH) && !(previous_class & JOBL_FOURTH)) {// Change to a 4th job.
    sd->status.trait_point += battle_config.trait_points_job_change;
    clif_updatestatus(sd, SP_TRAITPOINT);
    clif_updatestatus(sd, SP_UPOW);
    clif_updatestatus(sd, SP_USTA);
    clif_updatestatus(sd, SP_UWIS);
    clif_updatestatus(sd, SP_USPL);
    clif_updatestatus(sd, SP_UCON);
    clif_updatestatus(sd, SP_UCRT);
}
if( class_ & JOBL_FOURTH ){
    max = battle_config.max_fourth_parameter;
    break;
}
// Set trait status limit
if( class_ & JOBL_FOURTH ){
	max = battle_config.max_trait_parameter;
}else{
  	max = 0;
}
Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  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...