search

topicquests / sensecraft

GNU Affero General Public License v3.0
7 stars 1 forks source link

Node scoring persistence #139

Open maparent opened 2 years ago

maparent commented 2 years ago

First draft: Count descendent nodes (by other guilds?)

maparent commented 2 years ago

Thinking aloud about game dynamics. Mmowgli was an individual game, so any new node would accrue points to its ancestors. In a team game, we may (?) want to restrict points to nodes by other teams, to discourage teams building a huge (mostly irrelevant) tree of their own. I am thinking of crossing with other mechanics: I spoke of the threatened status of a node (i.e. there is an existing con that is not itself neutralized by another con, etc.) Maybe you should not get full points for a node that is threatened, which forces you to defend your positions... unless it's an attack you made yourself (ie. you built up a strawman.) I think with those we have the beginning of a suitable mechanics. More thoughts welcome. I'm actually thinking of focusing my energy here; it has a lot of UX impact, and would add a lot to the demo value.

maparent commented 2 years ago

First draft of algorithm written, first TDD test written against it. Ideally we should be able to use many scoring mechanism with the same stories.

maparent commented 2 years ago

There is space for much improvement, but the next step is to make this persistent.

KnowledgeGarden commented 2 years ago

Status of this? Can it be closed?

maparent commented 2 years ago

I would close after persistence