-
Notifications
You must be signed in to change notification settings - Fork 13
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
Create "recommended game" #160
Comments
I'm not sure on this feature, but maybe we should have a discussion about it, putting it here for logging purposes |
It's a good suggestion. We kind of do that at the moment, with the ordering of the open games. We order the games by predicted start date (soonest first). |
Hi Tom,
These weeks I have some stuff at work, and I'm spending a bit of time on
some other areas. Diplicity can handle itself for a while.
I think that we can add some extra attention to it with some simple layout.
In addition, it would be good to have a filter (especially in the finished
games list), so you can find for example a variant.
With regards
…On Mon, Jul 13, 2020 at 10:49 AM tttppp ***@***.***> wrote:
It's a good suggestion. We kind of do that at the moment, with the
ordering of the open games. We order the games by predicted start date
(soonest first).
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#160 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABXURGPQUAKWJ7HYUNJWA2TR3LDCHANCNFSM4NL7MCEA>
.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Some of the games are quite old, and we see some people looking for games relatively often.
We could pick a game as "recommended game", at any time.
All of the clients browsing the open game list will see that as top hit (MAYBE based on some settings of the player?).
That way, instead of letting everyone go into any game, we could guide them all into the same game, which will increases the speed of it filling.
The text was updated successfully, but these errors were encountered: