I think it sounds good. Some stuff, as you pointed out, that is currently in npc_types should be moved over to the profiles.
I'll do what I can to make the code work with the different database configurations, since npc_types will undergo some large scale changes.
I also want to be able to make the profiles as flexible as possible, so you can do things like randoms, percentages, fixed values, etc. I'll do some thinking on that. Probably the best way would be to do it with varchar fields, and then have ways of entering values, such as:
Code:
%+10 (Increase value by 10%)
%-10 (Decrease value by 10%)
10 (Make value 10)
+10 (Increase value by 10)
-10 (Decrease value by 10)
r10-20 (Set value to a random value between 10 and 20)
r+10-20 (Increase value random between 10 and 20)
r-10-20 (Decrease value random between 10 and 20)
Maybe add in a variable, as well for levels:
Code:
l* (Level times)
l% (Level divided by)
l- (Level minus)
l+ (Level plus)
This could be used anywhere a value is indicated, for example:
[code]
%+l*10
[code]
Would mean, "Increase value by (level * 10) Percent.
Thoughts?
Threaded Mode
