|
|
---|---|
Posted by | Prevent Same Quest Type Twice in a Row |
![]() [△] Nadir (#108458) Prophet View Forum Posts ![]() Posted on 2019-07-31 18:17:15 |
[ Support My Other Suggestions? ] More Tail + Leg Banding Colours Alter Stat Change to Giving Tree Cubs Change 'Dust' Eye Applicator Term to 'Fragments' New Event Title Ideas! ------- ✪ Summary: Rolling for a new quest is done when you don't like the current quest you have, right? So I bet when you roll for a new quest and get the exact same thing, that's thrilling isn't it!? Absolutely exciting! If the sarcasm wasn't heavy enough to imply what this suggestion is, here's the breakdown. ✪ What I Am Proposing: ➤ When you pay to get a different quest, it does NOT give you the same quest "type" twice in a row. Why would we want to pay money to be given the exact thing we are paying to bypass, just worded a different way, or worse yet, the exact same quest? This is not fair to players. If we roll for a new Snake Quest because we don't want the quest that requires us to hunt a Zebra, it is implied by paying that the player does NOT want a hunting quest. We should NOT be given a new quest to hunt a different animal. If we are given a quest during, say the July event to "defeat 8 lions in explore", and we roll for a different quest, we should NOT be given a quest to "defeat 8 lions in explore". Sometimes players roll for new quests multiple times in a row and it still does not give them something different - in some cases, something *they can do*. That 150 SB and 20 Shards or similar adds up fast, and before you know it, frustration and saying "maybe the next one will be different" can leave you with pocket change and shards you'll have to work double time to make back over a mechanic that shouldn't function this way in the first place. In short, we're giving you our lion game money for something, please modify it so our next roll makes it feel worth it. If you don't support, I'd like to know why. I appreciate constructive criticism over a simple "no". |
No replies have been posted yet.