Skip to content
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

Replay activities? #184

Open
PatriciaMoller opened this issue Dec 7, 2017 · 10 comments
Open

Replay activities? #184

PatriciaMoller opened this issue Dec 7, 2017 · 10 comments

Comments

@PatriciaMoller
Copy link
Collaborator

Is their any design reason as to why you can't replay an Activity when logged in?

It might be a bit problematic, especially for Activities with vouchers. If you don't get it the first time you, don't get a second chance to show that you might have learned something from the first play.

@pjotrsavitski
Copy link
Member

Changing that one would be complicated. It would also have an effect on the system overall.

A few examples that came to my mind:

  • A list of activities played wold have multiple ones, without a possibility to make any difference
  • Continuing an activity could become problematic (if multiple could be started)
  • Replaying for vouchers (although, those should not be valuable enough for that kind of grind)

As this is a major change (call it a feature if you must), then we would need a really good reason to make it happen.

@PatriciaMoller
Copy link
Collaborator Author

Why would there be multiple entries, is it listing the instances you have started?

I mostly noticed that testing becomes rather cumbersome when you more or less have to create a new activity to see how things act when logged in. If we just expect that player most likely won't replay anything, than it's not a big problem. But it also feels a bit unfair.

@pjotrsavitski
Copy link
Member

pjotrsavitski commented Dec 7, 2017 via email

@pjotrsavitski
Copy link
Member

I meant this one, thought it does seem to have the date being shown. Thus, it might not be all that confusing.

screen shot 2017-12-08 at 14 49 28

@PatriciaMoller
Copy link
Collaborator Author

Would it have to list every attempt? Why not show only the latest one and hide the rest, or separate on-going from completed?

Would it be possible to check if the voucher has been given? To stop them from getting multiple rewards even if they keep replaying

@pjotrsavitski
Copy link
Member

Well, listing all attempts might make sense (or not), depends on what we want to achieve. Separation is possible, but there should be some logic behind it.

Currently, the system does not relate game and voucher. If we want to keep the relation, then the current logic would have to change. If the voucher is no longer available, because user has already received one for playing the same activity, then it would introduce changes to system logic.

@PatriciaMoller
Copy link
Collaborator Author

PatriciaMoller commented Dec 12, 2017

I think it might be a bit overwhelming to see all them at the same time. They currently don't seem to be listed in any particular order either. I'm guessing they're sorted in the order the Activities were added to the system, but that doesn't make any sense if you don't know about that.
Putting completed ones in a "Completed" tab would at least tidy it up a bit. Being able to chose sorting order might be good too. Eg. Name, Progress %, Start time. Having Progress as default would make it easy for players to see what is the quickest to finish.
(The listing should maybe be its own issue/discussion)

I thought if it would be enough if the system didn't allow a user to get the same voucher twice. But didn't realize that the same voucher could be tied to multiple activities. If the player doesn't find out what voucher the got until the end of the game, they might feel cheated if they finish an Act. only to get a "Sorry, you've already gotten this". But then again, would one really need multiples of the same voucher, at least within the same day?

@pjotrsavitski
Copy link
Member

Yes, making changes could make things more complicated.

As for the vouchers. One could many instances of the same one, right now, there are no real limitations. The only possibility of not getting one is in case there is a limited amount, but we already have an issue about explaining that one.

@PatriciaMoller
Copy link
Collaborator Author

So far, no one I've tested with has been to that page. It might not be the highest priority. But as it has been brought up, it might be some that will have to be looked upon. (I haven't really been thinking of any of the Profile or Dashboard pages. Been mostly focused on the game itself)

Maybe it's something to be decided for each voucher, but how they are limited should be figured out. (Only apply the total amount limit, one per person, X amount for a set time, etc). And the tools for it should work. Something less valuable (E.g 10% in the Cafeteria) maybe wouldn't be a big issue if someone got a bunch of those and a lot are available. But free tickets or such might be more restricted. I'm not really sure what the scope for how big the rewards could be is.

Can you clarify what we have issues explaining? Is it about the voucher limitation?

@pjotrsavitski
Copy link
Member

Well, if you play some game in multiple parts (on several days; let's imagine there is a valid reason for that because that activity involves multiple zoos), then picking off from that page could be reasonable.

Dashboard is also the page you land on after logging in.

Well, the current solution is quite general and could be used in many different ways (the limitation of the amount being just one example). We still have not gotten any layout of what the vouchers would be, this makes it hard to make it more specific.

The vouchers could be spent from the Profile page (I did show and explain the process during the last meeting).

By the explaining I meant an issue that describes adding information about vouchers into the game. The issue #150

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

No branches or pull requests

2 participants