Open interrogator opened 6 years ago
Want to join in on this one, @notsomes ?
Basic design of base game, irrespective of game rules ... degisn by @TPalfinger
@notsomes do you have any questions on this before you begin? Would you like more permissions with regad to this repo, for example.
I've finally been able to start looking at the code. I hope to have a clear understanding of it asap (I'm also checking how you have structured the how project, how Docker works, etc etc).
Once I get it I'll try to do some quick things just to know how everything should work and then we can move on to develop the actual game(s). Will keep you updated.
Yes, the priority is for you to have a working environment, preferably using Docker. Once you can serve and visit the web app, go to Games
and generate one. You'll see the JSON on screen, and in the console. It's dummy data now, but the format is the same as what the real data will be.
I have a few questions regarding this game and its set of rules, or at least what some things are meant to represent or what do they mean, so I'd like both of you @TPalfinger and @interrogator –maybe even @amelieacdh can contribute– (if you have anything to say about any point, as you see fit) to clarify them if possible:
In this game's rules it is expected to play multiple rounds. The rounds work in the same way (in terms of mechanics – linking words between them), though it is not clear to me what separates a "primary" link from a "secondary" link from a "tertiary" link.
Are "primary/secondary/tertiary/..." links defined by the user and how he sees the words/concepts/relations? For example, one person may see apple-fruit as a primary link, and apple-pear as a secondary link, while other one may see it the other way around and create those links in different rounds.
Are "primary/secondary/tertiary/..." links expected to be defined by ourselves by giving each level some kind of description/category? For example, we may label each round with some word or category we think goes well with the words appearing in the cards, providing some context for the round. Example: "Round One! Create links between the words in the context of "Festivities"!" – User proceeds to link grapes with Christmas, turkey with Thanksgiving, etc etc until the timer marks zero. "Round Two!" Create links between the words in the context of "bla bla bla" – Repeat process. Would this work better (in terms of structuring the game in some way)?
While the timer seems to be the logical approach to limit rounds, it may not work. What if someone is able (somehow) to create all of the links he can think of during the time the first rounds lasts? What is he supposed to do in the next rounds? Please detail the game mechanics in more depth if possible.
Regarding points, I'd go with something simple at first, such as awarding points 5 times the number of links created or something silly like that. Once we have a good database of links provided by users, though, I'd change the approach and award points (or something not points) or let's call it a "similarity score" in terms of how the user created links in relation to other people. We discussed this already and it seemed like a good/fun idea to play around with. Thoughts?
Doesn't look clear to me what the text field function is. I mean, I see you want users to "describe" the concept, though I think concepts should be crystal clear (the more the better). I already mentioned concepts such as "Festivities", but we may even go further and make them even more concrete. For example, at the time of creating the game we may have some initial categories (e.g. Festivities) and then concepts within those categories (Christmas, Thanksgiving,...), each of the latter making for a round. This may change the whole "primary/secondary/tertiary level" approach but could be explored as another developing/game option.
Please provide answers or thoughts about every of those questions, and of course don't take it as a critique but rather a starting point to build Game00 or other multiple games! :D
@notsomes (not sure if you get a notification without that)
Hope things are clearer know :) And do not hesitate to input your thoughts!
I think we @TPalfinger @notsomes and me should briefly exchange on the game details in a separate meeting; also we will decide what part of our data can serve as an initial data set to use.
@notsomes @interrogator @TPalfinger what do we need to tackle next?
I'm going to make an issue for the newest game, which we fleshed out in Salamanca. Work on the card games is probably best to stop right now.
Currently, the backend gives dummy data to the frontend on request. This data should be able to be turned into a visual game, with a ruleset provided by #1.
Doing this will (probably) require building a game base class in
src/static/site/js/game.js
, which all game types inherit from. Then, in the same or a different file, build a Game00 subclass that follows the rules for this game.