用SpriteBuilder和Cocos2D创作创意iOS游戏全攻略

需积分: 9 155 浏览量更新于2024-07-19 收藏 11.21MB PDF 举报

"《学习SpriteBuilder进行iOS游戏开发》是一本实用指南，专为想要利用SpriteBuilder和Cocos2D（更准确地说是Cocos2d-Swift）构建富有创意且趣味横生的2D游戏的开发者设计。作者Steffen Itterheim通过一系列精心设计的示例，引导读者逐步创建一个基于物理引擎的、具有帕拉克斯滚动效果的游戏。灵感来源于热销应用Badland和Leo's Fortune，游戏采用层级结构，允许开发者轻松添加更多内容，而无需编写额外的代码。本书共分三部分： 1. **入门篇**（Part I）：介绍SpriteBuilder和Cocos2D-iOS的基本概念。第1章简要介绍SpriteBuilder，随后的章节深入探讨如何设置基础架构（Chapter 2），控制和滚动功能（Chapter 3），以及物理与碰撞检测（Chapter 4）。第5章讲解时间线和触发器在游戏中的应用，第6章介绍菜单和弹出式视图的设计。 2. **实战篇**（Part II）：将理论付诸实践。第7章着重于主场景和游戏状态管理，第8章教你如何选择并解锁游戏关卡。第9章讲解物理关节的使用，第10章则涉及软体刚体物理，这些技术是提升游戏物理效果的关键。 3. **进阶篇**（Part III）：针对已经掌握了基本工具的读者，这部分内容将进一步提升技能，帮助你成为真正的SpriteBuilder专家。这部分可能包含高级技巧、性能优化和用户体验优化等内容。通过这本书，读者不仅能够掌握SpriteBuilder的使用，还能了解如何结合Cocos2D技术，打造一款既有吸引力又功能丰富的iOS游戏。书中不仅提供了步骤说明，还穿插了作者的见解、注意事项、工作方法和实用技巧，旨在帮助读者解决实际开发过程中的问题，提升游戏开发效率。无论你是初学者还是有一定经验的开发者，都能从中受益匪浅。"

11CHAPTER 1: Introduction

When you open the SpriteBuilder project’s Xcode project and build it, you may get warnings or even

errors. The projects were all tested with Xcode 6.0. If you’re using Xcode 6.1 or later, there’s a chance

that Apple made changes and improvements to the build settings and compiler. For instance, you

may be asked to update the project’s Build Settings or format. This is usually safe to do.

Note The first time you run the Xcode project, it may appear to hang or take a very long time to complete.

This may happen in particular when you haven’t previously opened the SpriteBuilder project and published

it. In that case, Xcode will launch the publish process for the SpriteBuilder project, but it won’t give you any

progress indication. Therefore, it’s recommended that you open and publish the SpriteBuilder project first—

that way, at least you get a progress indicator.

You may get some compiler warnings or errors pointing out potential problems in the code. If there

are warnings originating from one of the library targets (Cocos2D, ObjectAL, or Chipmunk), you can

ignore those. They are typically uncritical and may even persist for several releases. The Cocos2D

developers clean up warnings from time to time. New errors in previously perfectly acceptable code

can occur, too. Usually this happens with newer Xcode versions, where the compiler now treats

certain cases of warnings as errors, or it simply finds new potential issues in general. As long as

they’re only warnings, ignore them. They are most likely artifacts caused by advancements in Xcode.

However, if you get compiler errors in the libraries, you may want to try updating Cocos2D to see

if the warnings/errors go away. If there’s an error in the project’s code itself (the code in the Source

group) and you can’t fix it by yourself, please check the SpriteBuilder forum at http://forum.

spritebuilder.com for errata and fixes.

Of the 17 SpriteBuilder projects, the majority were originally created with SpriteBuilder versions prior

to v1.3. Therefore, the projects numbered 00 to 13 do not contain the necessary code to compile

them for the Android platform. The projects numbered 14 through 16 do have Android support.

Accordingly, the projects 00 to 13 will have different items in the schemes and platform lists than

projects 14 through 16.

Tip You can convert a SpriteBuilder project that doesn’t have Android support to one that does by following

the instructions here: http://android.spritebuilder.com/#dealing-with-spritebuilder-

projects-from-spritebuilder-1-2-and-earlier.

Example Projects Mapped to Chapters

As I said earlier, the example project numbers do not match the chapter numbers. Table 1-1 contains

a list of chapter numbers and names and what chapter particular projects belong to.

12 CHAPTER 1: Introduction

About Deployment Targets

Eventually, you’ll have to make a decision on which devices your app should run on, and which iOS

versions you are going to support.

Table 1-1. Mapping Chapters to Example Projects

Chapter Project Folder Project Notes

02 - Laying the Groundwork 00 - Starting Point Same as creating a new SpriteBuilder

project.

02 - Laying the Groundwork 01 - Change Scenes with Buttons Represents the stage of the project

midway through Chapter 2.

02 - Laying the Groundwork 02 - Level with Player Prefab Represents the stage of the project at

the end of Chapter 2.

03 - Controlling and Scrolling 03 - Parallax Scrolling Represents the stage of the project at

the end of Chapter 3.

04 - Physics and Collisions 04 - Physics Movement and Level

Borders

Represents the stage of the project at

the end of Chapter 4.

05 - Timelines and Triggers 05 - Timeline Animations Represents the stage of the project

midway through Chapter 5.

05 - Timelines and Triggers 06 - Triggered Animations Represents the stage of the project at

the end of Chapter 5.

06 - Menus and Popovers 07 - Popover Menus Represents the stage of the project at

the end of Chapter 6.

07 - Main Scene and

GameState

08 - Main Menu and Settings Represents the stage of the project at

the end of Chapter 7.

08 - Selecting and Unlocking

Levels

09 - Level Selection Scroll View Represents the stage of the project at

the end of Chapter 8.

09 - Physics Joints 10 - Chains Ropes and Springs Represents the stage of the project at

the end of Chapter 9.

10 - Soft-Body Physics 11 - Soft-Body Player Represents the stage of the project at

the end of Chapter 10.

11 - Audio and Labels 12 - Audio Labels and Localization Represents the stage of the project at

the end of Chapter 11.

12 - Visual Effects and

Animations

13 - Animations and Effects Represents the stage of the project at

the end of Chapter 12.

13 - Porting to Android 14 - HelloSpriteBuilder Android Test project created early in Chapter 13.

13 - Porting to Android 15 - Prior to making Android-

specific fixes

Starting point for an Android port

midway through Chapter 13.

13 - Porting to Android 16 - Bouncy Beast for Android Represents the stage of the project at

the end of Chapter 13.

13CHAPTER 1: Introduction

In theory, Cocos2D apps can run on any device with support for OpenGL ES 2.0 running at least

iOS 5. That makes the iPhone 3GS and the first iPad the oldest iOS devices you can run your app

on. In theory.

However, there’s a huge difference in terms of performance between the iPhone 3GS and the

latest iPhone, and the first iPad compared to the latest iPad. Mobile technology is advancing fast,

definitely faster than desktop computer technology.

Furthermore, market penetration of each newer iOS device is significantly higher than its

predecessors. Therefore, supporting older devices like the iPhone 3GS, perhaps even the non-

widescreen phones iPhone 4 and 4S, may not always be the financially sound decision that it seems

to be. Historically, and in stark contrast to the Android market, you’re more likely to generate a

larger number of sales by specifically supporting the latest iOS version, the latest models, and their

exclusive features rather than trying to reach as far back as you can.

My personal recommendation is to follow Apple as it introduces new models and discontinues old

models. If you are unsure which of them to support, support those that are capable of running the

latest iOS version when starting a new project. For a list of iOS devices and their newest supported

operating system, refer to this list on Wikipedia: http://en.wikipedia.org/wiki/List_of_iOS_

devices.

For iOS 8, the oldest targetable devices are iPhone 4S and iPad 2. Discontinued iOS models very

quickly fall by the wayside in terms of app sales. Almost the same goes for iOS versions. You

can certainly require the second-to-latest major iOS version as your minimum deployment target

when starting a new app project. For example, at this point in time, iOS 8 is the latest iOS version.

By supporting devices running iOS 7.0 and up, your app has a potential addressable market that

amounts to 94% of App Store usage as of October 5, 2014.

Apple periodically updates a chart that tells you what iOS versions users are using when they

visit the App Store: https://developer.apple.com/support/appstore/. This chart reflects your

addressable market, not the potential millions of devices still running iOS 6 and earlier. Most of those

older devices that have been sold are either broken, stolen, or forgotten—or for the most part, their

users hardly get any new apps. Maybe those users are perfectly happy with the device as is, or

maybe they know that new apps are unlikely to run on their device.

But it’s even more important to ensure your published app keeps running on the lowest supported

device and iOS version as long as possible to keep your existing customers happy. That alone

speaks against trying to support iOS versions as far back as theoretically possible, and this is

particularly true for games that are more demanding on device resources than most other types of

apps.

Consider that the performance span between an iPhone 6 and an iPhone 3GS is tremendous. In

the GeekBench benchmark, the iPhone 6 (Plus) is more than 10 times faster than the iPhone 3GS.

Compared to the iPhone 4S, the iPhone 6 (Plus) is still over 7 times faster in the same benchmark.

You’ll find an up-to-date performance comparison of all iOS devices here: http://browser.

primatelabs.com/ios-benchmarks.

Based on this benchmark, it’s not hard to predict that developers of graphically intense games will

stop offering their games or reduce quality on iPhone 4S and earlier, iPad (third generation) and

earlier, and the original iPad mini (non-Retina). Too far ahead are the iPhone 5 generation and newer

devices in terms of performance.

15CHAPTER 1: Introduction

Chapter 8—Selecting and Unlocking Levels

A level selection screen is added with the help of the Scroll View node. How CCScrollView works,

how it can be programmed, and how you can respond to its delegate methods is carefully explained.

The level selection pages are divided into multiple worlds, with each level unlocked by completing

the previous level.

Chapter 9—Physics Joints

This entire chapter is dedicated to creating physics objects out of joints, specifically chains, ropes,

and springs. How joints work and what you can and probably shouldn’t do with them is explained in

detail.

Chapter 10—Soft-Body Physics

The player prefab is replaced by a soft-body player. A soft-body object is a deformable physics

object held together by joints, with its collision shape divided into multiple smaller bodies. This

chapter also introduces custom rendering with Cocos2D because the player’s texture needs to be

drawn to match its deformed shape at any time.

Chapter 11—Audio and Labels

You’ll learn how to play short sound effects with the Timeline and how to play them programmatically

with ObjectAL, and you’ll learn how to play background music. The other half of the chapter deals

with Label TTF properties like shadows and outline, but it also explains how to create, import, and

use bitmap fonts in SpriteBuilder.

Chapter 12—Visual Effects and Animations

You’ll be creating a sprite frame animation for the first time, and you’ll make it work with the player’s

custom rendering class. An introduction to Particle Effect nodes is mandatory in a chapter on visual

effects. This culminates in the use of the Effect nodes, which are essentially shader programs that

you can add and design in SpriteBuilder. At the end of this chapter, you’ll hardly recognize the main

menu scene.

Chapter 13—Porting to Android

At first, you’ll see what is necessary to develop for Android. Then you’ll create a new project with

which you’ll test deployment to an Android device. Finally, you’ll convert the Bouncy Beast project

and fix any compilation, launch, and layout issues that occur. You’ll get advice on how to best

approach cross-platform development with SpriteBuilder.

www.allitebooks.com

剩余439页未读，继续阅读

iMand

粉丝: 3
资源: 12

用SpriteBuilder和Cocos2D创作创意iOS游戏全攻略

iOS Games Sprites

Learning iOS Game Programming

Learn SpriteBuilder for iOS Game Development by Steffen Itterheim

Learn Lua for iOS Game Development 无水印pdf 0分

Learn GameSalad for iOS Game Development for iPhone, iPad, and HTML5

EN_Learn GameSalad for iOS Game Development for iPhone, iPad, and HTML5.pdf

Learn Unity 2017 for iOS Game Development Create Amazing 3D Games

Learn Unity 2017 for iOS Game Development Create Amazing 3D Games for 无水印原版pdf

learn ios game development 源码

Learn Unity for 2D Game Development

最新资源