Bug Tracker Migration

June 3rd
Good news everyone! The staff has decided that it is time to slowly kill off this Bug Tracker. We will begin the process of slowly migrating from this Bug Tracker over to our Github Issues which can be found here: https://github.com/HerculesWS/Hercules/issues

Over the next couple of days, I will be closing off any opportunity to create new reports. However, I still will keep the opportunity to reply to existing Bug Reports. Doing this will allow us to slowly fix any bug reports we have listed here so that we can easily migrate over to our Issue Tracker.

Update - June 7th 2015: Creating new bug posts has been disabled. Please use our https://github.com/HerculesWS/Hercules/issues tracker to post bugs. Users are still able to reply to existing bug posts.

- Administration

Issue Information

• Issue ID

  #000746

• Severity

  1 - Low

• Status

  Confirmed

• Return to Issue Listing

Issue Confirmations

• Yes (0)No (0)

0

Random Monster Spawning Code Cleanup

Posted by Hercules Bot on 04 January 2008 - 10:46 PM

Originally posted by theultramage
http://www.eathena.w...ker&showbug=746

The mob_db structure has a member, "int summonper[4]", representing summon rates for each mobdb entry for Dead Branch, Bloody Branch, Poring Box and Red Pouch of Surprise. There is also an array/structure called 'summon[4]' that also seems to track this stuff. During mobdb loading, both of these get filled in some weird fashion.

I think the only place that these get used is mob_get_random_id(). I suggest this thing be cleaned up and its purpose made clear.
See r12013 for my motivation (btw, blame goes to r2697 *_*).

• Back to top

1. Bug Tracker
2. → Core
3. → Severity: Low
4. → Status: Confirmed
5. Privacy Policy
6. Hercules Forum Rules ·