Yes, a lot of work, and no I am not saying a dev should fix DB mob regen rates - just how they effect the proposed rule. If we think about it, admins could get a generic "this is how it is... 5% per level" or whatever by default. But should I want all my boss mobs to be 20% per level, I simply go to my npc_types table and make the changes on MY server according to my desires. Nothing to do with dev coding. I am thinking that the hp_regen and mana_regen in the npc_types table is already there, let's use it as an offset instead of "regen xx mana per tick", as I think it is now(?)

Those fields are different though.. when they work, they are for regen all the time (including during combat).

So, since non-combat mob regen is a different thing, it would require a new field in the db, changes to all of the tools that work with mobs, as well as code to chech the db value and override the rule if it's different. Or it could be set up as whatever the value is in the db is the percentage of total hitponts the mob will regen in one tic. 0 is off, and a float value could determine.

Either way though, it becomes a lot more complicated.

I'm not saying it's a bad idea, just explaining that this can be a simple fix in the code, or a huge project. At least for now, since this is such a critical showstopping problem (I'd go so far as to say it can be an exploit) not to have it, I'd rather see the simple fix fast than the "complete system" done eventually.

Any fix to this will be a vast improvement, I'm so glad that I remerged my code with the source (aside from our custom stuff anyway). This fix will sooo make my day. =)

Dax

I am posting my fix for this in the code submissions forum. I put in a variable for it, so you can turn it off / adjust it if you want.

Dax

Updated this for a Rules-based fix (rather than a variable-based fix), as requested by CaveDude.

Dax