Maxlevel in addition to NPC level
This will add a maxlevel field for NPCs you want to scale dynamically to level. Currently, it does everything except set HP automatically. That will have to be set manually but can be changed by server admins. It also allows ATK to be calculated for NPCs with 0 attack also regardless of settings, and it sets generic stats for NPCS if they are 0.
If you set the field to 0, it will do nothing, so it does not affect anything past what is currently there. If someone wants to make their own formulas for generating NPCs, tweak npc.cpp. By default all stats are 75 so i'd say if you want NPCs to have custom stats, go for it or set it manually in the database, as it only checks for if stats are 0. The minlevel field itself chooses a random number between level and maxlevel, so if you have maxlevel as 10 and level as 1, it will choose a random number between 1 and 10. There's existing calculations for min/max dmg, so I left them there. Required SQL: Code:
ALTER TABLE `npc_types` ADD COLUMN `maxlevel` tinyint NOT NULL DEFAULT 0; Code:
Index: beacon.cpp |
I have a solution to the HP issue introduced with this code: Adding a random HP field! This allows for random HP between values.
If defined in the database, hp will be a minimum value and hpmax will be a maxhp value, in a similar fashion that level works by choosing a random number. That way fights are a wee bit more dynamic. I don't know if this is stepping too far into the custom realm where it should be posted in custom code, but.. Diff will be uploaded after I test this change. |
Ok, here's the diff for hpmax. You will need this SQL:
ALTER TABLE `npc_types` ADD COLUMN `hpmax` tinyint NOT NULL DEFAULT 0; And here's the diff, including the previous post. All of this is done on r830. Code:
Index: beacon.cpp |
Quote:
|
Wouldn't it make more sense if the level and HP were based on the same random number so that higher level mobs have more HP and vice versa.
Code:
max_hp = max_hp + ((level - moblevel)/(maxlevel - moblevel))*(hpmax - max_hp) |
Quote:
|
Oh, in that case you still have a problem with HP not being adjusted for level which will have a profound effect at lower levels.
|
Quote:
Otherwise i'd do that. That maxlevel feature is something that could be useful if given defaults. |
Just an FYI; Going forward, we are not putting names into the actual source code comments anymore. We have even been going through and removing some that are already in there. The names will go into the changelog like normal, and that is the best place to keep track of who did what. Just making note of that for future submissions.
Here is the code from the #spawn command that autocalculates MaxHPs: Code:
//Calc MaxHP if client neglected to enter it... We could always just scale HPs (and possibly other stats) based on the mob's actual level vs the level set in the database. So, if the level is set to 10, and max level is set to 12, that would mean mob stats/hps could scale up 20% from what they are set to in the DB. So, a level 11 NPC would scales it's hps by 1.1, which would mean a 100HP level 10 NPC would have 110HPs at level 11. and 120HPs at level 12. This scaling would probably work well in most cases. The formula for that should be pretty easy. Something like this should work: Code:
maxhp += (maxhp * ((moblevel / level) - 1)); If we wanted to be more flexible, though, we could add another field for scaling rates. The default for the scaling field would be 100. So, if we wanted a particular NPC's stats to scale at a faster rate as levels increase, we could set the scale rate to 200 (double scaling rate), or if we wanted it's stats to scale slower as levels increase, we could set it to 50 (half scaling rate). The formula for that would be something like this: Code:
maxhp += (maxhp * (((moblevel / level) - 1) * (scale_rate / 100))); Code:
STR += (STR * (((moblevel / level) - 1) * (scale_rate / 100))); Just something to consider. The main difference from what Secrets has posted and this is that there wouldn't be a need for a maxhp field, and instead there would be a scaling_rate field. I really like the idea of the whole random level NPC thing, no matter how it gets put in. We might as well work out all of the details now before it is committed so the system doesn't need to be adjusted afterward. It can be a pain to make adjustments after people have already started using a new system like this. Any thoughts? |
It's kind of the same idea edge did. We had a % modifier on stats, and the stats would scale to level. I would totally be for that, if only for making custom content easier.
The main issue a lot of server ops have in balancing NPCs is making it so their stats are challenging for the level they are at. Otherwise, you have level 98 mobs one shotting people because they think "higher level is better". If you have a generic scaling for NPCs, it would make it a ton easier to scale to custom content, and encounters in general. I would love a variable like this for creating almost anything. If this system was implemented, i'd also remove the hpmax submission. |
If I get time, I might try to work out the details to get the new maxlevel and scaling stuff added in. And after that, there is always the possibility of making use of that system through quest commands later.
Is anyone apposed to the idea of the scaling system to go with the new maxlevel system idea? Or are there any suggestions on how to handle it in a better way? EDIT: Corrected my formulas above so they would actually work as intended. |
Looking at the data in this post it would seem the live HP scaling was a bit of a hack. It would appear that 20 HP is added to base HP for each additional level. Obviously this may and probably did change if they continued to use scaling code in expansion releases.
|
This has already been added to the SVN. The scaling we use is based on percentages of current stats depending on the relative level of the spawned NPC vs it's base level and base stats.
|
Yeah, I noticed. I just thought that this would be an interesting little bit of info for anyone who was following this thread. Maybe bumping this server code submissions thread was not the most appropriate way to highlight this info.
|
All times are GMT -4. The time now is 08:32 PM. |
Powered by vBulletin®, Copyright ©2000 - 2025, Jelsoft Enterprises Ltd.