New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Creature balancing #985
Comments
elemental as in fire, water, earth and air? or as in the previously used in OD physical, magic, acid? |
elemental is the "generic" name for what we called "acid" |
As for the triangle, I would propose as a first step to try for 1 creature of each tier:
For example, if we consider 3 tier 1 creatures:
Spider would have Attack: 5 phy, 0 mag, 0 ele. Def: 2 phy, 4 mag, 0 ele. I guess that with this stats, Spider > Tentacle, Tentacle > Slime and Slime > Spider. @OpenDungeons/developers WDYT ? |
I would switch stats for spider to tentacle since spiders can poison a bit as well, otherwise its good |
Looks good! |
No problem, it was only an example. I'm not even sure that these creatures are the tier 1 keeper (since there are more like roach, cavehornet or the other tentacle). BTW, since we have many creatures on keeper side and not enough for heroes, it could be a good idea to switch some. Any idea ? Since we are talking about creature balancing, at which level do we except a creature to become better than its same tier better unit ? In my example, at which level does the slime become better than a level 1 tentacle ? |
thats pretty tricky, i tried to use a golden rule when i balanced last time, and that was, even the weakest creature should be able to hurt a bit the strongest one when both are at LV1. |
Seems good. For my part, I would say that level 7 to 10 creatures should begin to win vs their same tier better unit. |
Maybe not 'switch' but 'add' for heroes? Like
Maybe, there's a point in adding a 'balanced' creature? Which has equals on all. It'll be weaker than the same rank creatures, but will be more universal.
Maybe, there's a point to try this logic in the same tier: (rank 2 unit) equals 2 (rank 1 units of the same level) (50% kill depending on the 'first blow'). (rank 2 unit lvl.1) equals (rank 1 unit lvl.7) |
My idea was to not put too much burden on our artists shoulders and to go fast (as we have many creatures on keeper side but not enough on hero's). But if you want to add some new creatures, you are welcome. However, I think we need rooms more than creatures ATM.
Yes. Maybe for "special" creatures that do not spawn through the portal like skeleton / lich. I think we should try to avoid what was, IMHO, the biggest problem of DK: balancing. Basically, the idea was always to train one of the best creatures (for me, the vampire) and unleash it in an enemy dungeon where it would kill everybody. That's why we should try to add some more strategy and the triangle is IMHO, one of the best ways to achieve that.
Yes, we should try to balance creatures of different tiers as well. |
I've had a look at the creature list. As we can see in the wiki, we have 6 keeper tier 2 creatures (wyvern, lizardman, orc, goblin, tentacle, kreatur) + roach To have at least 3 creatures per tier for both sides, I would propose to change some creatures teams. Moreover, we could have 3 tier 4 creatures (allowing more interesting strategies than rushing blindly to tier 4 ASAP) That will leave:
Hero:
For balancing purposes, I would propose to try to:
Then, we will have to give some skills (but it will be for after ^^) @OpenDungeons/developers WDYT ? |
not bad, in absence of enought creatures for everyone, its a good plan. |
Looks perfect on paper :D |
well, I will try with some basic stats, each creature being perfect opposite to an hero. Then, we will see what we want ^^ |
Just like skills, elemental damages have been implemented. But ATM, no creature or spell use it.
Following #877 we said that we would like to have something like 3 creatures per tier specialized in one of the type and with a triangle. For example, if the 3 creatures are A, B an C, at same level, A > B, B > C and C > A.
The text was updated successfully, but these errors were encountered: