Jump to content
Haru

Mob DB file structure overhaul

Recommended Posts

This is amazing! Looks a lot cleaner, more structured and overall better. Going to make adding mobs alot more fun now ^^ Thank you  @@Haru and @@4144 for this contribution to Hercules, love you guys :D

*codes more NPC scripts*

Share this post


Link to post
Share on other sites

a sight for sore eyes :wub: , in the contrary it will need have more step in creating db for custom monster :lol: , anyway its better than before, thx a loot

Share this post


Link to post
Share on other sites

Suggestion:

 

How about we merge the mob_skill_db? Example.

 

 

  Reveal hidden contents

Share this post


Link to post
Share on other sites

Yes, this is something we're looking into. I would also love to have it streamlined in a similar fashion.

We decided not to merge it right away because of some concerns about the file size, but it is not excluded that it'll be merged in the near future.

Share this post


Link to post
Share on other sites

@@Haru @@4144

How to remove Orc_Load_Card using mob_db2.conf?

 

{
Id: 1190
Inherit: true
SpriteName: "ORC_LORD"
Drops: {
Orc_Load_Card: false or 0 (is not working)
}
},
 
Its not supported?
(I hate touching mob_db.conf :( )
 

Share this post


Link to post
Share on other sites
  On 10/25/2015 at 3:29 AM, kyeme said:

 

@@Haru @@4144

How to remove Orc_Load_Card using mob_db2.conf?

 

{
Id: 1190
Inherit: true
SpriteName: "ORC_LORD"
Drops: {
Orc_Load_Card: false or 0 (is not working)
}
},
 
Its not supported?
(I hate touching mob_db.conf :( )

 

 

@@kyeme, Instead of adding only the Orc_Load_Card in the monster information in mod_db2.conf, Why you don't insert all of its drop and don't add the Orc_Load_Card?

 

@EDIT: I tried it and it's working.

Edited by Frost

Share this post


Link to post
Share on other sites

@@Frost

Yes I did and its working.

 

It is nice if we have a settings like "0" to remove the specific item, so its not hard to see what changes you made

 

 

{
Id: 1190
Inherit: true
SpriteName: "ORC_LORD"
Drops: {
      Brood_Axe: 0
Orc_Load_Card: 0
 },
{
Id: 1288
Inherit: true
SpriteName: "EMPELIUM"
Hp: 342150
},
{
Id: 1191
Inherit: true
SpriteName: "MIMIC"
Drops: {
Emperium: 0
Rosary_: 0
Elunium_Stone: 0
Mimic_Card: 0
}
},

Share this post


Link to post
Share on other sites
  On 10/25/2015 at 4:15 AM, kyeme said:

 

@@Frost

Yes I did and its working.

 

It is nice if we have a settings like "0" to remove the specific item, so its not hard to see what changes you made

 

 

{
Id: 1190
Inherit: true
SpriteName: "ORC_LORD"
Drops: {
      Brood_Axe: 0
Orc_Load_Card: 0
 },

{
Id: 1288
Inherit: true
SpriteName: "EMPELIUM"
Hp: 342150
},

{
Id: 1191
Inherit: true
SpriteName: "MIMIC"
Drops: {
Emperium: 0
Rosary_: 0
Elunium_Stone: 0
Mimic_Card: 0
}
},

 

Yeah, you have a point on that :)

 

@@Haru, @@4144 is it possible to increase the item slot of MVP Drops and Drops?

Share this post


Link to post
Share on other sites

The problem with that approach is that you're assuming that no monsters have the same drop listed twice (while it's a valid situation).

 

This is the mob_db entry for PORING:

// Mob DB entry for PORING{    Id: 1002    // ...    Drops: {        Jellopy: 7000        Knife_: 100        Sticky_Mucus: 400        Apple: 1000        Empty_Bottle: 1500        Apple: 150        Unripe_Apple: 20        Poring_Card: 1    }},
If you added this in the mob_db2:
{    Id: 1002    Override: true    Drops: {        Apple: 0 // Which apple am I removing? The first? The last? Both?    }},
What would happen?

 

Also if you added:

{    Id: 1002    Override: true    Drops: {        Jellopy: 5000 // Am I replacing the existing Jellopy? Or adding a new drop?        Red_Potion: 1000 // What does this do? Replaces an existing entry? Adds a new drop?    }},
it wouldn't be clear what the result would be.

 

To remove all existing entries and add a completely different drops list, what would you do? If it was able to override, you'd need a reasonable way to specify that you want to empty the list.

 

 

 

About increasing the amount of drops and mvp drops, it's possible but it requires several source modifications (and possibly a very radical change in how they're represented in the SQL DB). I'm for the change, but I expect a lot of people to complain if we do, and their control panel breaks.

Share this post


Link to post
Share on other sites

@@Haru

You have a good point sir, how about adding Drops_Add and Drops_Remove  :D

 

// Mob DB entry for PORING{    Id: 1002    // ...    Drops: {        Jellopy: 7000        Knife_: 100        Sticky_Mucus: 400        Apple: 1000        Empty_Bottle: 1500        Apple: 150        Unripe_Apple: 20        Poring_Card: 1    }},//In mob_db2.conf{    Id: 1002    Inherit: true    Drops: {        Jellopy: 5000 // Replace the current Jellopy        Sticky_Mucus: 1000 // Replace the current Sticky_Mucus    }    Drops_Add: {        Mjolnir: 1000	// Poring will now drop mjolnir    }    Drops_Remove: {        Apple: 1000 // Remove the existing Apple with 1000 rate        Apple: 150 // Remove the existing Apple with 150 rate    }},

Share this post


Link to post
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.   Restore formatting

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

Important Information

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