Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Save more on your purchases! discount-offer-chevron-icon
Savings automatically calculated. No voucher code required.
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Unreal Development Kit Game Programming with UnrealScript: Beginner's Guide

You're reading from   Unreal Development Kit Game Programming with UnrealScript: Beginner's Guide Create games beyond your imagination with the Unreal Development Kit

Arrow left icon
Product type Paperback
Published in Dec 2011
Publisher Packt
ISBN-13 9781849691925
Length 466 pages
Edition 1st Edition
Languages
Tools
Arrow right icon
Author (1):
Arrow left icon
Rachel Cordone Rachel Cordone
Author Profile Icon Rachel Cordone
Rachel Cordone
Arrow right icon
View More author details
Toc

Table of Contents (18) Chapters Close

Unreal Development Kit Game Programming with UnrealScript
Credits
About the Author
About the Reviewers
www.PacktPub.com
Preface
1. Project Setup and Test Environments FREE CHAPTER 2. Storing and Manipulating Data 3. Understanding the Class Tree 4. Making Custom Classes 5. Using Functions 6. Using States to Control Behavior 7. Working with Kismet 8. Creating Multiplayer Games 9. Debugging and Optimization 10. Odds and Ends Pop Quiz Answers Index

Time for action – Debugging using the log


The first question we need to ask is: are our classes being used in the first place? Let's put a few logs in to find out.

  1. We'll start with BrokenActor. Even though we see it in the map when we run the game, we shouldn't make any assumptions about what's going on. We'll add a log in PostBeginPlay:

    simulated function PostBeginPlay()
    {
        `log("BrokenActor PostBeginPlay!");
    
        foreach DynamicActors(class'Pawn', Master)
            break;
    }
  2. We'll also add one in BrokenGame:

    function PostBeginPlay()
    {
        `log("BrokenGame PostBeginPlay!");
    }
  3. And finally one in BrokenPlayerController:

    simulated function PostBeginPlay()
    {
        `log("BrokenPlayerController PostBeginPlay!");
    }
  4. Compile the code and run the game.

  5. Exit and take a look at the log. We'll see that all three actors are logging their PostBeginPlay functions:

    [0005.44] ScriptLog: BrokenActor PostBeginPlay!
    [0005.44] ScriptLog: BrokenGame PostBeginPlay!
    [0005.44] Log: Bringing up level for play took: 0.032277...
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