Skip to content

Commit

Permalink
Corrected some errors inteh Rebellion skill_tree and job_db
Browse files Browse the repository at this point in the history
- Fixed bugreport:7724 (thanks ot Poison, LuLu)
  http://hercules.ws/board/index.php?app=tracker&showissue=7724
- Please note that, in Pre-Renewal, the job_db values aren't accurate,
  since the Rebellion class never existed before. It is currently using
  values from the Gunslinger class, just like Oboro and Kagerou use
  values from the Ninja class.

Signed-off-by: Haru <haru@dotalux.com>
  • Loading branch information
MishimaHaruna committed Sep 28, 2013
1 parent 71af4a3 commit f8f073b
Show file tree
Hide file tree
Showing 3 changed files with 8 additions and 6 deletions.
2 changes: 1 addition & 1 deletion db/pre-re/job_db1.txt
Expand Up @@ -280,4 +280,4 @@
// Oboro
4212, 26000,80 , 0 ,515 ,400 ,500 ,2000 ,2000 ,2000 ,2000 ,2000 ,2000 ,2000 ,2000 ,2000 ,2000 ,2000 ,2000 ,2000 ,2000 ,2000 ,2000 ,2000 ,2000 ,2000 ,2000 , 750 ,2000
// Rebellion
4215, 28000,88 , 0 ,450 ,540 ,2000 ,2000 ,2000 ,2000 ,2000 ,2000 ,2000 ,2000 ,2000 ,2000 ,2000 ,2000 ,2000 ,2000 ,2000 ,2000 ,490 ,590 ,440 ,940 ,1040 ,2000 ,2000 ,600
4215, 28000,88 , 0 ,450 ,500 ,2000, 2000, 2000, 2000, 2000, 2000 ,2000 ,2000 ,2000 ,2000 ,2000 ,2000 ,2000 ,2000 ,2000 ,2000 , 700 , 750 , 700 ,1500 ,1500 ,2000 ,2000
9 changes: 5 additions & 4 deletions db/pre-re/skill_tree.conf
Expand Up @@ -11,16 +11,16 @@
// http://hercules.ws/board/topic/1188-skill-tree-db-redesign/
//================ Structure Example =================
/*
Job_Name: { // Job names as in src/map/pc.c (they are hardcoded at the moment so if you want to add a new job you should add it there)
Job_Name: { // Job names as in src/map/pc.c (they are hardcoded at the moment so if you want to add a new job you should add it there)
inherit: ( "Other_Job_Name" ); // Base job from which this job will inherit its skill tree. NV_TRICKDEAD inheritance is skipped for non-novices from the source

skills: { // SKILL_NAMEs come from the Name (16th column) value in db/pre-re/skill_db.txt
SKILL_NAME1: Max_Level // Use this for skills that don't have other skill prerequisite; Max_Level is a numeric value that should match your client side files
SKILL_NAME2: { // Use this for skills which have other skills as prerequisites
MaxLevel: Max_Level // Max_Level is a numeric value that should match your client side files
SKILL_NAME_PREREQUISITE: Level_Prerequisite // The prerequisite skill and min level for having this skill available. Should also match your client side files
SKILL_NAME_PREREQUISITE2: Level_Prerequisite2 // You can add as many prerequisite skills as you want. Minimum of 1 if you add a skill this way
}
SKILL_NAME_PREREQUISITE2: Level_Prerequisite2 // You can add as many prerequisite skills as you want. Minimum of 1 if you add a skill this way
}
}
*/
//====================================================
Expand Down Expand Up @@ -1545,7 +1545,7 @@ Lord_Knight: {
KN_SPEARMASTERY: 10
KN_PIERCE: 5
KN_SPEARSTAB: 5
KN_RIDING: 1
KN_RIDING: 1
}
LK_HEADCRUSH: {
MaxLevel: 5
Expand Down Expand Up @@ -3851,6 +3851,7 @@ Oboro: {
OB_ZANGETSU: 2
}
}
}
Rebellion: {
inherit: ( "Gunslinger" );

Expand Down
3 changes: 2 additions & 1 deletion db/re/skill_tree.conf
Expand Up @@ -11,7 +11,7 @@
// http://hercules.ws/board/topic/1188-skill-tree-db-redesign/
//================ Structure Example =================
/*
Job_Name: { //Job names as in src/map/pc.c (they are hardcoded at the moment so if you want to add a new job you should add it there)
Job_Name: { // Job names as in src/map/pc.c (they are hardcoded at the moment so if you want to add a new job you should add it there)
inherit: ( "Other_Job_Name" ); // Base job from which this job will inherit its skill tree. NV_TRICKDEAD inheritance is skipped for non-novices from the source

skills: { // SKILL_NAMEs come from the Name (16th column) value in db/re/skill_db.txt
Expand Down Expand Up @@ -3848,6 +3848,7 @@ Oboro: {
OB_ZANGETSU: 2
}
}
}
Rebellion: {
inherit: ( "Gunslinger" );

Expand Down

0 comments on commit f8f073b

Please sign in to comment.