When the Viewscreen Became a Game
In Part 1, I explained how a classroom layout problem accidentally turned into a starship bridge, then into a functioning viewscreen. It started with moving stars, then came the clock, class schedule, agenda and eventually the end-of-class warp countdown.
At that point, the viewscreen had become a useful little classroom system.
But it was still something students mostly looked at.
The next question was obvious.
Could they interact with it?
From Spreadsheet to Space Battle
For content review, I wanted a system I could use with any class on any topic. I decided to start simple. I built the content around a basic spreadsheet. Each row contained one question, one correct answer and three incorrect answers.
That was it.
The experiment was really a proof of concept: could ChatGPT Work take something that simple and turn it into an actual classroom game? Could students join from their desks? Could it all happen live?
The answer was...yes.
 |
| Lock In and Fire Phasers! |
I built a mode called Space Battles, basically my own starship-flavored version of Kahoot. Students logged in as the crew, entered the room code, and everyone in the room answered the same question shown on the viewscreen at the same time. The more students who answered correctly, the more damage the enemy ship took. If more than half of the crew answered incorrectly, the USS Lynx took damage instead.
Suddenly, a wrong answer didn’t just mean you missed a question.
It meant you might have helped blow up your own ship.
Which for some reason, students found motivating.
Who knew?
Then I Realized Something
To join the battle, students signed in using their school accounts, all approved through our technology department. That meant the system knew who they were each time they played.
And that meant I could track individual progress.
How many questions had each student answered correctly? How many had they missed? Were they understanding the overall content? This brought the tool from simply content review, to student assessment.
And if I could track progress, I could do something else.
They could level up. Ranks.
Every student begins as a Cadet. Answer enough questions correctly and eventually...
ding...
Ensign.
Keep going and move farther up the chain of command.
The highest rank is Captain, because I couldn't let them outrank me.
This Needed a Name
Somewhere around this point, I realized I couldn’t really keep calling it “the viewscreen” anymore.
We had a ship. We had a crew. Students had ranks. They were signing in, progressing and battling enemy ships together as a crew.
This had become something else. Something more. It needed a name.
Lynx Command.
And once Lynx Command existed, naturally I started wondering what else it could do.
It's Not ALL About Blowing Things Up
Space Battles worked, and the students liked it. But I didn’t want every review experience to revolve around combat.
Space exploration should probably include a little exploration.
So I created another game mode called "Unknown Events".
These were short episodic scenarios built around strange things the crew might encounter. Each one had a simple story arc: a setup, a conflict and two possible endings: success or failure.
The whole thing played out like a mini TV episode. A brief introduction described the situation while a random clip of the USS Lynx drifted majestically through space on the main viewscreen along with the episode title.
 |
| Season 1: Episode 3 'The Silent Archive" |
The gameplay changed too. This was designed as a second-level content review.
Instead of everyone answering every question, one crew member was selected at random to answer for the entire class. A correct answer moved the crew forward. A wrong answer earned a strike.
Three strikes and the mission failed.
Same review content.
Completely different experience.
The Questions Didn’t Change. The Experience Did.
This was something I wanted to be very careful about.
I didn’t want every new game mode to create more work for me. We were still reviewing the same material, so Unknown Events used the exact same spreadsheet as Space Battles.
Same questions. Same correct answers. Same incorrect answers.
The story changed. The mechanics changed. The pressure changed.
The content didn’t.
That became an important part of how Lynx Command was designed. Instead of creating a new set of materials for every activity, I uploaded the exact same simple content source to create completely different classroom experiences.
And Then There Were Credits
This is where things got a little silly. Which usually means I was having fun.
Since "Unknown Events" were starting to feel like mini TV episodes, I decided they needed ending credits. After each event, a credit sequence played with music while student names appeared on the viewscreen assigned to roles like First Officer, Communications or Engineering.
And then there was the final credit screen.
That’s where you might find things like:
"The Guy in the Red Shirt" or "Door Hiss Sound Effect".
The ridiculous part is that the students watched the credits.
They actually waited to see where their names would appear, especially on that last screen.
That was probably the point where I realized the fictional layer was becoming part of the culture of the room. They weren’t just answering review questions anymore. They were waiting to see what part they had played in the episode.
So Naturally, It Needed an Opening
By this point, students were fully buying into Lynx Command. We had battles, Unknown Events, crew ranks, credits, a ship and something that was starting to feel like its own little universe.
So yes.
I made it a television-style opening sequence. Because at this point...it needed one.
Think We’re Done?
Not even close.
By this point the school year was underway, and new situations kept coming up. Something would happen in class and I would think, “Hey, I could build something that would make this easier.”
Or more interesting. Or more useful. Or just a little more fun.
And because I now had AI tools that could help turn those ideas into working systems, I could actually try them.
That is the part I want other teachers to pay attention to.
I don’t expect you to build "Lynx Command 2".
I don’t even want you to.
This isn’t a sales pitch for Lynx Command subscriptions.
The point is that teachers now have access to tools that make it possible to build custom systems for their own classrooms, students and ideas. You no longer have to begin with programming skills. You need an idea, the ability to describe what you want, and enough patience to test it, refine it and occasionally tell the AI, “No...that is absolutely not what I meant.”
Most of the tools I’ve used have free tiers available, so sometimes that means spreading the work across multiple days.
But the important thing is this:
It’s buildable.
For years, teachers have had ideas for tools, games, simulations and systems that might have been useful in their classrooms but were simply too complicated or expensive to create. The distance between “I wish this existed” and “I built a version of it” is getting much smaller. And that changes what's possible.
Next Up
So far, I’ve mostly shown you what Lynx Command looks like from the student side.
Next time, we’re going behind the curtain to look at the admin system, student progress tracking, ranks and how all of these questions, events and game modes are actually managed.
Because eventually, even a starship needs a control panel.
Comments
Post a Comment