This repository was archived by the owner on Dec 20, 2019. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 8
Game Folder Structure
Javier Torrente edited this page Dec 13, 2013
·
7 revisions
eAdventure games follow the next folder structure:
|-game.json
|-scenes
|- onescene.json
|- anotherscene.json
|- ...
|-atlas
|- onescene.atlas
|- onescene.png
|- ...
|-images
|- bg.png
|- ...
|-subgames
|- subgame1
|- subgame1.json
|- scenes
|- atlas
|- images
|- subgames
|- subgame2
...
NOTE: All json files (can o must? Revisar) can follow a simplified json notation with no double quotes.
game.json contains a Game, following the Game JSON Schema.
The folder scenes contains all the Scenes of the game, defined according the Scene JSON Schema.
This specification supports recursion as well. Under the 'subgames' folder there can also be other games stored each one in a separate subfolder following the same scheme. This allows reusing game pieces across games.
NOTE: The recursive specification of games through subgames is not implemented yet.
eAdventure - eUCM research group
- Setting up a Development Environment
- Contributing Guidelines
- Build Process
- Project structure
- Schema
-
Engine
- Files paths and FileResolver
- Binding Schema elements with Engine elements
- Managing the game view through Layers
- Game loop and scene management
- IO
- File Resolver
- Assets: Converting schema objects to engine objects
- Engine Objects
- Actors
- Effects
- Testing the engine
- Editor
- Remote communication
- Release Process
- Other documentation