Game & Activity Ideas - cdig/docs GitHub Wiki

When thinking of game ideas, it helps to think about player actions (verbs): Advocate, Argue, Flirt, Rate, Give, Read Comment, Greet, Recommend, Harass, Help, Join, Like, etc. And remember, "We are not the mountain, we are the sherpa"



Prototyped / Existing Games


Battery Tester

This game is on hold until we have a better higher-level solution for specifying schematic logic.

Component Caper

We are considering porting it to HTML.

Benefits

  • We have all the art.
  • We know the design well enough.
  • We have existing content.json files for it.

Downsides

  • A lot of the icons are SWFs, would need to be converted to SVGs or PNGs
  • At its core, it's just a multiple choice test — not very "game"-y

Floor It

This game had promise. But we didn't have time to work through a few design issues during the Cement project.

Reactor

We have an existing 2-player variant that probably doesn't need to be ported to HTML just yet.

There was also some work done on a 1-player variant. That might be worth porting. The game doesn't have much in the way of dynamics, though.



Budding Ideas

For games ideas that are just quick thoughts or wildly speculative, throw them into the list below.


1. Tours

Follow an arrow through each path of a circuit. It stops at various points, and talks about what's happening

2. Valve Picker

Given a named circuit, set up certain highlighted valves so that the circuit is correct. Easy/medium/hard

3. Driving

Drive a flow arrow down a circuit

4. Draw the path

The name says it all!

5. Wreck $#!%

Given a circuit, with some highlighted valves that can be configured, try to arrange them in a way that will damage stuff (can have multiple win conditions)

6. In-Order

Put these steps in order

7. Odd Valve Out

Remove the thing that doesn't belong

8. Repeat After Me

Watch "me" (computer) do it, then you do it

9. Bullshit Detector

The system presents steps one by one, and you have to stop it and correct it when it gets a step wrong (make sure the first few are always correct, so user is given context)

10. Day From Hell

Interactive story, where things get worse and worse. whenever something breaks, you have to pick the correct steps to take. Basically, the Filter Press game.

11. Select the Circuits

Select the circuits that: are washed out at the end of a job; are under high pressure; risk freezing; (for choices, show both the list of names and schematic views together, and make both selectable)

12. Simutech-like

time vs money

13. Builder

Drag component graphics to machine graphic, then connect hoses. Beside, it shows schematic assembling.

14. Cheat Sheet

The player could produce a physical list/record (like a cheat sheet for a test) using their own knowledge based on their own equipment.

15. Shutterbug

Using your smartphone, take a picture of a (cylinder/valve/etc) on your machine. Drag the blue dot onto the rod end, and the green dot into the blind end.

This gets submitted for marking, we mark it, and then when they log in next they see the result.

The novel ideas here are:

  • Manually marking their assignments. This makes it easier to do cool assignments that require a bit of human intelligence to assess. We can do this because our audience is small — 1000 active users doesn't mean much marking. We can gradually ramp up or down the number of manually-marked activities to balance our workload.
  • Using their phones to let them interact with their own equipment for credit. Mobile cool-factor + real life cool-factor.
  • Asynchronous activities — they don't get a result immediately. This opens up the possibility for challenges/activities/projects that they work on iteratively across many sessions.

16. Trivia Crack (Robyn)

Learners submit questions. If they submit a good one, we give them points. If they submit a great one that we don't have in quizzer yet, we get to use it (and give them lots of points).

17. Grader Hoses (Carl)

Correctly connect all of the hoses between the given valve ports on the grader (a game we have talked about and conceived in the past).

18. Sleuth? Click 'n' fix? (Robyn)

User can click on pieces of a scene to indicate which components have a problem. When they click, there is a multiple choice drop down asking them what they'd like to report/fix, etc. Example - several drawings of hoses that have been installed incorrectly, along with hoses that are fine. All hoses are clickable. User could click on a particularly long hose, for example, and then choose, "too long - replace with a shorter hose" from the multiple choice menu. Not sure how scoring/assessment should work - do they find out immediately if they were right? Do they have a counter at the top - 4 problems to go?

⚠️ **GitHub.com Fallback** ⚠️