Simplification of felid extra-lives mechanics
Posted: Friday, 7th February 2020, 04:26
Hi all,
With all respect to anyone who contributed to, or is a fan of, the current extra-lives mechanics for felids, I personally feel and submit that they are overly complicated, which causes both 1) confusing, difficult-to-understand source code, and 2) players being confused trying to understand exactly how the rules work, and perhaps potentially even feeling treated unfairly by the mechanics. A simplification would be very much in line with the "Clarity" subtopic of DCSS's "Philosophy."
I propose the following mechanics: At every 3rd level, starting at level 4, you gain an extra life – same as the way it is now. Difference: there is no maximum to the number of extra lives you possess. However, upon death and revival, you have a condition placed upon you, maybe “NoRevive” or maybe a snazzier name can be conjured up. This condition goes away after some appropriately-determined amount of XP gain, similar to stat drain or skill drain. If you are killed with the condition active, game over. Once the condition is lifted, you again have the privilege of being able to revive – assuming, of course, that you still have at least one extra life in reserve. The benefits of this are as follows:
• It is far more straightforward, less complicated, and less confusing than the current mechanics.
• There is no danger of a player feeling cheated by being in the situation of having 0 extra lives when a felid at the same experience level, and who has arguably done a poorer job of survival and should be closer to game-over, might still have 1 or more extra lives.
• It still prohibits dying multiple times in quick succession by way of the NoRevive condition.
• Not only is it much simpler and easier to understand, but it can also make sense thematically. Try coming up with a thematic explanation for the current ruleset, vs. trying to explain that you simply cannot revive too soon after your most recent revival.
I'd be willing to work on the required code changes myself, but before investing the time and work I'd like to see what other people think of this idea. Thoughts? Like? Dislike? Questions? Criticisms?
Thanks in advance!
With all respect to anyone who contributed to, or is a fan of, the current extra-lives mechanics for felids, I personally feel and submit that they are overly complicated, which causes both 1) confusing, difficult-to-understand source code, and 2) players being confused trying to understand exactly how the rules work, and perhaps potentially even feeling treated unfairly by the mechanics. A simplification would be very much in line with the "Clarity" subtopic of DCSS's "Philosophy."
I propose the following mechanics: At every 3rd level, starting at level 4, you gain an extra life – same as the way it is now. Difference: there is no maximum to the number of extra lives you possess. However, upon death and revival, you have a condition placed upon you, maybe “NoRevive” or maybe a snazzier name can be conjured up. This condition goes away after some appropriately-determined amount of XP gain, similar to stat drain or skill drain. If you are killed with the condition active, game over. Once the condition is lifted, you again have the privilege of being able to revive – assuming, of course, that you still have at least one extra life in reserve. The benefits of this are as follows:
• It is far more straightforward, less complicated, and less confusing than the current mechanics.
• There is no danger of a player feeling cheated by being in the situation of having 0 extra lives when a felid at the same experience level, and who has arguably done a poorer job of survival and should be closer to game-over, might still have 1 or more extra lives.
• It still prohibits dying multiple times in quick succession by way of the NoRevive condition.
• Not only is it much simpler and easier to understand, but it can also make sense thematically. Try coming up with a thematic explanation for the current ruleset, vs. trying to explain that you simply cannot revive too soon after your most recent revival.
I'd be willing to work on the required code changes myself, but before investing the time and work I'd like to see what other people think of this idea. Thoughts? Like? Dislike? Questions? Criticisms?
Thanks in advance!