Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Conferences
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Unity 4.x Game Development by Example: Beginner's Guide

You're reading from   Unity 4.x Game Development by Example: Beginner's Guide A seat-of-your-pants manual for building fun, groovy little games quickly with Unity 4.x

Arrow left icon
Product type Paperback
Published in Dec 2013
Publisher Packt
ISBN-13 9781849695268
Length 572 pages
Edition 3rd Edition
Languages
Tools
Arrow right icon
Author (1):
Arrow left icon
Ryan Henson Creighton Ryan Henson Creighton
Author Profile Icon Ryan Henson Creighton
Ryan Henson Creighton
Arrow right icon
View More author details
Toc

Table of Contents (22) Chapters Close

Unity 4.x Game Development by Example Beginner's Guide
Credits
About the Author
About the Reviewers
www.PacktPub.com
Preface
1. That's One Fancy Hammer! FREE CHAPTER 2. Let's Start with the Sky 3. Game #1 – Ticker Taker 4. Code Comfort 5. Game #2 – Robot Repair 6. Game #2 – Robot Repair Part 2 7. Don't Be a Clock Blocker 8. Hearty Har Har 9. Game #3 – The Break-Up 10. Game #3 – The Break-Up Part 2 11. Game #4 – Shoot the Moon 12. Game #5 – Kisses 'n' Hugs 13. AI Programming and World Domination 14. Action! Appendix Index

Time for action – winning is everything


To determine the best course of action for the computer opponent, we need to create a prioritized list of rules for the computer to follow when deciding how to place a piece, which changes depending on the situation on the board. Let's pretend we are the computer, and we see this situation:

It wouldn't make sense to place an O anywhere but in X's way—otherwise, the computer loses. So we have our first rule:

  • Block opponent from winning

Now let's look at this situation:

Sure, X is about to win, but O also has an opportunity to win. Which is more important: for O to keep X from winning, or for O to win? Clearly, it's more important for O to claim victory and win the game. So we have our second rule:

  • Win

We just said that it's more important for O to claim victory than to block X, so we've also established a preferred order for these two rules:

  • Win

  • Block

Notice that our two statements are already written in pseudocode. Win() and Block() could just as easily be...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime
Banner background image