It's been a while since I last did any game development, think I was about 12 when I made my last game, and to be honest I have no idea what on earth prompted me to stop doing this because it's a blast.
Yesterday I took part in IPSC 2009 and was the one solving problem H, which was a game of 10 wolves under your control hunting a flock of 60 sheep. Each turn you could make ten moves and the game's servers then made ten moves of sheep (I think). It was very fun to play and we managed to win the easy round by catching ten sheep, but ran out of time to eat all sixty.
Fast forward a few hours and it's the middle of the night with the internets down. I couldn't work on Twitulater so I decided to make a game of Wolf Hunt because I needed a sample app for the lecture this Saturday anyway.
I had a blast making the game, but it was quickly apparent that one wolf alone isn't enough to catch the sheep because they keep running away. The solution to this problem turned out to be simple - I invented the Quantum Wolf Hunt.
The way this solved the problem is that it introduces other wolves onto the gaming board to spook the sheep. However there is a twist - no ability to make a coordinated attack because each wolf is hunting their own sheep on a different quantum plane and depending on connection speeds and server load, the other wolves' motion could be non-linear.
Haven't managed to test this in practice, but that's why I'm putting it out a week in advance. To iron out any kinks.
Have fun guys :P
![Reblog this post [with Zemanta]](https://img.zemanta.com/reblog_e.png?x-id=add29e73-c816-414d-a8b0-a7bfb1b82954)
Continue reading about The game of Quantum Wolf Hunt
Semantically similar articles hand-picked by GPT-4
- IPSC 2006
- Cool thing Thursday: Dream of Pixels
- The real-time WebCamp bash
- Tracking runs is fun! :D
- Unit testing is anti-productive
Learned something new?
Read more Software Engineering Lessons from Production
I write articles with real insight into the career and skills of a modern software engineer. "Raw and honest from the heart!" as one reader described them. Fueled by lessons learned over 20 years of building production code for side-projects, small businesses, and hyper growth startups. Both successful and not.
Subscribe below 👇
Software Engineering Lessons from Production
Join Swizec's Newsletter and get insightful emails 💌 on mindsets, tactics, and technical skills for your career. Real lessons from building production software. No bullshit.
"Man, love your simple writing! Yours is the only newsletter I open and only blog that I give a fuck to read & scroll till the end. And wow always take away lessons with me. Inspiring! And very relatable. 👌"
Have a burning question that you think I can answer? Hit me up on twitter and I'll do my best.
Who am I and who do I help? I'm Swizec Teller and I turn coders into engineers with "Raw and honest from the heart!" writing. No bullshit. Real insights into the career and skills of a modern software engineer.
Want to become a true senior engineer? Take ownership, have autonomy, and be a force multiplier on your team. The Senior Engineer Mindset ebook can help 👉 swizec.com/senior-mindset. These are the shifts in mindset that unlocked my career.
Curious about Serverless and the modern backend? Check out Serverless Handbook, for frontend engineers 👉 ServerlessHandbook.dev
Want to Stop copy pasting D3 examples and create data visualizations of your own? Learn how to build scalable dataviz React components your whole team can understand with React for Data Visualization
Want to get my best emails on JavaScript, React, Serverless, Fullstack Web, or Indie Hacking? Check out swizec.com/collections
Did someone amazing share this letter with you? Wonderful! You can sign up for my weekly letters for software engineers on their path to greatness, here: swizec.com/blog
Want to brush up on your modern JavaScript syntax? Check out my interactive cheatsheet: es6cheatsheet.com
By the way, just in case no one has told you it yet today: I love and appreciate you for who you are ❤️