-
Notifications
You must be signed in to change notification settings - Fork 10
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
JesterQuest #114
Comments
|
finishing this quest (getting all achievements) unlocks: Jester Quester (achievement): Get a giant luck bonus (maybe something non-negligible, like 500), item find bonus (+25%?), title: Jester Quester, death message: traveled across the plains, swam through the seas, and climbed all the mountains to finish the Jester Quest just to end up dead in combat. |
I had another idea that assembling the JesterQuest collectibles could possibly boost their combat abilities with each one. Perhaps their basic attack just gets stronger, or they are just required collectibles for new abilities the Jester does not have access to right now. It would give them an opportunity to be more relevant in combat given you complete JesterQuest, and give tiers of rewards for each collectible in addition to the major bonus at the end. |
we can certainly do that. +0.3 spellPower per collectible would make them a truck at the end of it. Maybe it could unlock skills for them, too, but they'd need to be 100% rng and I haven't designed any skills of the sort yet. |
[11:27:15] <web:boozle [SWAG] [Gambler] [1~189]> is2g if one of them is located inside a fate area I will /rage/ This could be a possible disruption point, is linking JesterQuest to Fate. It'd be a bit nutters to expect anyone to get it after fates, but we can add fates after they get it. Mess with their questing a bit. |
JesterQuest will have to all be completed in the same ascension, but owning particular collectibles will make the jester stronger in combat, so it's still advantageous to have them. |
@seiyria you know.
Initiate plan JesterQuest.
The text was updated successfully, but these errors were encountered: