Modification of @mi

[Aleos]

Whenever a server has RENEWAL_EXP or RENEWAL_DROPS active, the @mi command becomes somewhat skewed informatively to the player. Pre-renewal just had to read directly from the mob_db since there were no variations of player level versus monster level. Now that there is a variation, should @mi be modified to adjust for this or should a separate command be created?

[Emistry]

isnt that we have a setting that can manipulate this ?

trunk/conf/battle/gm.conf

// requires RENEWAL_DROP to be enabled (src/map/config/renewal.h)
// modifies @mobinfo to display the users' real drop rate as per renewal_drop formula
// modifies @iteminfo to not display the minimum item drop rate (since it can't tell the mob level)
atcommand_mobinfo_type: 0

i think enable users to select which settings they want would be better.

[Aleos]

Ah! So I knew I wasn't going crazy. I could have sworn something was implemented for it, so should one be added for exp too then since drop is there?

Edit: It was added in r16337. But looking at the revision diff and the current atcommand.c, it seems it was completely removed from mobinfo at some point!

[MarkZD]

IMO, it should be done with a special parameter or on another function and let the @mobinfo keeps regarding only to the mobs.

So remove the atcommand_mobinfo_type, and let the new command enabled by default.

#ifdef RENEWAL_DROP &&|| RENEWAL_EXP, shows the referenced infos, otherwise show user a message informing it just work with those renewal settings or just shows the default drop, exp.

[Aleos]

Applied in r17173.