You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
- State requirements of Xcode 10 and iOS 12.
- Trim the scene update example in the Usage Guide, moving out the optional game controller update into the comments.
> `componentSystems` is the default array of systems in every scene.
67
68
>
68
69
> Other steps are left for the subclass because each scene may need to handle these differently.
70
+
>
71
+
> If your game states also perform per-frame updates, then you must also call `OctopusKit.shared?.gameController.update(deltaTime: updateTimeDelta)`
69
72
70
73
----
71
74
@@ -166,7 +169,7 @@ systems.
166
169
167
170
- A **Subscene**is a node which may be added to a scene, but maintains its own hierarchy of entities and components. When a subscene is presented, the scene sets a special flag to pause the entities in the scene itself and any previous subscenes. This allows subscenes to be used for modal UI and content which must be overlaid on top of the scene's content, while pausing the main action without pausing the engine, so that only the topmost subscene will be updated.
168
171
169
-
> e.g.: In a game where the player can rummage through the hero's inventory, subscenes may be used to display the inventory while pausing the gameplay. Multiple subscenes may be used to let the player open smaller containers in the inventory, such as pouches inside a backpack, each displaying its contents over the parent container's UI. The engine ensures that only the topmost container's UI can be interacted with.
172
+
> e.g.: In a game where the player can rummage through the hero's inventory, subscenes may be used to display the inventory while pausing the gameplay. Multiple subscenes may be used to let the player open smaller containers in the inventory, such as pouches inside a backpack, each displaying its contents over the parent container's UI. The engine ensures that only the topmost container's UI can be interacted with.
Copy file name to clipboardExpand all lines: README.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -9,7 +9,7 @@ Built upon Apple's SpriteKit, GameplayKit and Metal technologies.
9
9
4.[Getting Started](#getting-started)
10
10
5.[Etcetera](#etcetera) (license, contact)
11
11
12
-
🚀 *Eager to dive in? Download the [Quickstart project.][quickstart-project] (Xcode 9.4+)*
12
+
🚀 *Eager to dive in? Download the [Quickstart project][quickstart-project] (Xcode 10.)*
13
13
14
14
> This project is a result of trying to make my own games as a hobby. I love Swift but I couldn't find any engines that support it or had the kind of architecture that I wanted to work with, so I started making my own.
15
15
>
@@ -184,7 +184,7 @@ Set the custom class of the scene as `OctopusScene` or a subclass of it. Load th
184
184
185
185
## Getting Started
186
186
187
-
1.**Read the [Quickstart and Usage Guide.][usage-guide]** You will need Xcode 9.4 or 10.
187
+
1.**Read the [Quickstart and Usage Guide.][usage-guide]** You will need Xcode 10.
188
188
189
189
> **Skill Level: Intermediate**: Although OK is not presented in a form suitable for absolute beginners, mostly because I'm too lazy to write documentation from step zero, it's not "advanced" level stuff either; if you've read the [Swift Language Book][swift-book] and have attempted to make a SpriteKit game in Xcode, you are ready to use OK!
0 commit comments