Jump to content
  • 0
Sign in to follow this  
utofaery

I need help converting this line from old eathena format to Hercules format

Question

from old eathena >> it does has this >> skill_unit_db.txt 

and in skill_unit_db.txt has line as below

 

115,0x90,    ,  0, 1,1000,enemy, 0x28000    //HT_SKIDTRAP        <<  "Changed Line"

 

and now in Hercules DB folder all other skill files is mashup and fix into on skill_db.txt 

which is why I need to know how can I convert the "Changed Line" above to new hercules format.


The reason I asking is that within hercules DB has no detailed explaination of new skill_db.txt

 

Edited by utofaery

Share this post


Link to post
Share on other sites

5 answers to this question

Recommended Posts

  • 0
2 hours ago, utofaery said:

The reason I asking is that within hercules DB has no detailed explaination of new skill_db.txt

nope, read db/re/skill_db.conf
https://github.com/HerculesWS/Hercules/blob/stable/db/re/skill_db.conf#L221
the header of that file already tell you what each line means

and rathena skill keeping that format
https://github.com/rathena/rathena/blob/master/db/re/skill_unit_db.txt#L50

Share this post


Link to post
Share on other sites
  • 0

My bad was going through my very old archive trying to migrate stuff from old eathena db folder.

Now I know it's all inside the skill db merged 

but I got new question:

Q1: what's the GM_SANDMAN do?

 

Q2: what can I do to make monster that was spawn'ed from dead branch to be announced map wide?

I don't know how to get the spawn'ed monster's ID.

 

Q3: increase size of mob.c:summon variable

how to do this ?

I tried to add custom branches and this line output in map-server

[Debug]: Can't store more random mobs from mob_customNormal.txt, increase size o
f mob.c:summon variable!

 

Edited by utofaery

Share this post


Link to post
Share on other sites
  • 0

Q1 GM_SANDMAN
exactly what it says, just a skill only accessible by GMs to cast player to sleep
this skill is granted by angra manyu (Item ID 1599)

 

Q2 add announcement

{
	Id: 604
	AegisName: "Branch_Of_Dead_Tree"
	Name: "Dead Branch"
	Type: "IT_USABLE"
	Buy: 50
	Weight: 50
	BuyingStore: true
	Script: <" monster "this",-1,-1,"--ja--",-1,1,""; ">
},

add announce script command in the Script: field

b. randomize monster
https://github.com/HerculesWS/Hercules/blob/stable/db/re/mob_branch.txt

 

Q3. no idea what's the meaning of this question
if you want to summon a large size monster,

*monster("<map name>", <x>, <y>, "<name to show>", <mob id>, <amount>{, "<event label>"{, <size>{, <ai>}}})

 

Share this post


Link to post
Share on other sites
  • 0

Q3 is actually I trying to clone the mob_branch.txt to a new Mob_customBranch.txt 

changes to mob.c and mob.h respectively has be done.

Spoiler

        DBPATH"mob_branch.txt",
        DBPATH"mob_poring.txt",
        DBPATH"mob_boss.txt",
        "mob_pouch.txt",
        "mob_classchange.txt",
        "mob_customNormal.txt",
        "mob_customMVP.txt"};

 

#define MAX_RANDOMMONSTER 9 //xsa // 5
#define MAX_MOB_DB 20000
 

but map server spit out the error of 

[Debug]: Can't store more random mobs from mob_customNormal.txt, increase size o
f mob.c:summon variable!

if I clone content from DBPATH"mob_branch.txt"  to mob_customNormal.txt

so in the end is there a limitation of something or can I do to prevent map server from spitting out that kind of debug warning?


 

Share this post


Link to post
Share on other sites
  • 0

if me, want to add another custom dead branch, I would just write it in very simple term

getitem F_Rand(1201,1101,501,502,503), 1;

those monster box ... dead branch has some kind official rate ...
if ignore the rate part, a simple script function will do

https://rathena.org/board/topic/78263-scripting-faqtipstricks/
PS: still haven't include this in my blog ...

Share this post


Link to post
Share on other sites

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
Sign in to follow this  

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.