Skip to content
This repository has been archived by the owner on Aug 8, 2019. It is now read-only.

Lich Class Revamp #816

Open
JukeDragh opened this issue Feb 21, 2018 · 4 comments
Open

Lich Class Revamp #816

JukeDragh opened this issue Feb 21, 2018 · 4 comments

Comments

@JukeDragh
Copy link
Contributor

JukeDragh commented Feb 21, 2018

With the Lich Tower coming up sometime in the future, I think the Lich needs a few more things to become a class players to want to use.

Three New Spells:
Finger of Death- Deals a percentage of the target's health based on the percentage difference between the caster's int and target's con. Should cost a percentage of mp instead of a static value (75%?)

Soulfire- Deals a moderate to low amount of damage but doesn't cost mp and regenerates mp instead.

Phylactery Shatter- A low chance spell that destroys one of the lich's phylacteries to deal a large amount of damage and restore all of their mp.

The general combat cycle would consist of the lich using FoD to deal a large amount of damage early on and Soulfire afterwards to get the mp back to cast FoD again to, hopefully, kill the opponent.
Shatter is a comeback mechanism that would only happen about 1-2 times during a long fight and would give them some breathing room to compensate for potentially shortening their lifespan.
FoD is strongest against players who haven't been specing into con (i.e. Mage, Necro, and Bito).

@JukeDragh
Copy link
Contributor Author

Feb 21, 2018, 12:44:01 AM [ 15 [NERF] Zigniber, the Jailbird ] Maybe make the mp cost a flat value plus the percentage.

@JukeDragh
Copy link
Contributor Author

JukeDragh commented Feb 21, 2018

Possibly lower the amount of hp that con gives so as to avoid the 10mil hp + 36 phylactery nightmare
Current: https://github.com/IdleLands/IdleLands/blob/master/src/core/base/profession.js#L6

@JukeDragh
Copy link
Contributor Author

Will probably need to move the phylactery code out of summon.js.

@JukeDragh
Copy link
Contributor Author

Possibly give it some way to prevent or defend against stuns?

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant