nclm / tagmixing-modules Goto Github PK

Identified at Maker Faire.

Selecting multiple answers to the answer “What happens when a player is tagged?” could mean:

• Multitag (the first time, the second time, etc.) – Implemented
• Each team have its effect – Implemented
• All happen at once – Tacit?
• All happen at once but still in a specific order to be physically possible (e.g. “Go to some place THEN Freeze”).

This need at least a new “floating” module (like multitag, etc), to be used with number variable modules. Maybe there’s a more elegant way.

Way of defining the playing zone, for instance “can only play staying on the lines” (made of chalk, or on a football field, etc.).

Identified at Maker Faire.

Missing answer to “When does the game end?”.

Have to think about use cases. Which player(s), etc. Use with # NUMBER.

Identified at Maker Faire.

Missing answer to “When does the game end?”:

X When everyone is not-it.

(opposite answer to the classic “When everyone is it”)

Identified at Maker Faire.

Missing answer to “When does the game end?”:

X When everyone is part of a team:
> PLAYERS
(Name which team)

Identified at Maker Faire.

Noted as a missing option for Beginning:

X The player starts with a playing ‘handicap’.
> TEXT 

The answers to that are the same than “The player get a playing handicap” in Tag. Some possible answers are however already in Beginning under “Do players have a special state when starting?”. There’s some re-organisation needed in order to have these options clean, and possibly shareable between Beginning and Tag, which therefore needs serious re-factoring since that’s not currently possible.

Also in this issue: the word ‘handicap’. Sounds to close to disability. Constraint? Challenge? Something more abstract like Flavour?

The modules should move from the custom txt format to a standard serialisation plain text format.

Possible options:

• JSON
• YAML
• XML (possibly GEXF?)

It will be the first step to enable the cards and the map to be programmaticality generated at each update of the modules, and will be the basis to build the app (for that one, see nclm/tagmixing-app#1).

In the run for the initial batch of modules, there was an “Open questions” corner.

From memory, those are unimplemented mechanics that I didn’t manage to make part of the system. They remain unsolved. Some may require serious refactoring of other things.

Before working on these, I either have to:

• Decipher the blurry photo.
• Find the original post-it notes that I surely kept somewhere.

The scope of project doesn’t allow balls, hoops and other game items yet.

Identified at Maker Faire.

Missing answer to “What happens when a player is tagged?”:

X The player joins the team of their catcher

This may be a duplicate of “The player becomes it!”, except it is contextual and more adapted for games with several teams tagging each other. Explore how to implement this with or without merging the options. Also, “catcher” is not a word used in Tag Mixing and chasing games, so the wording has to be thought about.

Identified at Maker Faire.

Probably in Jailing/Freezing: “back” should be removed from “They go back to”, since the players may have to go somewhere they never went before. Weirdly, the module isn’t on the txt hosted here, so that module was probably added/edited when making the cards or map. Add it back without the back.

Identified at Maker Faire.

Missing answer to “When does the game end?”:

When one of the team access its designated arrival place.
(Combine PLAYERS and PLACE modules to match teams to their places.)
> PLAYERS
> PLACE

“One of” attempts to renders “or and not and” from the note, double check if the logic is correct.

This is close to “When a team access a special place” which is already here. Look into it. To be merged, possibly. Keep the granular players options from that module (what is a team? all of the players, one of them, all the free ones among them, this amount of them, etc?).