|
|
@@ -130,7 +130,7 @@ Even for large experienced game producers, the creation of such a complex game i
|
|
|
|
|
|
=== Extend SimpleApplication
|
|
|
|
|
|
-Every jME3 game is centered around one main class that (directly or indirectly) extends com.jme3.app.xref:ROOT:jme3/intermediate/simpleapplication.adoc[SimpleApplication].
|
|
|
+Every jME3 game is centered around one main class that (directly or indirectly) extends com.jme3.app.xref:core:app/simpleapplication.adoc[SimpleApplication].
|
|
|
|
|
|
|
|
|
[IMPORTANT]
|
|
|
@@ -207,7 +207,7 @@ If your game is even more complex, you may want to learn about "real" Entity Sys
|
|
|
|
|
|
=== The Smart Way to Access Game Features
|
|
|
|
|
|
-xref:ROOT:jme3/intermediate/simpleapplication.adoc[SimpleApplication] gives you access to game features such as a the rootNode, assetManager, guiNode, inputManager, audioManager, physicsSpace, viewPort, and the camera. But what if you need this access also from another class? Don't extend SimpleApplication a second time, and don't pass around tons of object references in constructors! Needing access to application level objects is a sign that this class should be designed as an xref:core:app/state/application_states.adoc[AppState] (read details there).
|
|
|
+xref:core:app/simpleapplication.adoc[SimpleApplication] gives you access to game features such as a the rootNode, assetManager, guiNode, inputManager, audioManager, physicsSpace, viewPort, and the camera. But what if you need this access also from another class? Don't extend SimpleApplication a second time, and don't pass around tons of object references in constructors! Needing access to application level objects is a sign that this class should be designed as an xref:core:app/state/application_states.adoc[AppState] (read details there).
|
|
|
|
|
|
An AppState has access to all game features in the SimpleApplication via the `this.app` and `this.stateManager` objects. Examples:
|
|
|
|
mitm001